Plan

Projectmanagement.com
Requirements Management Plan
Identifying, managing, and verifying requirements for [Project Name]

projectmanagement.com 11 11 !reedom "rive # $$ Reston, %& '$$ 1

'
Overview
This plan will guide us through the following aspects of requirements management: Collection- gathering the basic needs of stakeholders Categorization categorizing those needs Prioritization prioritizing those needs and identif ing !must haves" Tracing tracking how those needs are addressed throughout the life of the pro#ect Change $anagement the process b which we will change our requirements as needs change %erification how we will verif that requirements have been met

Plan

This document is to be used a tool for communications& giving all stakeholders a view on how this process is managed for 'Pro#ect (ame)*

+equirements Collection
"uring t(is p(ase, t(e emp(asis is on capturing as many perceived requirements as possi)le from all valid sta*e(olders. Not all of t(e needs +e identify (ere +ill end up as actual ,requirements-, )ut t(ey +ill )e identified and understood. [Collection Method 1] [.o+ it +ill )e used, +it( +(ic( groups, and +(y] /ou may +is( to pull te0t for t(is section from gantt(ead on1 2rainstorming %oice of t(e 3ustomer 3ustomer Needs &nalysis

&lso consider using surveys and intervie+s of different types 4people at different levels, in different roles, people deeply involved in t(e )usiness process you are addressing, sponsors, e0ecutives, etc.5. [Collection Method 2] [.o+ it +ill )e used, +it( +(ic( groups, and +(y] [Collection Method 3] [.o+ it +ill )e used, +it( +(ic( groups, and +(y]

&s +e identify eac( requirement, +e +ill document t(e1

Plan
Requirement name Requirement description 7(e sta*e(older to +(om it is important 8ome measure of criticality 4(o+ important it is )ased on a quantified vie+ of ,(aving it- versus ,N97 (aving it-5 &cceptance 3riteria 4a quantified +ay of understanding t(e specifics of t(e requirement. In ot(er +ords, (o+ +ill +e *no+ it:s )een fulfilled;5

+equirements Categorization
"uring t(is p(ase, +e +ill logically group requirements. Requirements +ill )e grouped into t(e follo+ing categories1 [Requirement Category 1] [<(y t(is category is important and ma*es sense] 3ategories often include1 !unctional Requirements 7ec(nical Requirements 7raining Requirements =uality Requirements Performance Requirements 8upport Requirements Maintenance Requirements [Requirement Category 2] [<(y t(is category is important and ma*es sense] [Requirement Category 3] [<(y t(is category is important and ma*es sense]

+equirements Prioritization
9ur approac( to prioriti>ing requirements +ill )e to [descri)e approac(] 9ften t(is is a matter of +or*ing +it( t(e project sponsors to ma*e some decisions. 7(e follo+ing gantt(ead tec(niques can )e (elpful and some of t(e te0t from t(e site can )e used in t(is document as +ell. "ecision?ma*ing tec(niques 9ne important aspect of prioriti>ation is t(e relations(ip )et+een requirements. 8ometimes you (ave to do one t(ing if you do anot(er. 8ometimes t(e )est +ay to do t(is is to conduct a 3ustomer 8atisfier &nalysis, and loo* at t(ings more )roadly t(an you +ould if you are just eyeing individual requirements.

@
+equirements Traceabilit

Plan

3ertain requirement attri)utes need to )e trac*ed across t(e project life cycle A so t(at you can relate t(em )ac* to +(at you are actually doing on t(e project. <e +ill trac* t(ose attri)utes and maintain a consistent understanding of (o+ t(ey are )eing addressed during t(e course of t(e project. 2eginning on [date] +e +ill trac* all requirements, t(eir source, t(e project o)jective t(ey support, t(e part of t(e <28 +(ere it is addressed, +(en it is verified and validated. <e +ill use [requirements management system B or requirements tracea)ility matri0 /] to manage data on eac( requirement. [7eam Mem)er] +ill )e responsi)le for t(e trac*ing of requirements. .eCs(e +ill report any impacts to project requirements )ased on current performance to [Project Manager] +it(in '@ (ours of a status c(ange. [!urt(er descri)e t(e tools and met(ods used to trace requirements (ere]

Requirements Traceability Matrix

+equirement

Priorit

Categor

,ource

+elated -., Code

Change $anagement
9ur project:s requirements +ill c(ange over time and t(ose c(anges must )e managed in order to ensure a successful outcome. ["escri)e t(e process for ma*ing c(anges and supporting materials.] .ere are e0amples of c(ange request policies and systems t(at could )e a part of t(is description. 3(ange Management Policy and Process 3(ange Management 8tandards

D
+equirements %erification

Plan

["escri)e met(ods and metrics used to verify requirements, (o+ t(eir ac(ievement +ill )e measured, tested, etc.]

Requirements Verification Matrix

+equirement

-hat will be measured / 0metric1

-hen it will be measured / 0date1

-ho will measure it /

2cheived /