requirements prioritization, razvan radulian, nwa iiba chapter, june_2014
DESCRIPTION
We are not very good prioritizing requirements, wouldn't you agree? I presented this topic at the NWA IIBA Chapter as an introduction to the topic of Requirements Prioritization. Given the complexity of this topic, my goal was more to ignite questions, rather than provide "all the answers". From live feed-back, I succeeded (though I'm not sure that comes across from the slides by themselves... up for you to judge ;-).TRANSCRIPT
![Page 1: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/1.jpg)
Requirements PrioritizationRazvan Radulian, MBA
June 10th, 2014
NWA IIBA Chapter Meeting
![Page 2: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/2.jpg)
Agenda
• Why are we talking about it?• What are we talking about?• Who cares? Why?• When do (should) we do it?• How do we do it?• Techniques• Pitfalls & "Best" Practices
![Page 3: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/3.jpg)
Quick note about my approach (W5Hy)First (W5H), understand…
•Why/Why not•What/What not•Who: By Whom/For Whom•When/When not•Where/Where not• How/How Not
… then (y), explore:
•Why [not] That?•Why [not] Them?•Why [not] Then?•Why [not] There?•Why [not] That Way?
![Page 4: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/4.jpg)
KISS: Above all, Keep it Simple and Short!• Simple, not simplistic!• Short, but no [lazy] short-cuts!
[Noticed my minimalistic style?]
![Page 5: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/5.jpg)
Why are we talking about it?
• Statistic: 65% of IMPLEMENTED Requirements are rarely or never!• CHAOS Reports: How many successful projects?!?• Waterfall: 14%• Agile: 42%
• Scope Creep or Scope Management?• Project & Resource Management• Risk Management
![Page 6: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/6.jpg)
What are we talking about? Core concepts• Definition…• Prioritization vs. Urgency…• Requirements Analysis…• Deciding how to decide
![Page 7: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/7.jpg)
Terms: Requirements Prioritization
• The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Source: BABOK Glossary
![Page 8: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/8.jpg)
Terms: Prioritization vs. Urgency
• Importance: What's most important to do• Timing: What do we need to do first
![Page 9: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/9.jpg)
Fundamentals: Requirements Analysis• Prioritize Requirements• Organize Requirements• Specify and Model Requirements• Define Assumptions and Constraints• Verify Requirements• Validate RequirementsSource: BABOK, Requirements Analysis Knowledge Area (6.1)
![Page 10: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/10.jpg)
Who cares? Why? Do-ers and Consumers...• Business side…• Implementation side…• Facilitator(s)…
![Page 11: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/11.jpg)
Who: Business stakeholders
• Customer• Sponsor• User(s)• Marketing, Sales...
![Page 12: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/12.jpg)
Who: Implementation stakeholders
• Implementers (IT and more)• QA/Testers• Trainers• Usability and User-experience experts• Support
![Page 13: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/13.jpg)
Who: Facilitator(s)
• Business Analyst• Project Manager
![Page 14: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/14.jpg)
When do (should) we do it?
• Plan-driven approaches (e.g. Waterfall)• Change-driven approaches (e.g. Agile)• Initiating/Planning vs. Monitoring & Control
![Page 15: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/15.jpg)
How do we do it?
• The Process…• The Inputs…• The Outputs (again, Who cares? Why?)…• The Criteria…
![Page 16: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/16.jpg)
How: The Process (simplified)
• Plan and design a/the Requirements Prioritization process• Execute• Elicit and understand the requirements• Analyze and evaluate• Decide
• Monitor and upon change requests, repeat...• Once in awhile, step back and re-evaluate the process itself• If necessary, improve
![Page 17: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/17.jpg)
How: The Inputs
• Business Case• Business Need• Requirements (ah, yeah!)• Requirements Management Plan• Stakeholder List, Roles, and Responsibilities
![Page 18: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/18.jpg)
How: The Outputs (again, Who cares? Why?)• Requirements [Prioritized]• Categorized…• Ranked…
![Page 19: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/19.jpg)
How: Outputs: Requirements [Prioritized]• Categorized• High, Medium, Low• MoSCoW…• Shall, Will, Might… (Don't!)
• Ranked• 1, 2, 3...• Sprint "Backlog"
![Page 20: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/20.jpg)
How: The Criteria
• Business Value• Business or Technical Risk• Implementation Difficulty• Likelihood of Success• Regulatory or Policy Compliance• Stakeholder Agreement• Urgency
![Page 21: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/21.jpg)
Techniques
• MoSCoW…• Voting…• Ranking…• Decision Analysis…• Risk Analysis…• Timeboxing/Budgeting…
![Page 22: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/22.jpg)
Technique: MoSCoW
• Must• A requirement that must be satisfied in the final solution for the solution to be
considered a success.
• Should• High-priority item that should be included in the solution if it is possible. This is often a
critical requirement but one which can be satisfied in other ways if strictly necessary.
• Could• A requirement which is considered desirable but not necessary. This will be included if
time and resources permit.
• Won't• A requirement that stakeholders have agreed will not be implemented in a given
release, but may be considered for the future.
![Page 23: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/23.jpg)
Technique: Voting
• Allocating fixed amount of resource.• "5" Dots• $100 or 100-points• Other tokens
![Page 24: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/24.jpg)
Technique: Ranking & the Pareto Principle• Sorted Priorities• Avoiding the "High, Medium, Low" heuristic behavior • The Law of the Few (80/20, Pareto Principle)
• Focus on the important 35%• Remember the 65% statistic?
• Agile: Product Backlogs or the Lessons we should learn • See again the CHAOS Report (2011): Waterfall vs. Agile
![Page 25: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/25.jpg)
Technique: Decision Analysis
• Framing the Problem• Objectives/Criteria• Evaluating (e.g. impact/outcome & probability)• Decision Tables & Decision Trees
![Page 26: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/26.jpg)
Technique: Risk Analysis
• Impact & Likelihood• Assumptions & Constraints• Risk Mitigation Factors
![Page 27: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/27.jpg)
Technique: Timeboxing/Budgeting
• All In, All Out, Selective• PM's "Triple" Constraint:• Time (Schedule)• Money (Budget)• Scope (Product, Project)• Quality, Risks…
• Agile's “tricks”:• Product Backlog• Estimates• Planning & Commitments
![Page 28: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/28.jpg)
Some [of the many possible] Pitfalls...• Again, what was that 65% statistic?!? • Scope Creep or Gold-plating?
• 99% High-priority = NO Priorities!• "Flying by the seat of of your pants"• The Moving Target!• The Moving Highway!• The Moving Participants!
![Page 29: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/29.jpg)
... and some "Best" Practices (1 of 2)• There are no "Best Practices"!• Do it early, but not too early!• Do it often, but not too often!• Just-in-time Prioritization...
• Follow a process • If you don't have a process...
• Design one and experiment with it• Adopt and adapt (sorry, no silver-bullets!)
• Expect it to change
![Page 30: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/30.jpg)
... and some "Best" Practices (cont’d)• Clear and committed Roles & Responsibilities• Strong Support (Hey, Execs, are you listening?)• Once in awhile, step back and reflect...
... better yet, learn and improve!
![Page 31: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/31.jpg)
Related Topics
• Enterprise Analysis• Project & Resource Management• Programs& Portfolio Management• Agility & Discipline (Risk-driven Management)• Facilitation
![Page 32: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/32.jpg)
Thanks!
• My contact info:Razvan [email protected]
• Ask, share, helpIt is Common-sense...... just not that common!
![Page 33: Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014](https://reader035.vdocuments.net/reader035/viewer/2022070302/547db8b4b37959652b8b52fe/html5/thumbnails/33.jpg)
Q&A