Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  THE ART (OR SCIENCE?) OF PRIORITIZING REQUIREMENTS RIGHT
Previous Previous
 
Next Next
New Post 8/20/2018 8:20 AM
User is offline Srilatha
1 posts
No Ranking


THE ART (OR SCIENCE?) OF PRIORITIZING REQUIREMENTS RIGHT  
  1. Get all involved in a room to discuss each participant’s reasons for priorities so that they are all heard.
  2. Don’t try to prioritize all requirements in one sitting.
  3. Try to get numerical priority (especially for high priority items) instead of general high, medium, low categories.
  4. Buy A Feature (Assign a value to each feature and give stakeholders a fixed amount of fake cash that they may use to “purchase” the features they most desire.)
  5. First In, First Out
  6. Prioritize by considering Cost of Delay
  7. Company Drivers/Department Drivers – Know the priority of each driver and based on that, prioritize the requirements.
  8. MoSCoW approach – must have, should have, could have, won’t have
  9. Determine if multiple requirements are addressing the same problem to reduce potential duplicates or conflicting requirements first.
  10. Agree on a Ranking/Rating System and define the rank values (High, Medium, Low; What do they mean?)
  11. Refer to the project objectives to identify high priority requirements. If a requirement does not help achieve an objective determine whether the requirement is out of scope or an objective was missed.
  12. Determine high priority requirements by asking “If you could only have x items in your solution which would you choose?”
  13. Priority Pyramid – Force the group to determine the most important feature or requirement for the top box. Next select the next 2 most important items for row 2.
    Continue expanding by one feature for each row until the pyramid is built. The top 2 or 3 rows would be the highest priority.
  14. Realize that priorities will change over time, even on short projects. Constantly revisit
    priorities to ensure validity
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  THE ART (OR SCIENCE?) OF PRIORITIZING REQUIREMENTS RIGHT

Community Blog - Latest Posts

Alexey Kiselev
Alexey Kiselev
We are writing User Stories to fix the scope and describe - what our application should do when implemented.User Stories are great, because the are: Short, Defining Roles, A great connection of the requirement itself and a business need. User Story declared as a high level definition of the requirement, but it could be used to s...
0 Responses
Ann P
Ann P
What’s the difference between ECBA CCBA and CBAP Certification? Which certification should I pursue ECBA CCBA or CBAP? How do I know which certification is right/suited for me? There are so many certifications I am completely confused which one to pursue? Can you please guide me on which certification should I go for?   These are s...
2 Responses
Simona from Minit
Simona from Minit
Process mapping vs. process discovery is akin to perceived reality vs. reality; the former rooted in subjectivity, the latter rooted in verifiable data. Elements of process mapping creep into process discovery, restricting an absolute dichotomy between the two. However, the critical differentiator between mapping and discovery lies in the distincti...
0 Responses




Latest Articles

Demystifying Strategic Thinking in Business Analysis
Nov 12, 2018
0 Comments
One of my former business analysts on the team asked me this question recently; ‘I am really over being a BA. How do I move into strategy?&rsquo...
Featured Digital Library Resources 
Copyright 2006-2018 by Modern Analyst Media LLC