1. T-76.4115 Iteration Demo BetaTeam PP Iteration 13.10.2005

2. T-76.4115 Iteration demo 2 Agenda  Project status (15 min)  achieving the goals of the iteration  project metrics  Work results (20 min)  presenting the iteration’s results  project plan  requirements  demo  architectural structure  Used work practices ( 10 min)

3. T-76.4115 Iteration demo 3 Introduction to the project Motivation: This is a use-case driven, architecture centric and iterative release project to NAPA Ltd. Customer: NAPA Ltd ( computing-based systems for ship safety and performance ) Customer Coals: To implement, test and delivery a product database server, which work in the first phase together with current shared file style data manipulation. The new solution will be integrated to the application’s interface which already exists and uses its interface functions. Project members goals: Geting the product database server work done with good quality, learning new practices and tools as a team with good team spirit.

4. T-76.4115 Iteration demo 4 Status of the iteration’s goals  Goal 1: Specify the goals of the project from all perspectives  OK  Goal 2:Familiarize with the topic  OK, but customer current system familiarizing needs more effor from project group  Goal 3:Familiarize with different stakeholder  OK  Goal 4:Requirement Specification in general level including most important requirements and use cases  OK  Goal 5: Architecture at rought level  OK  Goal 6: Identifing risks  OK  Goal 7: Defining the methods and tools and working environment  OK, defining has been doen at rough level, but practices need focusing  Goal 8, Focusing building and version control practices  OK, version control parctice has been described in separate instruction, but the building process needs focusing

5. T-76.4115 Iteration demo 5 Status of the iteration’s deliverables  Project plan  OK, building parctices and some roles needs refining  Requirements document  OK, all important requirements documented in general level  Progess report  OK  Architecture (draft)  OK, part of requirement specification

6. T-76.4115 Iteration demo 6 Realization of the tasks StatusRealPlanDiff(Left) Meetings and Lectures (PP iteration) Meetings & agendaok 37,7539-1,2512 Lecturesok 17,535-17.512 CVS & WEB pages workmoving I1 05-55 Tools & Infra & customer laptop evaluationmoving I1 020-2020 Requirements Specification (PP iteration)finnishd Architecture draft, Requirements elicitation, priorisation, validation and analysis, req Spe document 635-29 Project management (PP iteration)finished Project plan, progress report, working hour management 3237-5 Qality (PP iteration)under work Reviews, defining practices and tools 817-93 * unplanned task (= a new task added during the iteration)

7. T-76.4115 Iteration demo 7 Working hours by person  The customer laptop evaluation couldn’t start as planned  Requirements work overestimated  SEPA work starting has been postponed  Unclear working hours reporting period in the planning phase RealPlanDiff Ulla Suomela 6291-29 Jari Leppä 2856-27 Raine Mäki 2056-36 M4 000 M5 000 M6 000 M7 000 Total 11020393 Realized hours in PP iterationPlan in the beginning of this iteration PP Σ I1I2Total Ulla 919030 150 Jari 56 5044150 Rane 56 5044150 M4 007080150 M5 007080150 M6 007080150 Total 203 340358900 Latest plan (inc. realized hours and other updates) PPI1 Σ I2Total Ulla 624811040150 Jari 287210050150 Rane 20608070150 Hannu 070 80150 Juho 070 80150 Kauko 070 80150 Total 110390500400900

8. T-76.4115 Iteration demo 8 Risks  What is the current situation regarding the risks?  The progress of the iterations are too rapid Effort: There might be too little time to implement a critical and specific part of the project deliverables. Contolling actions:Everyone has a named backup person. Communication his /hers schedule problems and sharing the work early enough.Sharing the workload realistic and even.

9. T-76.4115 Iteration demo 9 Results of the iteration  Briefly describe the most important content of the major deliverables of the iteration, e.g., the following  project plan  requirements  system architecture

10. T-76.4115 Iteration demo 10 Project plan  Stakeholders and staffing

11. T-76.4115 Iteration demo 11 Project customer goals

12. T-76.4115 Iteration demo 12 Project members goals

13. T-76.4115 Iteration demo 13 Project practices and tools  Focusing the testing and building practises during next iteration  Tools For implementation: Borland, Together 2006 Eclipse 3.1, Java Sybase SQL Adaptive Server Anywhere 9 (ASA)SQL Adaptive Server Anywhere 9 CVS version control system For reports and documents: MS Office / Open Office Word, power point, Excel

14. T-76.4115 Iteration demo 14 Iteration phasing IMPLEMENTATION 1 (21.10.- 8.12.2005) 6 weeks 1. Increment planning phase 21.10 -31.10 ( e-mail review) 2. Increment implementation & unit testing phase 1.11 - 21.11 3. Increment itegration and system testing phase 22.11 - 8.12 (iteration demo)

15. T-76.4115 Iteration demo 15 Requirements Specification, Functional requirements

16. T-76.4115 Iteration demo 16 Requirement Specification, Non-Functional requirements

17. T-76.4115 Iteration demo 17 Demo - Basic Architecture

18. T-76.4115 Iteration demo 18 Used work practices  How have you been using the planned work practices, what are the experiences of  mandatory practices: time reporting  project meetings: standard agenda  Are you going to  adopt some new practices Change chairman according the phases in the iteration Increment implementation & unit testing phase 1.11 - 21.11 chairman is lead developer Jari Leppä Increment itegration and system testing phase 22.11 - 8.12 chairman is quality manager Raine Mäki

19. T-76.4115 Iteration demo 19 Questions