T Project Review MalliPerhe PP Iteration

2 T Project Review Agenda  Project status  achieving the goals of the iteration  project metrics  Work results  presenting the iteration’s results  Used work practices

3 T Project Review Introduction to the project  Goal of the project is to build a modeling tool for Configurable Software Product Families (CSPF)  Customer is SoberIT  An engineering tool  Both the architectural and the feature-based view are modelled  And the relations between the different entities  Modeling tool must support the Kumbang language  The customer already has a configurator tool for Kumbang

4 T Project Review Introduction to the domain  Software Product Family  Products share common assets and architecture  Configurable SPF  significant part of the deployment process is done without adding new code by configuring existing assets  Kumbang  Synthesis of two earlier modelling languages

5 T Project Review Status of the iteration’s goals  Goal 1: Project planning  OK, slight slipping from the deadline  Goal 2: Understanding the domain  OK, group members have studied the material provided by the customer  Goal 3: Requirements specification  OK  Goal 4: Work and communication methods and environment  PARTIAL, practices have been agreed upon, but their deployment is still in progress

6 T Project Review Status of the iteration’s deliverables  Project Plan  OK, chapters 5.5, and were left out from the initial delivered version  Requirements document  OK  Eclipse plugin technology assesment  OK  Glossary  OK

7 T Project Review Realization of the tasks  Task durations were not estimated  Observations  Project plan 90 h (31 %)  Lectures 43 h (15 %)  Meetings 38 h (13 %)

8 T Project Review Working hours by person  Some hours from PP phase were moved to later iterations Realized hours in this iterationPlan in the beginning of this iteration Latest plan Plan Real 7 Rauli -4 Total 3 Matti -2 Mikko -8 Juha -2 Jukka -4 Antti 2 Antero Diff 42

9 T Project Review Changes to the project  Project started  No major changes to the project template  Glossary delivered as a separate document

10 T Project Review Risks  Significant risks have been identified and are being followed  Major risks  Communication problems with the customer and between group members  Team does not react to risks  Eclipse plugin technology is not suitable for the project  Risks are followed in weekly meetings using a follow-up template  Decision on the need for a corrective action

11 T Project Review Project  Stakeholders and staffing  Project group  Customer  Mentor  Most important project goals  Compatibility with the Kumbang language  Good expandability  Good architecture  High quality of code  Learning something

12 T Project Review Requirements  Customer's requirements have been identified  Quality over features and usability  Basic use cases extracted  Load/save/create models  Modify components and features  Browse the model  Add bindings and constraints

13 T Project Review Project practices  Iteration planning  Iteratative development  Time reporting  Trapoli  Defect tracking  Bugzilla and Excel  Documenting  Reviews  Internal and project  Requirements management  Version control  CVS  Recording the meetings  SEPAs  Progress tracking and control  Static methods  Heuristic evaluation  Refactoring

14 T Project Review Tools  Tools  Eclipse  CVS  Bugzilla  Trapoli  JavaNCSS  IRC/ICQ/Skype  Audacity

15 T Project Review Questions?