T76 4115 Iteration demo T76 4115 Iteration Demo

T-76. 4115 Iteration demo T-76. 4115 Iteration Demo Team Balboa I 1 - Iteration 9. 12. 2009

T-76. 4115 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 2

T-76. 4115 Iteration demo Introduction to the project – Happy office -Pick and paint time tracking and scheduling solution 3

T-76. 4115 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 4

T-76. 4115 Iteration 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 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 6

T-76. 4115 Iteration demo Realization of the tasks 7

T-76. 4115 Iteration demo Realization of the tasks 8

T-76. 4115 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 9

T-76. 4115 Iteration demo Resource usage 160 140 120 100 Planned hours 80 Realized Hours 60 40 20 0 Ohto Mikko Ville. H Nick Teemu Marja Risto Ville. S Osmo Realized Planned Hours hours 10

T-76. 4115 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 11

T-76. 4115 Iteration demo Quality metrics Requirements 12

T-76. 4115 Iteration demo Quality metrics 13

T-76. 4115 Iteration demo Quality metrics 14

T-76. 4115 Iteration demo Quality metrics 30+ Test cases 15

T-76. 4115 Iteration demo Quality metrics 16

T-76. 4115 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 17

Technical architecture T-76. 4115 Iteration demo Core System UI Components Post-requests View Controllers dhtmlx. Scheduler dhtmlx. Calendar Managers Java. Script Models Java. Script XML Parser DB XML dhtmlx. Tree

T-76. 4115 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 19

T-76. 4115 Iteration demo Major risks ID Risk 1 TKK’s Vista workstations fail to cooperate 2 Developers can’t work on the same days and in the same space. 3 A developer quits in the middle of the project. 4 Virtual server is lost 5 Yii framework and dhtml. XScheduler learning takes more time than calculated. 6 Customer can’t be reached 7 Usability requirement can’t be met with dhtml. XScheduler library Prop. Current at beg. prop. 3 1 3 2 2 2 1 1 2 0 1 1 Sev. Effects Controlling actions Responsible Development work is delayed. Developers’ motivation decreases. Developers use their own laptops (4/6 developers). Vista network stations are used as little as possible. 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. Project Build a good team spirit that everyone is eager to work together rather than alone. 3 Crucial 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) 3 Taking backups of the code and wiki. All our code and documentation may QA manager documentation on the virtual server. be lost if stored only on the server. Maintaining local versions of the code on Ville Saalo Development work is delayed. developers’ workstations. 2 2 Project manager and 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. 3 Development can’t continue. End result isn’t optimal Communicate questions and problems to customer as soon as they raise. Project manager 3 We 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 Architect 20

T-76. 4115 Iteration demo Demo ? 21

T-76. 4115 Iteration demo Agenda Introduction Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Technical architecture Risks Demo! + Wiki demo What Next 22

T-76. 4115 Iteration demo What next? • Quality + Usability + Delivery o o o Correcting identified bugs and enhancements Performing user, acceptance and process testing Usability evaluations and feedback Creating Selenium and Unit tests Delivering the system • Other tasks Finalizing especially UIs Implementing some new features but main focus is in quality and integrity. o Reporting features (tuntien purku) o o