Requirements management


Published on

Requirements management

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Requirements management

  1. 1. Requirement Excellence Framework™ Requirement Management
  2. 2. Requirements Management• Manage versions of requirements documents.• Adopt and enforce a change control process.• Perform requirements change impact analysis.• Store requirement attributes.• Track the status of each requirement.• Trace requirements into designs, code, and tests. Confidential - Not for External Distribution 1
  3. 3. Requirement Management Functional and Supplemental Stakeholder Need User Story Use Case Requirements are grouped into bundles. Associated User Stories, Use Cases Stakeholder Needs, and Related Related Rules Business Rules are included by Functional Supplemental reference. Requirement Requirement Lifecycle Events are identified based on the type of requirements in the bundle. Lifecycle Events include such things as Validation, Design Reviews, User Bundles Acceptance Testing, Code Inspections, Sprint Plans etc. Lifecycle EventChange Requests DefectsAfter a bundle has Participants Test Scenarios Validations Requirement defectsbeen baselined, all are recorded andchanges, additions, Project Stakeholders Validations are performed tracked to ensure theyand deletions are Participate in Test Cases to confirm such things as: are resolved.controlled and lifecycle events to • needs are addressed,tracked. perform tests and User Acceptance Tests • developers understand validations of the are defined to ensure the requirements, and requirements. that the solution meets • there is sufficient budget the defined to build the solution. requirements. 2
  4. 4. Requirements Bundles• Requirement bundles are used to group a set of requirements together for build, test, and deployment.• Bundles may also be used for process improvement and organizational change teams.• For agile development, bundles are used for managing requirements for a Sprint or iteration.• Bundles may be baselined and any additions or changes will be controlled through change management.• Functional requirements may only be placed in one bundle, supplemental requirements may be placed in multiple bundles. 3
  5. 5. Project Retrospective• The purpose of the project retrospective is to close the project and record lessons learned. 4
  6. 6. Bundle Lifecycle Events• Requirement Inspection• Development Validation• Stakeholder Validation• Risk and Compliance Validation• Internal Audit Review• Organizational Change Review• Requirement Approval• Technical Design Review• Functional Design Review• System Test• UAT• Pilot Test• Deployment• Customer Satisfaction Confidential - Not for External Distribution 5
  7. 7. Bundle Lifecycle Events Change Bundles Defects Requests Lifecycle Event TestParticipants Validations Scenarios Test Cases Confidential - Not for External Distribution 6
  8. 8. Stakeholder Participation• Requirements have many sources. They may come from anyone with an interest in the outcome of the project. Customers, partners, end users, and domain experts are some sources of requirements; so too are management, project team members, business policies, and regulatory agencies.• It is important to know how to determine who the sources should be, how to get access to those sources, and how to elicit information from them. The individuals who serve as primary sources for this information are referred to as “stakeholders” in the project.• If you are developing an information system to be used internally within your company, you may include people with end-user experience and business domain expertise in your development team. Very often you will start the discussions at a business-model level rather than at a system level. If you are developing a product to be sold to a marketplace, you may make extensive use of your marketing people to better understand the needs of customers in that market.• Requirements may be elicited through activities such as interviewing, brainstorming, conceptual prototyping, using questionnaires, and performing competitive analysis. The result of requirements elicitation is a list of requests or needs that are described textually and graphically and that have been given priority relative to one another. Confidential - Not for External Distribution 7