The document discusses critical success factors in software projects, noting that 26% of projects fail and 46% experience cost or schedule overruns or loss of functionality. It identifies common reasons for failures as including unclear user needs, scope, change management, technology changes, business needs changes, unrealistic deadlines, resistant users, and lost sponsorship. The document recommends managing expectations, skills, quality, and progress, making sustainable choices, and performing a post-mortem review after every project to identify lessons learned and improve future projects.

1. Critical Success
Factors in Software
Projects
Paper by John S. Reel, Trident Data Systems
Presented by Shelley Keith

2. 26% of all
software
projects fail
It’s Complicated
46% experience
cost/schedule
overruns,
function loss

4. 1. PMs don’t understand user needs
2. Ill-defined scope
3. Poor change management
4. Changes in technology
5. Changes in business needs
6. Unrealistic deadlines
7. Resistant users
8. Lost sponsorship
9. Skill gaps
Heed the Signs

5. • Manage expectations
• Manage skills and egos
• Protect quality
• Track progress
• Make sustainable choices
• Perform a post-mortem. Every. Time.
Getting it right(er)

6. 1. Declare intent at kickoff
2. Select representative participants
3. Prepare the review data
4. Conduct review of findings & experiences
5. Present the results to leadership & teams
6. Adopt the recommendations for max benefit
The Wrap Up...winning at post-mortems

7. 1. Declare intent at kickoff
2. Select representative participants
3. Prepare the review data
4. Conduct review of findings & experiences
5. Present the results to leadership & teams
6. Adopt the recommendations for max benefit
The Wrap Up...winning at post-mortems