T Iteration Demo Vitamin B PP Iteration

T Iteration demo 2 Agenda  Project status (10 min)  achieving the goals of the iteration  project metrics  Work results (20 min)  presenting the iteration’s results  demo  Used work practices (10 min)

T Iteration demo 3 Introduction to the project Assembly Party Management System (PMS)  Assembly  An annual computer party organized in Hartwall Arena, Helsinki  Several thousand visitors in a four day event  Main events in the party are competitions (compos)  PMS  Sever/client system for handling the Assembly party compos  The new software will replace old system  Old system has been used for years and is a bottle neck for the party organizing  Requirements are pretty clear  Will be open source software  Other party organizations can take into use also Show this slide when there are new people in the audience.

T Iteration demo 4 Status of the iteration’s goals  Goal 1: Specify the goals of the project from all perspectives  OK  The goals are clear  Goals have been written to project plan and requirements document  Goal 2: Select and adapt work practices to be used in the project  OK  The practices are listed in the project plan  Risk management not properly adapted yet  Will be starting from next project meeting  Goal 3: Make the contract with the customer  The customer made contract with HUT  The project team made contract with HUT  There is no direct contract between the customer and the project team

T Iteration demo 5 Status of the iteration’s deliverables  Project plan  OK, except  chapter 5.2 QA plan, because it will be done in the next iteration  Requirements document  OK, all important requirements documented in general level  A lot of use cases  9 for visitors  18 for organizers  3 sign up  3 survey use cases  Some of the use cases have been further refined to detailed use case descriptions  VUC1 User account registration  VUC2 Party registration  VUC4 Entry submission  VUC6 Vote

T Iteration demo 6 Effort used on tasks RealizedPlanned Project management (project meetings) 85,0- Course lectures or meetings 10,5- Project planning (iteration planning) 28,5- Design and implementation (core) 6,0- Design and implementation (UI) 27,5- Requirements development 21,5- Architecture development 28,0- Communication (IRC, , etc.) 11,5- Reviews 6,5- Usability test planning & execution (SEPA) 0,0- Automated unit testing (SEPA) 0,0- Unit and integration testing 0,0- Documentation (updating wiki) 8,5- Learning the tools (C#, subv., Visual Studio) 28,5- Other work 1,0- TOTAL 263-

T Iteration demo 7 Resources (1/2)  Janne Holm Project Manager  Henrik Hovi Software Architect  Jukka Uskonen QA Manager  Teijo Laine Developer  Henri Tuomola Developer  Jukka Tornberg Developer  Pekka HelkiöDeveloper  Mikko SivulainenCustomer’s technical advisor  No effort calculated

T Iteration demo 8 Resources (2/2)  The 40 hours extra for the people with 190 hours were for the SEPA work  190 hours were changed to 170 hours because approximately only 20 hours of SEPA work is actually project work (the other 20 hours is for reporting the SEPA results) PMArQAD1D2D3D4SUM PP I I Total Original plan (in the beginning of the iteration) Realization and updated plan (realized hours and updates) PMArQAD1D2D3D4SUM PP 7138, I1 2981,561, I Total

T Iteration demo 9 Changes to the project  During the PP iteration no major changes were made to the project

T Iteration demo 10 Risks  We have fours major risks identified  A developer quits in the middle of the project.  Not probable  New technology causes problems  Might realize if not handled correctly  Project member getting sick for a long time (several weeks)  Not probable  The customer has no time to participate the project  Not probable

T Iteration demo 11 Results of the iteration  The most important deliverables of the iteration  Project plan  Requirements document  UI prototype  UI Prototype  A web based UI  Layout is already in pretty good shape  No real functionality yet, but user can browse different pages

T Iteration demo 12 Project plan (1/5) Stakeholders and staffing

T Iteration demo 13 Project plan (2/5) Project goals 1. Replace the old system with a new one  excellent framework to build on  minimum amount of functionality to be able to replace 2. Create high quality system with excellent maintainability and further development possibilities 3. Create more advanced features to the system 4. Some of the project members continue in the project after the course

T Iteration demo 14 Project plan (3/5) Project practices  Iterative, incremental development (course dictates)  Documents will be written in HTML  Will be exported to PDF when needed  Risks gone through and analyzed in each project meeting  Time tracking: weekly effort reports to PM  Small groups (UI, architecture, requirements)  Communication: IRC, , weekly meetings  Defect tracking: Trac

T Iteration demo 15 Project plan (4/5) Tools  Programming languages: C#, PHP5  MONO framework  Visual Studio for code generation  Subversion for version control  PostgreSQL database  Apache web server  XHTML compliant UI

T Iteration demo 16 Project plan (5/5) Phasing  The work will be conducted in three iterations  Project planning  Implementation 1  Implementation 2

T Iteration demo 17 Demo  System administrator UI  Visitor UI

T Iteration demo 18 Used work practices (1/3) Mandatory work practices  Iterative work  Natural choice  Time reporting  Collecting by is frustrating  We would need a way of reporting hours directly to some system  Version control (Subversion)  Natural

T Iteration demo 19 Used work practices (2/3) Own work practices  Weekly meetings  First meetings were too long  Now there’s smaller groups with assigned tasks so weekly meetings might get shorter  Are weekly meetings needed any more?  Communication: IRC,  IRC is our main communication tool  However, not everyone is “hanging” on IRC all day long  is used for important messages  Web pages  Trac (  Our internal wiki  pms.dy.fi  Our public web pages

T Iteration demo 20 Used work practices (3/3) Work practices in the future It seems that the work practices we’re using are working pretty well  Hour reporting is something we could take a look at  Also, we need to think about the weekly meetings  We need to have a reflection workshop to find out if it really is true