Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (18)
Similar to DCBADD2015 our req are good
Similar to DCBADD2015 our req are good (20)
More from IIBADCBADD
Recently uploaded
Recently uploaded (20)
DCBADD2015 our req are good
- 2. 47% of unsuccessful projects fail to meet their goals due to poor requirements management Poor requirements are a major source of project failure. Source: PMI’s Pulse of the Profession: Requirements Management — A Core Competency for Project and Program Success, August 2014
- 3. How can we improve the quality of requirements? q Well written? q Complete? q Atomic? q Testable? q No ambiguous words? q Coherent? q Verified? q Pass the quality checker? q Glossary clear? q Unique identifiers q Consistent q .. q ..
- 5. Improve the quality of requirements with visual models. 27 mostly text-based requirements documents with 1490 requirements Team partially retrofitted requirements with models to identify gaps 82 initial models (poor quality) 345 additional models created (partial retrofitting) 178 requirements new or changed requirements 12% of requirements had issues and Average 2 issues per model Case Study from Seilevel Project
- 7. PROJECT SUCCESS 0% 20% 40% 60% 80% Met Business Intent On Time Within Budget Delivered Scope Formal Process To Ensure Quality No Formal Process Better requirements quality means better business outcomes. Source: PMI’s Pulse of the Profession: Requirements Management — A Core Competency for Project and Program Success, August 2014
- 9. …or not.
- 11. Exploration Investment Delivery Realization Elimination Business value is delivered when a solution meets a business need. Strategy Project/Program Realize Business Value Identify Business Value
- 14. 0 5 10 15 20 25 Use measurable business benefits to prioritize between projects Biz stakeholders select projects with most meausrable benefits Biz stakeholders select features contribute the most benefits strongly disagree disagree neither agree strongly agree Stakeholders struggle to connect business value to features. Business does reasonably well selecting projects But not as good at selecting features Source: Seilevel Customer Survey
- 17. Business Objective 2 Provide training to 100% of sales team Projects don’t always have to tackle the ultimate goal. Business Problem 1 Sales team not selling enough products Business Objective 1 Increase sales by $10 million Product Concept Online Training Business Problem 2 Sales team doesn’t understand products Download Training Training Surveys
- 18. Objective chains assess the value per feature. Objective Factor Business Objective Objective Factor Objective Factor Objective Factor Objective Equations Data Needs Features Features Evaluate the value of features or sets of features
- 19. Current state & Assumptions: 1000 sales reps 600 take training today 90% pass tests if trained 25% pass tests if not trained 640 pass tests today $200/day more sales if trained Often, a few features produce most of the value. Increasing # sales reps who passed tests increases sales Increase Revenue Taking training before tests increases # passed tests DOWNLOADABLE TRAINING ONLINE TRAINING 835 pass tests now (90% of 900 + 25% of 100) $39K increase in sales ($200 x 195 new passed tests) Providing training options outside classroom increases participation Providing online training increases # of reps taking training Providing offline training increases # of reps taking training Participation increases by 2% Feature value = $2.6K 300 more reps take training (30% of 1000) Participation increases by 30% $39,000/day $2,600/day
- 20. Inspection and adaption are critical for business success. • Business objectives focus • Cut minimal value projects and features • Link requirements to business objectives • Measure and improve Good Practices for Delivering Value Good practices Measure results