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.

How to Organize and Prioritize Requirements


Published on

This presentation reviews how requirement prioritization is a decision process used to determine the relative impor­tance of requirements. The importance of requirements may be based on their relative value, risk, difficulty of implementation, or on other criteria. These priorities are used to determine which requirements should be targets for further analysis and to determine which requirements should be implemented first. We shall discuss the inputs, techniques used, and the expected outcome.

Prioritization of requirements ensures that analysis and implementation efforts focus on the most critical requirements

Published in: Business
  • Login to see the comments

How to Organize and Prioritize Requirements

  1. 1. How to Organize and Prioritize Requirements IIBA Event October 27, 2009 Patrick van Abbema
  2. 2. Requirements Analysis 2
  3. 3. Organize Requirements Don't agonize, organize. 3
  4. 4. Organize Requirements What is What are Why? the the Purpose? objectives? 4
  5. 5. Organize Requirements • Organizational Process Assets Inputs • Requirements • Solution Scope Organize • Organize Task Requirements Requirements • Requirements Outputs Structure 5
  6. 6. Organize Requirements Elements – Model Selection 6
  7. 7. Organize Requirements Stakeholders RACI NAME Role Responsibilities * R A C I - Coordinates participation across the stages of the project work HR Business for user readiness and A C I Lead organization re-design activities - Role design and user procedure definition Procurement Advises on purchasing policies and A C I Advisor processes 7
  8. 8. Organize Requirements Output REQUIREMENTS TRACEABILITY MATRIX Project Name: Business Analyst: Patrick van Abbema Project Manager Name: Project Description: <required> Initiative Process M or Req Requirement Description/ ID Req ID ID R? Source Notes / Questions I5 - Select Shall be and Section 508 Implement BReq1 Compliant M a Learning for Manageme Criteria: accessibility nt System - Support JAWS reader 8
  9. 9. Prioritize Requirements If you don't know where you are going, then any path will take you there... 9
  10. 10. Prioritize Requirements WHY? What is the Purpose? 10
  11. 11. Prioritize Requirements • Business Case • Business Need Inputs • Requirements • Reqs. Mgt. Plan • Stakeholder List Prioritize • Prioritize Requirements Task Requirements • Assess Proposed Solution • Allocate Req. Outputs • Validate Solution • Requirements Mgt.& Com. 11
  12. 12. Prioritize Requirements Techniques MoSCoW Must Should Could Won’t 12
  13. 13. Prioritize Requirements Examples Weighing your requirements Multiplying Compatibility Importance factor 13
  14. 14. Prioritize Requirements Elements Indicate your Products Ceiling Score with the requirement 1 = Out-of-the-box 2 = Standard tailoring 3 = Customization required 4 = Partner 5 = Future release 6 = Not available 14
  15. 15. Prioritize Requirements Examples Indicate how important the requirement is 1 = Very Low 2 = Low 3 = Medium 4 = High 5 = Very High 15
  16. 16. Prioritize Requirements Challenges Challenges in facilitating a requirements prioritization session include Non-negotiable Demands Unrealistic 16
  17. 17. Prioritize Requirements Stakeholders Implementation Domain SME Project Manager Sponsor SME 17
  18. 18. Prioritize Requirements Output Req. Requirements Importance Notes Ceiling ID to <XX> Score The Product shall Mandatory 1) Identify 3 full-scale 2 integrate with implementations of The Peoplesoft (v8.8) HR Product with integration with and Financials. Peoplesoft v8.8 HR and Financials. Who are these clients and what is their contact information? 2) What are the resources required by the Supplier to successfully complete the implementation? 18
  19. 19. Questions? 19