T-7 6 .6 1 2 Softw are Project Managem ent Face Wash – Project Plan Tero Jantunen Tuomas Järvensivu Tommi Kokki Juha Laitinen 28.4.2005 Face Wash Project Plan 1
Project scope and goals • Renew all the Customer Order Process (COP) and Transportation and Warehousing (TAW) screens • Increase the modularity of the architecture • Internal project – internal customer 28.4.2005 Face Wash Project Plan 2
3 Organization structure Face Wash Project Plan 28.4.2005
4 Face Wash Project Plan W ork flow diagram 28.4.2005
Process m odel W ork phases 1. Preparation (1.12.2000 – 31.1.2001) 2. Subcontractor training (1.2 – 28.2.2001) 3. Increment 1 (1.3 – 31.3.2001) 4. Increment 2 (1.4 – 30.4.2001) 5. Finalization (1.5 – 31.5.2001) 28.4.2005 Face Wash Project Plan 5
Preparation phase • Framework completion • End user survey • Screen prototyping • GUI guideline • Architectural planning • Product design • Requirements elicitation • Training material • Deliverable testing • Project Management 28.4.2005 Face Wash Project Plan 6
Subcontractor training phase • Framework completion • Project kick-off • Subcontractor training • Test & Quality planning • Project Management 28.4.2005 Face Wash Project Plan 7
I ncrem ents 1 and 2 • Replanning • Implementation – COP screens – TAW screens • Technical coordination • Module testing • Integration testing • Documenting & reporting • Defect resolving • Project management 28.4.2005 Face Wash Project Plan 8
Finalization • Replanning • Defect resolving • User manual • Release notes • Product finalization • Project management 28.4.2005 Face Wash Project Plan 9
Com m unication plan • Weekly meetings – Agenda prepared in advance, minutes recorded – Video conferencing for cross-site meetings • Extranet www site – Easy-to-access portal for all information • Site responsible contact persons • Problem solving workflow 28.4.2005 Face Wash Project Plan 10
11 Problem solving w orkflow Face Wash Project Plan 28.4.2005
Project Managem ent Practices • Built around meetings – Steering group meetings – Project management team meetings – Project team meetings • Controlling • Reporting – Project team level • Time tracking, test reports, code status – Project management team level • Weekly status, quality and implementation reports – Steering group level • Weekly reports (risks, requirements, expenditure, earned value, quality, need for comments 28.4.2005 Face Wash Project Plan 12
Measurem ent and m onitoring • Quality metrics – Open defects – Resolved defects – Defects resolved / new defects found rate – Document quality – reviews • Code metrics – LOC – Coupling – Comment / LOC ratio • Progress metrics – Spent hours – Status of tasks – Arisen risks – Requirement state – Earned value – Expenditure 28.4.2005 Face Wash Project Plan 13
14 Thanks for your tim e! Any questions? Face Wash Project Plan 28.4.2005
Recommend
More recommend