<Company Name> <Project Name> Project or Software Development Plan

Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brac ets and displa!ed in blue italics "st!le#$nfo%lue& is included to provide guidance to the author and should be deleted before publishing the document. ' paragraph entered following this st!le will automaticall! be set to normal "st!le#%od! Text&.( [To customi)e automatic fields "which displa! a gra! bac ground when selected&* select +ile,Properties and replace the Title* -ub.ect and /ompan! fields with the appropriate information for this document. 'fter closing the dialog* automatic fields ma! be updated throughout the document b! selecting 0dit,-elect 'll "or /trl1'& and pressing +2* or simpl! clic on the field and press +2. This must be done separatel! for 3eaders and +ooters. 'lt1+2 will toggle between displa!ing the field names and the field contents. -ee 4ord help for more information on wor ing with fields.(

<Project Name> Software Development Plan <doc ment identifier>

Version: <1.0> Date: <dd/mmm/yy>

Revision History
Date <dd/mmm/yy> Version <!.!> <details> Description <name> Author

"onfidential

<"ompany Name># 1$$$

Pa%e & of $

<Project Name> Software Development Plan <doc ment identifier>

Version: <1.0> Date: <dd/mmm/yy>

a!le of Contents
1. 'ntrod ction 1.1 P rpose 1.& Scope 1.) Definitions# *cronyms and *++reviations 1., -eferences .Partial/ 1.( 0verview &. Project 0verview &.1 Project p rpose# scope and o+jectives &.& *ss mptions and constraints &.) Project delivera+les &., 2vol tion of t3e Software Development Plan ). Project 0r%ani4ation ).1 0r%ani4ational Str ct re ).& 2!ternal 'nterfaces .0ptional/ ).) -oles and -esponsi+ilities ,. 5ana%ement Process ,.1 Project 2stimates ,.& Project Plan ,.&.1 P3ase Plan ,.&.& 'teration 0+jectives .0ptional/ ,.&.) -eleases .0ptional/ ,.&., Project Sc3ed le ,.&.( Project -eso rcin% ,.&.1 7 d%et ,.) 'teration Plans .0ptional/ ,., Project 5onitorin% and control ,.,.1 -e8 irements mana%ement plan ,.,.& Sc3ed le control plan ,.,.) 7 d%et control plan .0ptional/ ,.,., : ality control plan .0ptional/ ,.,.( -eportin% Plan .0ptional/ ,.,.1 5eas rement Plan .0ptional/ ,.( -is; 5ana%ement plan ,.1 "lose<o t plan (. =ec3nical process plans (.1 Development "ase .0ptional/ (.& 5et3ods# tools and tec3ni8 es (.) 'nfrastr ct re plan .0ptional/ (., Prod ct acceptance plan .0ptional/ 1. S pportin% process plans 1.1 "onfi% ration mana%ement plan 1.& 2val ation plan 1.) Doc mentation plan .0ptional/ "onfidential <"ompany Name># 1$$$ ( ( ( ( ( 1 1 1 1 1 1 1 1 1 1 1 1 6 6 6 6 6 6 6 6 6 6 6 9 9 9 9 9 9 9 9 9 9 9 9 9 $ $ Pa%e ) of $

<Project Name> Software Development Plan <doc ment identifier> 1., : ality ass rance plan .0ptional/ 1.( Pro+lem resol tion plan .0ptional/ 1.1 S +contractor mana%ement plan .0ptional/ 1.6 Process improvement plan .0ptional/ 6. *dditional plans .0ptional/ 9. *nne!es $. 'nde!

Version: <1.0> Date: <dd/mmm/yy>

$ $ $ $ $ $ $

"onfidential

<"ompany Name># 1$$$

Pa%e , of $

<Project Name> Software Development Plan <doc ment identifier>

Version: <1.0> Date: <dd/mmm/yy>

Project or Software Development Plan

1. "ntro#$ction
[The introduction of the Project or Software Development Plan should provide an overview of the entire document. $t should include the purpose* scope* definitions* acron!ms* abbreviations* references and overview of this Project or Software Development Plan.( 1.1 P$rpose [-pecif! the purpose of this Project or Software Development Plan.( Scope [' brief description of the scope of this Project or Software Development Plan5 what Pro.ect"s& it is associated with* and an!thing else that is affected or influenced b! this document.( Definitions' (cronyms an# (!!reviations [This subsection should provide the definitions of all terms* acron!ms* and abbreviations required to interpret properl! the Project or Software Development Plan. This information ma! be provided b! reference to the pro.ect 6lossar!.( References *Partial+ [This subsection should provide a complete list of all documents referenced elsewhere in the Project or Software Development Plan. 0ach document should be identified b! title* report number "if applicable&* date* and publishing organi)ation. -pecif! the sources from which the references can be obtained. This information ma! be provided b! reference to an appendix or to another document. +or the -oftware 7evelopment Plan* the list of referenced artifacts should include: "onfidential $teration Plans Requirements 8anagement Plan 8easurement Plan Ris 8anagement Plan 7evelopment /ase %usiness 8odeling 6uidelines User $nterfaces 6uidelines Use /ase 8odeling 6uidelines 7esign 6uidelines Programming 6uidelines Test 6uidelines 8anual -t!le 6uide $nfrastructure Plan Product 'cceptance Plan /onfiguration 8anagement Plan <"ompany Name># 1$$$ Pa%e ( of $

1.%

1.&

1.)

<Project Name> Software Development Plan <doc ment identifier> 1., 0valuation Plan 7ocumentation Plan 9ualit! 'ssurance Plan Problem Resolution Plan -ub1contractor 8anagement Plan Process $mprovement Plan (

Version: <1.0> Date: <dd/mmm/yy>

-verview [This subsection should describe what the rest of the Project or Software Development Plan contains and explain how the document is organi)ed.(

%.
%.1

Project -verview
Project p$rpose' scope an# o!jectives [' brief description of the purpose and ob.ectives of this pro.ect* and a brief description of what deliverables the pro.ect is expected to deliver.( (ss$mptions an# constraints [' list of assumptions that this plan is based on* and an! constraints "e.g. budget* staff* equipment* schedule& that appl! to the pro.ect.( Project #elivera!les [Tabular list of the artifacts to be created during the pro.ect* with target deliver! dates.( .vol$tion of t/e Software Development Plan [Table of proposed versions of the Project or software development plan* and the criteria for the unscheduled revision and reissue of this plan.(

%.%

%.&

%.)

&.
&.1

Project -r0ani1ation
-r0ani1ational Str$ct$re [7escribe the organi)ational structure of the pro.ect team* including management and other review authorities.( .2ternal "nterfaces *-ptional+ [7escribe how the pro.ect interfaces with external groups. +or each external group* identif! the internal:external contact names.( Roles an# Responsi!ilities [$dentif! the pro.ect organi)ational units that will be responsible for each of the core wor flows* wor flow details* and supporting processes.(

&.%

&.&

).
).1

3ana0ement Process
Project .stimates [Provide the estimated cost and schedule for the pro.ect* as well as the basis for those estimates* and the points:circumstances in the pro.ect when re1estimation will occur.( <"ompany Name># 1$$$ Pa%e 1 of $

"onfidential

<Project Name> Software Development Plan <doc ment identifier> ).% 4.2.1 Project Plan Phase Plan [$nclude the following: 4or brea down structure.

Version: <1.0> Date: <dd/mmm/yy>

' timeline or 6antt chart showing the allocation of time to the pro.ect phases:iterations. $dentif! ma.or milestones with their achievement criteria

7efine an! important release points and demos( 4.2.2 Iteration Objectives [Optional] [;ist the ob.ectives to be accomplished for each of the iterations.( Releases [Optional] [%rief descriptions of each software release* whether demo* beta* etc.( Project Schedule [7iagrams:tables showing target dates for completion of iterations and phases* release points* demos* and other milestones.( Project Resourcin

4.2.3

4.2.4

4.2.5

4.2.5.1 Staffing Plan [Optional] [$dentif! here the numbers and t!pe of staff required "including and special s ills or experience&* scheduled b! pro.ect phase or iteration.( 4.2.5.2 Resource Acquisition Plan [7escribe how !ou will approach finding and acquiring the staff needed for the pro.ect.( [<ptional( 4.2.5.3 Training Plan [;ist an! special training pro.ect team members will require* with target dates for when this training should be completed.( [<ptional( 4.2.! "ud et ['llocation of costs against the 4%- and the Phase Plan.( "teration Plans *-ptional+ [0ach iteration plan will be enclosed in this section b! reference.( Project 3onitorin0 an# control Re#uire$ents $ana e$ent plan [0nclosed b! reference( Schedule control plan [7escribes the approach to be ta en to monitor progress against the planned schedule and how to ta e corrective action when required.(

).&

).) 4.4.1

4.4.2

"onfidential

<"ompany Name># 1$$$

Pa%e 6 of $

<Project Name> Software Development Plan <doc ment identifier> 4.4.3

Version: <1.0> Date: <dd/mmm/yy>

"ud et control plan [Optional] [7escribes the approach to be ta en to monitor spending against the pro.ect budget and how to ta e corrective action when required.( %ualit& control plan [Optional] [7escribe the timing and methods to be used to control the qualit! of the pro.ect deliverables and how to ta e corrective action when required.( Reportin Plan [Optional] [7escribes internal and external reports to be generated* and the frequenc! and distribution of publication.( 'easure$ent Plan [Optional] [0nclosed b! reference( Ris4 3ana0ement plan Close6o$t plan [7escribe the activities for the orderl! completion of the pro.ect* including staff reassignment* archiving of pro.ect materials* post1mortem debriefings and reports etc.(

4.4.4

4.4.5

4.4.!

)., ).5

,.
,.1

ec/nical process plans

Development Case *-ptional+ [0nclosed b! reference( 3et/o#s' tools an# tec/ni7$es [;ists the documented pro.ect technical standards etc b! reference: %usiness 8odeling 6uidelines User1$nterface 6uidelines Use1/ase 8odeling 6uidelines 7esign 6uidelines Programming 6uidelines Test 6uidelines 8anual -t!le guide(

,.%

,.&

"nfrastr$ct$re plan *-ptional+ [0nclosed b! reference( Pro#$ct acceptance plan *-ptional+ [0nclosed b! reference(

,.)

5.
5.1

S$pportin0 process plans

Confi0$ration mana0ement plan [0nclosed b! reference( <"ompany Name># 1$$$ Pa%e 9 of $

"onfidential

<Project Name> Software Development Plan <doc ment identifier> 5.%

Version: <1.0> Date: <dd/mmm/yy>

.val$ation plan [Part of the -7P: describes the pro.ect=s plans for product evaluation* and covers the techniques* criteria* metrics and procedures used for evaluation > this will include wal throughs* inspections and reviews. Note that this is in addition to the Test Plan* which is not enclosed in the -7P.( Doc$mentation plan *-ptional+ [0nclosed b! reference( 8$ality ass$rance plan *-ptional+ [0nclosed b! reference( Pro!lem resol$tion plan *-ptional+ [0nclosed b! reference( S$!contractor mana0ement plan *-ptional+ [0nclosed b! reference( Process improvement plan *-ptional+ [0nclosed b! reference(

5.&

5.)

5.,

5.5

5.9

9. :. ;.

(##itional plans *-ptional+

['dditional plans if required b! contract or regulations.(

(nne2es
['dditional material of use to the reader of the -7P.(

"n#e2

"onfidential

<"ompany Name># 1$$$

Pa%e $ of $