T-76.115 Project Review

1. T-76.115 Project Review Artifacts PP Iteration

2. Agenda • Project status • Current team status • Iteration goals and deliverables • Tasks summary • Work practices to be used in the project • General XP practices • Test-driven development • Risk management • Current Artifact Tracker status • Project Plan • Plans for the Next Iteration • Summary

3. Team status Project manager: Michal Pilawski Developers: • Jie Chen • Kari Saikkonen • Xiang Liu • Jing Lei • Wei Yan Technical Issues • Cocoon • CVS • Advanced XML issues Equal responsibility of all development tasks

4. Iteration goals & deliverables • Goal 1: Requirements specification on general level including most important use cases. Status: OK, approved by the customer. • Goal 2: Project planned on general level. Status: Project plan ready, being verified during this meeting. • Goal 3: Next iteration planned on detailed level. Status: Goals set with the customer. Tasks planned and most responsibilities delegated. • Goal 4: Programming environment (server used for Cocoon and SCM activities) running. Status: Ready?? • Goal 5: Understanding domain Cocoon and XML. Status: To some extent… project manager fault (no exact deadline set) • (Goal 6: Select and adapt work practices to be used in the project) Status: Some practices described and adopted during next week

5. Realization of the tasks Reasons for major discrepancies • Tasks reporting inconsistency (project manager fault) • Lack of estimation practice • Unplanned work related to practices and Sixto

6. Working hours by person (as of Sunday, October 26)

7. Work Practices Team is going to work according to following XP practices: • Modified planning game (through web) • Small releases • Metaphor • Simple design • Planning game • Testing-driven development • Refactoring • Pair programming • Meeting practices based on XP • Collective ownership • Continuous integration In addition following practices: • Trapoli for effort management • Bugzilla for bug management • CVS for version control

8. Example: Planning game • Planning game will be used at the beginning of each release and iteration. • The customer brings a set of user stories. • The development team: • Estimates the effort required to implement each story • Assesses the technical risks associated with each story • Specifies how many hours they will be able to spend on the project in a given release or iteration. • The customer decides which functionalities should be implemented in a given release (iteration) on a basis of effort estimates and benefits the functionality would bring to the customer. • Project manager serves as a contact between customer and developers • User stories as shared through project webpage

9. Risks Management • Insufficient knowledge of CVS • Kari and Xiang give presentation on CVS to team members (5th of November) and they check the state of files in CVS regularly (Kari&Xiang) • Insufficient knowledge of technology (Cocoon) • Constant development and sharing of Cocoon knowledge by the team. Critical parts have to be reviewed by both Cocoon experts. Pair programming. Cocoon presentation 5th of November) (Kari&Ling) • Low motivation of the team members / Lack of commitment to the work • Short iterations and quick release phases. Clearly defined short tasks. Review session once a week to see progress. Building team spirit and increasing team commitment towards common goal. (Michal)

10. Plan for the next iteration User story Current system has to be expanded by functionality of filtering. It has to enable filtering by developer, project, release and sprint and by any other criteria defined in the artifacts. Goals: • Create architectural design of the system • Fully utilize CVS in practice • Start working with Cocoon 2.1 • Create XML Schema for the cyclist • Implement filtering functionality to the ready prototype (functionality 3.5 in Requirements document, part of every use case and not limited to any specific one) • Add user stories functionality to webpage (best using cocoon) Deliverables: • The system design and technical specification document (core architecture) • Short how-to-use CVS document • Refactored prototype code • XML schema for already developed cyclist • Documented code for filtering functionality • Updated project plan with more detailed test approach description • Updated requirements document • Test case specifications for test driven development • Test report • Progress report (slideshow)

11. Tasks • CVS (responsible Kari Saikkonen) – 5 hours (2.5h Kari, 0.5h other team members • Preparation of short how-to-use CVS manual. • Preparation and teaching of short practical CVS lesson to group members. • Design (responsible team members to be specified next week) – 60 hours • Create design under guidance of Heikki • User stories (responsible Michal Pilawski) – 5 hours (4h Michal, 1h developers for estimating effort for each story) • Risk management (responsible Michal Pilawski) – 15 hours (divided between all people responsible for controlling activities) • XML Schema (responsible Jie Chen, Wei Yan) – 40 hours • Master XML Schemas – 30 hours • Create XML Schema for cyclist – 10 hours • Cocoon presentation (responsible Kari Saikkonen and Jing Lei) – 10 h (5h preparation, 1h per person presentation) • Filtering functionality (responsible people to defined after design created) – 100 hours • Create test cases for filtering functionality – 5 hours • Code filtering functionality – 50 hours • Test and implement filtering functionality – 25 hours • Document the code – 3 hours • Deliver the new system to client, perform testing with client – 15 hours • Write test report – 2 hours • Update documents (responsible Michal Pilawski) – 10 hours • Project plan – 1 hour • Req. Document – 3 hours • Progress report – 6 hours • User stories functionality at project webpage (responsibility to be defined) – 5 hours

12. Tasks Dependencies User stories (5h) Use stories web (5h) Update documents (10h) CVS (5h) Filtering Functionality (100h) Cocoon (10h) Design (60h) XML Schema (40h) Risk management (15h)

13. Next phases’ goals Implementation 2 Goals: • Create effort tracking functionality (Use cases 001, 003) • Create bug and test cyclists (Use case 002) • Add linking functionality to cyclists (functionality 3.7) Implementation 3 Goals: • Implement functionalities required for Use case 005 • Implement all other not implemented functionalities • Perform heavy testing together with customer Delivery Goals: • Stabilize the system and deliver it to customer • Finalize the project (submit documentation, final report, etc.)

14. Thank you very much Any questions or comments?