<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 bracets 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! bacground 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 woring with fields.(
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
Revision History
Date Version Description Author
<dd/mmm/yy> <!.!> <details> <name>
"onfidential <"ompany Name># 1$$$ Pa%e & of $
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
a!le of Contents
1. 'ntrodction (
1.1 Prpose (
1.& Scope (
1.) Definitions# *cronyms and *++reviations (
1., -eferences .Partial/ (
1.( 0verview 1
&. Project 0verview 1
&.1 Project prpose# scope and o+jectives 1
&.& *ssmptions and constraints 1
&.) Project delivera+les 1
&., 2voltion of t3e Software Development Plan 1
). Project 0r%ani4ation 1
).1 0r%ani4ational Strctre 1
).& 2!ternal 'nterfaces .0ptional/ 1
).) -oles and -esponsi+ilities 1
,. 5ana%ement Process 1
,.1 Project 2stimates 1
,.& Project Plan 6
,.&.1 P3ase Plan 6
,.&.& 'teration 0+jectives .0ptional/ 6
,.&.) -eleases .0ptional/ 6
,.&., Project Sc3edle 6
,.&.( Project -esorcin% 6
,.&.1 7d%et 6
,.) 'teration Plans .0ptional/ 6
,., Project 5onitorin% and control 6
,.,.1 -e8irements mana%ement plan 6
,.,.& Sc3edle control plan 6
,.,.) 7d%et control plan .0ptional/ 9
,.,., :ality control plan .0ptional/ 9
,.,.( -eportin% Plan .0ptional/ 9
,.,.1 5easrement Plan .0ptional/ 9
,.( -is; 5ana%ement plan 9
,.1 "lose<ot plan 9
(. =ec3nical process plans 9
(.1 Development "ase .0ptional/ 9
(.& 5et3ods# tools and tec3ni8es 9
(.) 'nfrastrctre plan .0ptional/ 9
(., Prodct acceptance plan .0ptional/ 9
1. Spportin% process plans 9
1.1 "onfi%ration mana%ement plan 9
1.& 2valation plan $
1.) Docmentation plan .0ptional/ $
"onfidential <"ompany Name># 1$$$ Pa%e ) of $
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
1., :ality assrance plan .0ptional/ $
1.( Pro+lem resoltion plan .0ptional/ $
1.1 S+contractor mana%ement plan .0ptional/ $
1.6 Process improvement plan .0ptional/ $
6. *dditional plans .0ptional/ $
9. *nne!es $
$. 'nde! $
"onfidential <"ompany Name># 1$$$ Pa%e , of $
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
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.(
1.% 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.(
1.& 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!.(
1.) 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:
$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
"onfidential <"ompany Name># 1$$$ Pa%e ( of $
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
0valuation Plan
7ocumentation Plan
9ualit! 'ssurance Plan
Problem Resolution Plan
-ub1contractor 8anagement Plan
Process $mprovement Plan (
1., -verview
[This subsection should describe what the rest of the Project or Software Development Plan contains and
explain how the document is organi)ed.(
%. Project -verview
%.1 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.(
&. Project -r0ani1ation
&.1 -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 worflows* worflow
details* and supporting processes.(
). 3ana0ement Process
).1 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.(
"onfidential <"ompany Name># 1$$$ Pa%e 1 of $
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
).% Project Plan
4.2.1 Phase Plan
[$nclude the following:
4or breadown structure.
' 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.(
4.2.3 Releases [Optional]
[%rief descriptions of each software release* whether demo* beta* etc.(
4.2.4 Project Schedule
[7iagrams:tables showing target dates for completion of iterations and phases* release points* demos* and
other milestones.(
4.2.5 Project Resourcin
4.2.5.1 Staffing Plan [Optional]
[$dentif! here the numbers and t!pe of staff required "including and special sills 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.! "udet
['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
4.4.1 Re#uire$ents $anae$ent plan
[0nclosed b! reference(
4.4.2 Schedule control plan
[7escribes the approach to be taen to monitor progress against the planned schedule and how to tae
corrective action when required.(
"onfidential <"ompany Name># 1$$$ Pa%e 6 of $
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
4.4.3 "udet control plan [Optional]
[7escribes the approach to be taen to monitor spending against the pro.ect budget and how to tae
corrective action when required.(
4.4.4 %ualit& control plan [Optional]
[7escribe the timing and methods to be used to control the qualit! of the pro.ect deliverables and how to
tae corrective action when required.(
4.4.5 Reportin Plan [Optional]
[7escribes internal and external reports to be generated* and the frequenc! and distribution of
publication.(
4.4.! 'easure$ent Plan [Optional]
[0nclosed b! reference(
)., Ris4 3ana0ement plan
).5 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.(
,. ec/nical process plans
,.1 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. S$pportin0 process plans
5.1 Confi0$ration mana0ement plan
[0nclosed b! reference(
"onfidential <"ompany Name># 1$$$ Pa%e 9 of $
<Project Name>
Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<docment identifier>
5.% .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 walthroughs* inspections and reviews. Note
that this is in addition to the Test Plan* which is not enclosed in the -7P.(
5.& Doc$mentation plan *-ptional+
[0nclosed b! reference(
5.) 8$ality ass$rance plan *-ptional+
[0nclosed b! reference(
5., Pro!lem resol$tion plan *-ptional+
[0nclosed b! reference(
5.5 S$!contractor mana0ement plan *-ptional+
[0nclosed b! reference(
5.9 Process improvement plan *-ptional+
[0nclosed b! reference(
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 $