110 likes | 265 Views
MANAGING SOFTWARE PROJECTS. PROJECT POST MORTEM REPORT Team <x> Name <A>, name <B>, name <C>, name <D>, name <E>, name <F>, name <G>……..……………………. Agenda. Project overview Project achievements Performance against plans Technical review and testing results Issues and risks summary
E N D
MANAGING SOFTWARE PROJECTS PROJECT POST MORTEM REPORT Team <x> Name <A>, name <B>, name <C>, name <D>, name <E>, name <F>, name <G>……..……………………
Agenda • Project overview • Project achievements • Performance against plans • Technical review and testing results • Issues and risks summary • Project successes • Lessons learnt • Next time? • The course?
Project overview • Client requirement summary statement • Development approach selected • Time constraints • Available funding and resources
Project achievements • Delivered scope • Quality of deliverables • Acceptance of deliverables
Performance against plans • Deliverables • Time • Effort & Cost • Earned Value Statistics at project closure • SPI = CPI = EAC (PMUs) =
Review & testing results • Hardware • Software • Integrated solution
Issues & risks summary • Top 3 risks • Risk statistics • Top 3 issues • Issues statistics
Project Successes • Project management • Solution development & delivery • The Team
Lessons learnt • Project management • Solution development & delivery • The Team
Next Time? • What would we do differently next time?
The Course? • Five important things learnt from COMP8110 • Suggested course improvements