Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Requirements Prioritization 
Razvan Radulian, MBA 
June 10th, 2014 
NWA IIBA Chapter Meeting
Agenda 
• Why are we talking about it? 
• What are we talking about? 
• Who cares? Why? 
• When do (should) we do it? 
• H...
Quick note about my approach (W5Hy) 
First (W5H), understand… 
• Why/Why not 
• What/What not 
• Who: By Whom/For Whom 
• ...
KISS: Above all, Keep it Simple and Short! 
• Simple, not simplistic! 
• Short, but no [lazy] short-cuts! 
[Noticed my min...
Why are we talking about it? 
• Statistic: 65% of IMPLEMENTED Requirements are rarely or never! 
• CHAOS Reports: How many...
What are we talking about? Core concepts 
• Definition… 
• Prioritization vs. Urgency… 
• Requirements Analysis… 
• Decidi...
Terms: Requirements Prioritization 
• The process of determining the relative importance of a set of items 
in order to de...
Terms: Prioritization vs. Urgency 
• Importance: What's most important to do 
• Timing: What do we need to do first
Fundamentals: Requirements Analysis 
• Prioritize Requirements 
• Organize Requirements 
• Specify and Model Requirements ...
Who cares? Why? Do-ers and Consumers... 
• Business side… 
• Implementation side… 
• Facilitator(s)…
Who: Business stakeholders 
• Customer 
• Sponsor 
• User(s) 
• Marketing, Sales...
Who: Implementation stakeholders 
• Implementers (IT and more) 
• QA/Testers 
• Trainers 
• Usability and User-experience ...
Who: Facilitator(s) 
• Business Analyst 
• Project Manager
When do (should) we do it? 
• Plan-driven approaches (e.g. Waterfall) 
• Change-driven approaches (e.g. Agile) 
• Initiati...
How do we do it? 
• The Process… 
• The Inputs… 
• The Outputs (again, Who cares? Why?)… 
• The Criteria…
How: The Process (simplified) 
• Plan and design a/the Requirements Prioritization process 
• Execute 
• Elicit and unders...
How: The Inputs 
• Business Case 
• Business Need 
• Requirements (ah, yeah!) 
• Requirements Management Plan 
• Stakehold...
How: The Outputs (again, Who cares? Why?) 
• Requirements [Prioritized] 
• Categorized… 
• Ranked…
How: Outputs: Requirements [Prioritized] 
• Categorized 
• High, Medium, Low 
• MoSCoW… 
• Shall, Will, Might… (Don't!) 
•...
How: The Criteria 
• Business Value 
• Business or Technical Risk 
• Implementation Difficulty 
• Likelihood of Success 
•...
Techniques 
• MoSCoW… 
• Voting… 
• Ranking… 
• Decision Analysis… 
• Risk Analysis… 
• Timeboxing/Budgeting…
Technique: MoSCoW 
• Must 
• A requirement that must be satisfied in the final solution for the solution to be 
considered...
Technique: Voting 
• Allocating fixed amount of resource. 
• "5" Dots 
• $100 or 100-points 
• Other tokens
Technique: Ranking & the Pareto Principle 
• Sorted Priorities 
• Avoiding the "High, Medium, Low" heuristic behavior 
• T...
Technique: Decision Analysis 
• Framing the Problem 
• Objectives/Criteria 
• Evaluating (e.g. impact/outcome & probabilit...
Technique: Risk Analysis 
• Impact & Likelihood 
• Assumptions & Constraints 
• Risk Mitigation Factors
Technique: Timeboxing/Budgeting 
• All In, All Out, Selective 
• PM's "Triple" Constraint: 
• Time (Schedule) 
• Money (Bu...
Some [of the many possible] Pitfalls... 
• Again, what was that 65% statistic?!? 
• Scope Creep or Gold-plating? 
• 99% Hi...
... and some "Best" Practices (1 of 2) 
• There are no "Best Practices"! 
• Do it early, but not too early! 
• Do it often...
... and some "Best" Practices (cont’d) 
• Clear and committed Roles & Responsibilities 
• Strong Support (Hey, Execs, are ...
Related Topics 
• Enterprise Analysis 
• Project & Resource Management 
• Programs& Portfolio Management 
• Agility & Disc...
Thanks! 
• My contact info: 
Razvan Radulian 
razvan@w5hy.com 
• Ask, share, help 
It is Common-sense... 
... just not tha...
Q&A
Upcoming SlideShare
Loading in …5
×

of

Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 1 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 2 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 3 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 4 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 5 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 6 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 7 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 8 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 9 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 10 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 11 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 12 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 13 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 14 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 15 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 16 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 17 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 18 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 19 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 20 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 21 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 22 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 23 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 24 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 25 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 26 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 27 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 28 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 29 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 30 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 31 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 32 Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014 Slide 33
Upcoming SlideShare
How to prioritize requirements - better and faster (workshop), Razvan Radulian
Next
Download to read offline and view in fullscreen.

1 Like

Share

Download to read offline

Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014

Download to read offline

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 ;-).

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Requirements prioritization, Razvan Radulian, NWA IIBA Chapter, June_2014

  1. 1. Requirements Prioritization Razvan Radulian, MBA June 10th, 2014 NWA IIBA Chapter Meeting
  2. 2. 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
  3. 3. 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?
  4. 4. KISS: Above all, Keep it Simple and Short! • Simple, not simplistic! • Short, but no [lazy] short-cuts! [Noticed my minimalistic style?]
  5. 5. 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
  6. 6. What are we talking about? Core concepts • Definition… • Prioritization vs. Urgency… • Requirements Analysis… • Deciding how to decide
  7. 7. 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
  8. 8. Terms: Prioritization vs. Urgency • Importance: What's most important to do • Timing: What do we need to do first
  9. 9. Fundamentals: Requirements Analysis • Prioritize Requirements • Organize Requirements • Specify and Model Requirements • Define Assumptions and Constraints • Verify Requirements • Validate Requirements Source: BABOK, Requirements Analysis Knowledge Area (6.1)
  10. 10. Who cares? Why? Do-ers and Consumers... • Business side… • Implementation side… • Facilitator(s)…
  11. 11. Who: Business stakeholders • Customer • Sponsor • User(s) • Marketing, Sales...
  12. 12. Who: Implementation stakeholders • Implementers (IT and more) • QA/Testers • Trainers • Usability and User-experience experts • Support
  13. 13. Who: Facilitator(s) • Business Analyst • Project Manager
  14. 14. When do (should) we do it? • Plan-driven approaches (e.g. Waterfall) • Change-driven approaches (e.g. Agile) • Initiating/Planning vs. Monitoring & Control
  15. 15. How do we do it? • The Process… • The Inputs… • The Outputs (again, Who cares? Why?)… • The Criteria…
  16. 16. 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
  17. 17. How: The Inputs • Business Case • Business Need • Requirements (ah, yeah!) • Requirements Management Plan • Stakeholder List, Roles, and Responsibilities
  18. 18. How: The Outputs (again, Who cares? Why?) • Requirements [Prioritized] • Categorized… • Ranked…
  19. 19. How: Outputs: Requirements [Prioritized] • Categorized • High, Medium, Low • MoSCoW… • Shall, Will, Might… (Don't!) • Ranked • 1, 2, 3... • Sprint "Backlog"
  20. 20. How: The Criteria • Business Value • Business or Technical Risk • Implementation Difficulty • Likelihood of Success • Regulatory or Policy Compliance • Stakeholder Agreement • Urgency
  21. 21. Techniques • MoSCoW… • Voting… • Ranking… • Decision Analysis… • Risk Analysis… • Timeboxing/Budgeting…
  22. 22. 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.
  23. 23. Technique: Voting • Allocating fixed amount of resource. • "5" Dots • $100 or 100-points • Other tokens
  24. 24. 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
  25. 25. Technique: Decision Analysis • Framing the Problem • Objectives/Criteria • Evaluating (e.g. impact/outcome & probability) • Decision Tables & Decision Trees
  26. 26. Technique: Risk Analysis • Impact & Likelihood • Assumptions & Constraints • Risk Mitigation Factors
  27. 27. 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
  28. 28. 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!
  29. 29. ... 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
  30. 30. ... 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!
  31. 31. Related Topics • Enterprise Analysis • Project & Resource Management • Programs& Portfolio Management • Agility & Discipline (Risk-driven Management) • Facilitation
  32. 32. Thanks! • My contact info: Razvan Radulian razvan@w5hy.com • Ask, share, help It is Common-sense... ... just not that common!
  33. 33. Q&A
  • powerirs

    Sep. 15, 2014

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 ;-).

Views

Total views

1,046

On Slideshare

0

From embeds

0

Number of embeds

33

Actions

Downloads

51

Shares

0

Comments

0

Likes

1

×