t-76.4115 iteration demo t-76.4115 iteration demo team balboa i1 - iteration 9.12.2009
TRANSCRIPT
T-76.4115 T-76.4115 IterationIteration demo demo
T-76.4115 Iteration Demo
Team BalboaI1 - Iteration
9.12.2009
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
2
T-76.4115 T-76.4115 IterationIteration demo demo
Introduction to the project – Happy office
3
-Pick and paint time tracking and scheduling solution
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
4
T-76.4115 T-76.4115 IterationIteration demo demo
Status of the iterations goals• Creating the documents
• Done, but• 2 features still ”90% done”
– Graying feature– Permission system (several user roles) still under construction
• User management (”90 % done”)• Project management (”90 % done”)• Work type management (TODO)• Permission management (TODO)
• Could be done now and will be done 18.1.09
5
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
6
T-76.4115 T-76.4115 IterationIteration demo demo
Realization of the tasks
7
T-76.4115 T-76.4115 IterationIteration demo demo
Realization of the tasks
8
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
9
T-76.4115 T-76.4115 IterationIteration demo demo
Resource usage
10
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
11
T-76.4115 T-76.4115 IterationIteration demo demo
Quality metrics
12
Requirements
T-76.4115 T-76.4115 IterationIteration demo demo
Quality metrics
13
T-76.4115 T-76.4115 IterationIteration demo demo
Quality metrics
14
T-76.4115 T-76.4115 IterationIteration demo demo
Quality metrics
15
30+ Test cases
T-76.4115 T-76.4115 IterationIteration demo demo
Quality metrics
16
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
17
T-76.4115 T-76.4115 IterationIteration demo demo
Technical architecture
DBDB
ModelsModels
ManagersManagers
View ControllersView Controllers
Core System
XMLXML
UI Components
dhtmlxSchedulerdhtmlxScheduler dhtmlxCalendardhtmlxCalendar dhtmlxTree dhtmlxTree
JavaScript XMLParser
JavaScript XMLParser
Post-requests
JavaScript ModelsJavaScript Models
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
19
T-76.4115 T-76.4115 IterationIteration demo demo
ID RiskProp.at beg.
Currentprop.
Sev. Effects Controlling actions Responsible
1TKK’s Vista workstations fail to cooperate
3 1 2Development work is delayed. Developers’ motivation decreases.
Developers use their own laptops (4/6 developers). Vista network stations are used as little as possible.
Project manager
2Developers can’t work on the same days and in the same space.
3 1 2
Development work becomes inefficient when developers’ questions get answered with a delay. Quality of the final system is poor when developers haven’t made decisions together.
Try to choose work days that fit everyone and courage everyone to attend on those days. Build a good team spirit that everyone is eager to work together rather than alone.
Project manager
3A developer quits in the middle of the project.
2 1 3Crucial knowledge is lost.Project scope must be decreased.
Taking care of good team spirit. (avoiding)The development work of critical parts is done using pair programming and reviews. (minimizing effect)
Project manager
4 Virtual server is lost 2 2 3
All our code and documentation may be lost if stored only on the server. Development work is delayed.
Taking backups of the code and wiki-documentation on the virtual server.Maintaining local versions of the code on developers’ workstations.
QA manager and Ville Saalo
5
Yii framework and dhtmlXScheduler learning takes more time than calculated.
20
2 Development work is delayed.
Trying to learn the framework as early as possible. Arranging trainings and experience exchange sessions with the whole development team.
Architect
6Customer can’t be reached
1 1 3Development can’t continue.End result isn’t optimal
Communicate questions and problems to customer as soon as they raise. Project manager
7
Usability requirement can’t be met with dhtmlXScheduler library
11
3We may have to choose another technology.End result is of poor quality
Demonstrate the library to the customer with a demo. Developers use much time in the beginning for learning the features of the library.
QA manager
Major risks
20
T-76.4115 T-76.4115 IterationIteration demo demo
?
Demo
21
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
22
T-76.4115 T-76.4115 IterationIteration demo demo
What next?• Quality + Usability + Delivery
o Correcting identified bugs and enhancementso Performing user, acceptance and process testingo Usability evaluations and feedbacko Creating Selenium and Unit testso Delivering the system
• Other taskso Finalizing especially UIso Implementing some new features but main focus is in quality and
integrity.o Reporting features (tuntien purku)