How Agile Reduces Requirements Risk Ebg Consulting Slide Share
7 likes5,373 views
The document discusses how Agile practices help mitigate requirements risks in software development, highlighting issues such as scope creep, lack of customer involvement, and unrealistic expectations. It emphasizes the importance of maintaining a flexible, prioritized backlog, frequent delivery, and cross-functional collaboration to address these risks effectively. By implementing Agile methodologies, development teams can reduce costs associated with requirement errors and rework while improving overall product outcomes.
How Agile Reduces Requirements Risk Ebg Consulting Slide Share
- 1. How Agile Reduces Requirements Risk Ellen Gottesdiener www.ebgconsulting.com © EBG Consulting, 2010
- 2. Ellen Gottesdiener Founder & Principal Consultant, EBG Consulting Trainer, facilitator, mentor, agile coach, conference advisor Years of varied project and product experience Certified Professional Facilitator, Certified Scrum Master Expert Reviewer, contributor to IIBA BABOK® (Business Analysis Body of Knowledge®) Author: articles, books eNewsletter: Success with Requirements free - sign up at www.ebgconsulting.com
- 3. Agile practices Intro reducing risk Q&A Requirements Summary risks
- 4. requirements: basis for product development
- 7. requirements risks
- 8. top project risks creeping user reqts (80%) changing reqts (66%) poor specs (66%) www.ebgconsulting.com/reqtproblems.php
- 9. requirements errors 28% to 42.5% of software development costs www.ebgconsulting.com/reqtproblems.php
- 10. requirements rework 40% to 50% of total development budget www.ebgconsulting.com/reqtproblems.php
- 11. time
- 12. money
- 13. trust
- 14. #1 scope creep #2 lack of customer involvement #3 unrealistic customer expectations #4 poor impact analysis #5 requirements defects #6 changing practices and tools
- 15. #1 scope creep
- 16. freeze myth
- 17. product roadmap
- 18. product big-view release pre-view iteration now-view
- 19. rolling wave planning
- 20. incremental funding
- 21. timebox
- 22. needs are continually reprioritized
- 24. #2 lack of customer involvement
- 28. themes
- 29. demos
- 30. #3 unrealistic customer expectations
- 33. boulders rocks pebbles
- 34. collapse v & v
- 35. decision making
- 36. frequent incremental delivery
- 37. #4 poor impact analysis
- 38. needs change
- 39. development delivery usage dependencies
- 42. #5 requirements defects
- 43. ambiguous, missing, erroneous, conflicting requirements
- 45. right size
- 46. done
- 47. tamped- down requirements
- 49. analysis is just… enough in-time before
- 50. cross-functional team
- 51. #6 changing practices and tools
- 52. Evolution is chaos with feedback Physicist Joseph Ford
- 54. visibility
- 55. inspect and adapt
- 56. summary
- 57. #1 scope creep #2 lack of customer involvement #3 unrealistic customer expectations #4 poor impact analysis #5 requirements defects #6 changing practices and tools
- 58. reducing requirements risks with agile practices planning development delivery team
- 60. product roadmap rolling wave planning incremental funding continual reprioritization themes dynamic backlog
- 61. agile development practices
- 62. product owner/champion boulder – rocks – pebbles tamped-down requirements analysis spikes JIT analysis collapse v&v
- 64. done demos frequent delivery right sized documentation
- 65. agile team practices
- 66. cross-functional team daily calibration information radars feedback & learning collaboration
- 67. email ellen@ebgconsulting.com more agile ebgconsulting.com/agile.pdf about EBG www.ebgconsulting.com © EBG Consulting, 2010