Agile Project Management with Scrum
Business Requirement Documentation Problems
- Long and monolithic.
- Sometimes unreadable and unread.
- Lack of clarity about which features are for which client.
- Can become disconnected from actual client needs.
- Difficult to change or update.
Agility/XP + Lean + Engineering/Product advisor, mentor, Complexity-thinking practitioner. Change Agent for hire. Organisational gardener, culture curator, collaboration orchestrator, delivery facilitator. Author-Speaker
6 年Always amused to see my Dilbert strip (the one on top, the Bermuda triangle of Agile) go around since I authored it out of frustration during 2011
Director, Data & Analytics (DnA) Operations at BMO Financial Group
6 年I would suggest a more balanced metric between waterfall and agile as this seems to be leaning towards agile while missing benefits of the waterfall. I believe both are tools and have their own place in industries. We need to analyze the need and then use the appropriate tools to meet those needs. One of the key advantage of waterfall is the clear definition of the end state before work starts. Just imagine building a 100 mile road through 2-3 downtowns using agile. On the other hand, agile is excellent when the end state is not clear and you need to market the product as you go.
Senior Manager
8 年Great..
Agility/XP + Lean + Engineering/Product advisor, mentor, Complexity-thinking practitioner. Change Agent for hire. Organisational gardener, culture curator, collaboration orchestrator, delivery facilitator. Author-Speaker
8 年Happy to see the Dilbert strip I authored in 2010 still trending. The one above. Meanwhile Jim Highsmith agile triangle has become more popular: https://jimhighsmith.com/beyond-scope-schedule-and-cost-the-agile-triangle/