T-76.115 Project Review

Artifacts

PP Iteration

Agenda

1. Project status• Current team status• Iteration goals and deliverables• Tasks summary

2. Work practices to be used in the project• General XP practices• Test-driven development• Risk management

3. Current Artifact Tracker status4. Project Plan5. Plans for the Next Iteration6. Summary

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

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

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

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

Member Est. PP Real PP Est. I1 Est. I2 Est. I3 Est. Del

Xiang Liu 40 16.5 60 30 40 20

Jie Chen 20 10 40 60 50 20

Jing Lei 40 33 50 50 30 20

Kari Saikkonen

40 39.5 50 50 30 20

Sixto Franco

0 27.5 0 0 0 0

Michal Pilawski

100 83.5 20 20 20 30

Wei Yan 30 22 40 60 50 10

Work PracticesTeam 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

Example: Planning game1. Planning game will be used at the beginning of each release and

iteration.2. The customer brings a set of user stories.3. 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.4. 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.

5. Project manager serves as a contact between customer and developers

6. User stories as shared through project webpage

Risks Management1. 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)

2. 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)

3. 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)

Plan for the next iterationUser storyCurrent 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:1. Create architectural design of the system2. Fully utilize CVS in practice3. Start working with Cocoon 2.14. Create XML Schema for the cyclist5. 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)6. Add user stories functionality to webpage (best using cocoon)

Deliverables:1. The system design and technical specification document (core architecture)2. Short how-to-use CVS document3. Refactored prototype code4. XML schema for already developed cyclist5. Documented code for filtering functionality 6. Updated project plan with more detailed test approach description7. Updated requirements document 8. Test case specifications for test driven development9. Test report

10. Progress report (slideshow)

Tasks1. 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.

2. Design (responsible team members to be specified next week) – 60 hours• Create design under guidance of Heikki

3. User stories (responsible Michal Pilawski) – 5 hours (4h Michal, 1h developers for estimating effort for each story)

4. Risk management (responsible Michal Pilawski) – 15 hours (divided between all people responsible for controlling activities)

5. XML Schema (responsible Jie Chen, Wei Yan) – 40 hours• Master XML Schemas – 30 hours• Create XML Schema for cyclist – 10 hours

6. Cocoon presentation (responsible Kari Saikkonen and Jing Lei) – 10 h (5h preparation, 1h per person presentation)

7. 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

8. Update documents (responsible Michal Pilawski) – 10 hours• Project plan – 1 hour• Req. Document – 3 hours• Progress report – 6 hours

9. User stories functionality at project webpage (responsibility to be defined) – 5 hours

Tasks Dependencies

CVS (5h)

User stories (5h)

Design (60h)

Risk management (15h)

XML Schema (40h)

Cocoon (10h)

Update documents

(10h)Filtering Functionality

(100h)

Use stories web (5h)

Next phases’ goals

Implementation 2 Goals:1. Create effort tracking functionality (Use cases 001, 003)2. Create bug and test cyclists (Use case 002)3. Add linking functionality to cyclists (functionality 3.7)Implementation 3 Goals:1. Implement functionalities required for Use case 0052. Implement all other not implemented functionalities3. Perform heavy testing together with customerDelivery Goals:1. Stabilize the system and deliver it to customer2. Finalize the project (submit documentation, final report,

etc.)

Thank you very much

Any questions or comments?