1. Requirement Excellence Framework Requirement Management www.EnfocusSolutions.com

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. Requirement Management Functional and SupplementalStakeholder Need User Story Use Case Requirements are grouped into bundles. Associated User Stories, Use Cases Stakeholder Needs, and RelatedRelated RulesBusiness Rules are included by FunctionalSupplementalreference.RequirementRequirement Lifecycle Events are identified based on the type of requirements in the bundle. Lifecycle Events include such things as Validation, Design Reviews, UserBundlesAcceptance Testing, Code Inspections, Sprint Plans etc. Lifecycle EventChange Requests DefectsAfter a bundle has ParticipantsTest Scenarios ValidationsRequirement defectsbeen baselined, allare recorded andchanges, additions, Project Stakeholders Validations are performed tracked to ensure theyand deletions are Participate inTest Cases to confirm such things as:are resolved.controlled andlifecycle events to needs are addressed,tracked.perform tests andUser Acceptance Tests developers understandvalidations of the are defined to ensurethe requirements, andrequirements.that the solution meets there is sufficient budget the definedto build the solution. requirements. 2 4. Requirements Bundles Requirement bundles are used to group a set ofrequirements together for build, test, and deployment. Bundles may also be used for process improvement andorganizational change teams. For agile development, bundles are used for managingrequirements for a Sprint or iteration. Bundles may be baselined and any additions or changeswill be controlled through change management. Functional requirements may only be placed in one bundle,supplemental requirements may be placed in multiplebundles.3 5. Project Retrospective The purpose of the project retrospective is to closethe project and record lessons learned. 4 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 SatisfactionConfidential - Not for External Distribution 5 7. Bundle Lifecycle EventsChange BundlesDefects RequestsLifecycleEvent TestParticipantsValidationsScenariosTest Cases Confidential - Not for External Distribution 6 8. Stakeholder Participation Requirements have many sources. They may come from anyone with an interest inthe outcome of the project. Customers, partners, end users, and domain expertsare some sources of requirements; so too are management, project teammembers, business policies, and regulatory agencies. It is important to know how to determine who the sources should be, how to getaccess to those sources, and how to elicit information from them. The individualswho serve as primary sources for this information are referred to as stakeholdersin the project. If you are developing an information system to be used internally within yourcompany, you may include people with end-user experience and business domainexpertise in your development team. Very often you will start the discussions at abusiness-model level rather than at a system level. If you are developing a productto be sold to a marketplace, you may make extensive use of your marketing peopleto better understand the needs of customers in that market. Requirements may be elicited through activities such as interviewing,brainstorming, conceptual prototyping, using questionnaires, and performingcompetitive analysis. The result of requirements elicitation is a list of requests orneeds that are described textually and graphically and that have been givenpriority relative to one another.Confidential - Not for External Distribution7