<Company Name>

<Project Name>
Software Development Plan (Small Project)
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 in *icrosoft +ord "which displa! a gra! bacground when selected&, select
-ile.Properties and replace the Title, /ub0ect and 1ompan! fields with the appropriate information for
this document. 'fter closing the dialog, automatic fields ma! be updated throughout the document b!
selecting 2dit./elect 'll "or 1trl3'& and pressing -4, or simpl! clic on the field and press -4. This must
be done separatel! for 5eaders and -ooters. 'lt3-4 will toggle between displa!ing the field names and the
field contents. /ee +ord help for more information on woring with fields.(
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
evision !istory
Date Version Description Author
<ddmmm!!> <#.#> <details> <name>
$onfidential <$ompan! Name>% &01' Pa(e & of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
"a#le of Contents
1. Introduction...........................................................................................................................................................4
6.6 Purpose...........................................................................................................................................................7
6.8 /cope...............................................................................................................................................................7
6.9 :efinitions, 'cron!ms, and 'bbreviations.....................................................................................................7
6.7 References.......................................................................................................................................................7
6.; <verview.........................................................................................................................................................;
2. Project Overview...................................................................................................................................................5
8.6 Pro0ect Purpose, /cope, and <b0ectives.........................................................................................................;
8.8 'ssumptions and 1onstraints.........................................................................................................................;
8.9 Pro0ect :eliverables.......................................................................................................................................;
8.7 2volution of the /oftware :evelopment Plan.................................................................................................;
3. Project Organization............................................................................................................................................5
9.6 <rgani)ational /tructure................................................................................................................................;
9.8 2xternal $nterfaces.........................................................................................................................................=
9.9 Roles and Responsibilities..............................................................................................................................=
4. anage!ent Process............................................................................................................................................"
7.6 Pro0ect 2stimates............................................................................................................................................>
7.8 Pro0ect Plan....................................................................................................................................................>
'.&.1 P)ase Plan...............................................................................................................................................*
'.&.& +teration ,-jectives.................................................................................................................................*
'.&.. /eleases...................................................................................................................................................*
'.&.' Project Sc)ed"le......................................................................................................................................*
'.&.0 Project /eso"rcin(..................................................................................................................................*
'.&.1 2"d(et.....................................................................................................................................................*
7.9 $teration Plans................................................................................................................................................>
7.7 Pro0ect *onitoring and 1ontrol.....................................................................................................................>
5. Anne#es..................................................................................................................................................................$
$onfidential <$ompan! Name>% &01' Pa(e . of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
Software Development Plan (Small Project)
1. $ntro%&ction
[The introduction of the Software Development Plan provides an overview of the entire document. $t
includes the purpose, scope, definitions, acron!ms, abbreviations, references, and overview of this
Software Development Plan.(
1.1 P&rpose
[/pecif! the purpose of this Software Development Plan. The text below is provided as an example. (
3)e p"rpose of t)e /oftware :evelopment Plan is to (at)er all information necessar! to control t)e project.
+t descri-es t)e approac) to t)e development of t)e software and is t)e top4level plan (enerated and "sed -!
mana(ers to direct t)e development effort.
3)e followin( people "se t)e /oftware :evelopment Plan:
3)e project !anager "ses it to plan t)e project sc)ed"le and reso"rce needs% and to trac5
pro(ress a(ainst t)e sc)ed"le.
Project tea! !e!%ers "se it to "nderstand w)at t)e! need to do% w)en t)e! need to do it% and
w)at ot)er activities t)e! are dependent "pon.
1.' Scope
[' brief description of the scope of this Software Development Plan? what Pro0ect"s& it is associated with
and an!thing else that is affected or influenced b! this document. The text below is provided as an
example.(
3)is /oftware :evelopment Plan descri-es t)e overall plan to -e "sed -! t)e <project name> project%
incl"din( deplo!ment of t)e prod"ct. 3)e details of t)e individ"al iterations will -e descri-ed in t)e
+teration Plans.
3)e plans as o"tlined in t)is doc"ment are -ased "pon t)e prod"ct re6"irements as defined in t)e @ision
:ocument.
1.( Definitions) *cronyms) an% *##reviations
[This subsection provides the definitions of all terms, acron!ms, and abbreviations required to properl!
interpret the Software Development Plan. This information ma! be provided b! reference to the pro0ectAs
Blossar!.(
See t)e Project 7lossar!.
1.+ eferences
[This subsection provides a complete list of all documents referenced elsewhere in the Software
Development Plan. $dentif! each document 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 Software Development Plan, the list of referenced artifacts includes:
RUP for /mall Pro0ects +ebsite
$teration Plans
:evelopment 1ase
$onfidential <$ompan! Name>% &01' Pa(e ' of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
@ision
Blossar!
'n! other supporting plans or documentation.
1., -verview
[This subsection describes what the rest of the Software Development Plan contains and explains how the
document is organi)ed. The text below is provided as an example.(
3)is /oftware :evelopment Plan contains t)e followin( information:
Project ,verview 8 provides a description of t)e project9s p"rpose% scope% and o-jectives. +t also defines
t)e delivera-les t)at t)e project is e#pected to deliver.
Project ,r(ani:ation 8 descri-es t)e or(ani:ational str"ct"re of t)e project team.
;ana(ement Process 8 e#plains t)e estimated cost and sc)ed"le% defines t)e major p)ases and milestones
for t)e project% and descri-es )ow t)e project will -e monitored.
<pplica-le Plans and 7"idelines 8 provides an overview of t)e software development process% incl"din(
met)ods% tools and tec)ni6"es to -e followed.
'. Project -verview
'.1 Project P&rpose) Scope) an% -#jectives
[' brief description of the purpose and ob0ectives of this pro0ect and a brief description of what
deliverables the pro0ect is expected to deliver.(
'.' *ss&mptions an% Constraints
[' list of assumptions that this plan is based and an! constraints, for example. budget, staff, equipment,
schedule, that appl! to the pro0ect.(
'.( Project Delivera#les
[' list of the artifacts to be created during the pro0ect, including target deliver! dates. The text below is
provided as an example.(
Delivera-les for eac) project p)ase are identified in t)e Development $ase. Delivera-les are delivered
towards t)e end of t)e iteration% as specified in section 7.8.7 Pro0ect /chedule.
'.+ .vol&tion of t/e Software Development Plan
[' table of proposed versions of the Software Development Plan, and the criteria for the unscheduled
revision and reissue of this plan. The text below is provided as an example.(
3)e /oftware :evelopment Plan will -e revised prior to t)e start of eac) +teration p)ase.
(. Project -r0ani1ation
(.1 -r0ani1ational Str&ct&re
[:escribe the organi)ational structure of the pro0ect team, including management and other review
authorities.(
$onfidential <$ompan! Name>% &01' Pa(e 0 of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
(.' .2ternal $nterfaces
[:escribe how the pro0ect interfaces with external groups. -or each external group, identif! the internal
and external contact names. This should include responsibilities related to deplo!ment and acceptance of
the product.(
(.( oles an% esponsi#ilities
[$dentif! the pro0ect organi)ational units that will be responsible for each of the disciplines, worflow
details, and supporting processes. The text below is provided as an example.(
Person &ationa' (ni)ied Process &o'e
Sall! Slalom% Senior ;ana(er
Project ;ana(er
Deplo!ment ;ana(er
/e6"irements /eviewer
<rc)itect"re /eviewer
$onfi("ration ;ana(er
$)an(e $ontrol ;ana(er
;att ;o("l% VP ,perations
Project /eviewer
/e6"irements /eviewer
3om 3elemar5% Senior Software =n(ineer
S!stem <nal!st
/e6"irements Specifier
>ser +nterface Desi(ner
Software <rc)itect
Desi(n /eviewer
3est ;ana(er
3est <nal!st
and to a lesser e#tent t)e followin( roles:
Desi(ner
+mplementer
$ode /eviewer
+nte(rator
3est Desi(ner
3ester
3ec)nical ?riter
S"san Snow% Software =n(ineer
@enr! @alfpipe% A"nior Software =n(ineer
32D1% Software =n(ineer
32D&% A"nior Software =n(ineer
Desi(ner
+mplementer
$ode /eviewer
+nte(rator
3est Desi(ner
3ester
3ec)nical ?riter
Patric5 Powder% <dministrative <ssistant
/esponsi-le for maintainin( t)e Project we- site%
assistin( t)e Project ;ana(er role in
plannin(sc)ed"lin( activities% and assistin( t)e
$)an(e $ontrol ;ana(er role in controllin(
c)an(es to artifacts. ;a! also provide assistance
to ot)er roles as necessar!.
$onfidential <$ompan! Name>% &01' Pa(e 1 of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
<n!one on t)e project can perform <n! /ole activities.
+. 3ana0ement Process
+.1 Project .stimates
[Provide the estimated cost and schedule for the pro0ect, as well as the basis for those estimates, and the
points and circumstances in the pro0ect when re3estimation will occur.(
+.' Project Plan
[This section contains the schedule and resources for the pro0ect.(
4.2.1 Phase Plan
[$nclude the following:
+or %readown /tructure "+%/& C optional for small pro0ects
a timeline or Bantt chart showing the allocation of time to the pro0ect phases or iterations
identif! ma0or milestones with their achievement criteria
:efine an! important release points and demos.(
4.2.2 Iteration Objectives
[Dist the ob0ectives to be accomplished for each of the iterations.(
4.2.3 Releases
[' brief description of each software release and whether itAs demo, beta, and so on.(
4.2.4 Project Schedule
[:iagrams or tables showing target dates for completion of iterations and phases, release points, demos,
and other milestones.(
4.2.5 Project Resourcing
[$dentif! the numbers and t!pe of staff required here, including an! special sills or experience, scheduled
b! pro0ect phase or iteration.
:escribe how !ou will approach finding and acquiring the staff needed for the pro0ect.
Dist an! special training pro0ect team members will require, with target dates for when this training should
be completed.
'llocation of costs against the +%/ and the Phase Plan.(
4.2.6 Budget
['llocation of costs(
+.( $teration Plans
[2ach iteration plan will be enclosed in this section b! reference.(
+.+ Project 3onitorin0 an% Control
[The following is a checlist of items to consider:
$onfidential <$ompan! Name>% &01' Pa(e * of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
Requirements *anagement : /pecif! the information and control mechanisms which will be
collected and used for measuring, reporting, and controlling changes to the product requirements.
/chedule and %udget 1ontrol::escribe the approach to be taen to monitor spending against the
pro0ect budget and progress against the planned schedule. :escribe how to tae corrective action
when required.
Eualit! 1ontrol::escribe the timing and methods to be used to control the qualit! of the pro0ect
deliverables and how to tae corrective action when required. $nclude techniques, metrics,
criteria, and procedures used for evaluationC this will include walthroughs, inspections, and
reviews. Note that this is in addition to the Test Plan, which is not enclosed in the /oftware
:evelopment Plan.
Reporting and *easurement: :escribe internal and external reports to be generated, and the
frequenc! and distribution of publication. /pecif! which metrics should be collected and wh!.
Ris *anagement: :escribe the approach that will be used to identif!, anal!)e, prioriti)e, monitor
and mitigate riss. $nclude a list of riss and their current status.
Pro0ect 1lose3out: :escribe the activities for the orderl! completion of the pro0ect, including staff
reassignment, archiving of pro0ect materials, post3mortem debriefings and reports, and so forth.
1onfiguration *anagement: :escribe the process b! which problems and changes are submitted,
reviewed, and dispositioned. :escribe how pro0ect or product artifacts are to be named, mared,
and numbered, including hardware, s!stem software, 1ommercial3<ff3The3/helf "1<T/&, plans,
models, components, test software, results and data, executables, and so on. :escribe retention
policies, and the bac3up, disaster, and recover! plans. 'lso describe how the media is to be
retainedConline, offline, media t!pe, and format.
Problem Resolution: :escribe the approach to be taen to resolve disagreements with the
customer, including how to handle schedule slips, scope, and contractual disagreements.
/ubcontractor *anagement: :escribe how subcontractors will be managed.
Process $mprovement Plan: :escribe how the effectiveness of the process will be assessed and
improved.
The text that follows is provided as an example.(
&e*uire!ents anage!ent
3)e re6"irements for t)is s!stem are capt"red in t)e Vision doc"ment. /e6"ested c)an(es to re6"irements
are capt"red in $)an(e /e6"ests% and are approved as part of t)e $onfi("ration ;ana(ement process.
+chedu'e and ,udget -ontro'
=#penses are monitored -! t)e project mana(er% and reported and assessed mont)l!. (See /eportin( and
;eas"rement -elow).
3)e project mana(er maintains a sc)ed"le s)owin( t)e e#pected date of eac) milestone. 3)e line items in
t)e sc)ed"le incl"de wor5 pac5a(es assi(ned to individ"als. =ac) individ"al w)o is assi(ned a wor5
pac5a(e provides Bcompletion information to t)e project mana(er on a wee5l! -asis. $)an(es in t)e
sc)ed"le will -e escalated to t)e project sponsors% w)o will t)en decide w)et)er to alter scope in order to
preserve tar(et completion dates.
.ua'it/ -ontro'
Defects will -e recorded and trac5ed as $)an(e /e6"ests% and defect metrics will -e (at)ered (see
/eportin( and ;eas"rement -elow).
$onfidential <$ompan! Name>% &01' Pa(e C of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
<ll delivera-les are re6"ired to (o t)ro"() t)e appropriate review process% as descri-ed in t)e
Development $ase. 3)e review is re6"ired to ens"re t)at eac) delivera-le is of accepta-le 6"alit!% "sin(
("idelines descri-ed in t)e />P for Small Projects review ("idelines and c)ec5lists.
<n! defects fo"nd d"rin( review w)ic) are not corrected prior to releasin( for inte(ration m"st -e capt"red
as $)an(e /e6"ests so t)at t)e! are not for(otten.
&eporting and easure!ent
>pdated cost and sc)ed"le estimates% and metrics s"mmar! reports% will -e (enerated at t)e end of eac)
iteration.
3)e ;inimal Set of ;etrics% as descri-ed in t)e />P 7"idelines: ;etrics% will -e (at)ered on a wee5l!
-asis. 3)ese incl"de:
=arned val"e for completed tas5s. 3)is is "sed to re4estimate t)e sc)ed"le and -"d(et for t)e remainder of
t)e project% andor to identif! need for scope c)an(es.
3otal defects open and closed D s)own as a trend (rap). 3)is is "sed to )elp estimate t)e effort remainin( to
correct defects.
<cceptance test cases passin( D s)own as a trend (rap). 3)is is "sed to demonstrate pro(ress to
sta5e)olders.
+n addition% overall costs will -e monitored a(ainst t)e project -"d(et.
&is0 anage!ent
/is5s will -e identified in +nception P)ase "sin( t)e steps identified in t)e />P for Small Projects activit!
E+dentif! and <ssess /is5sF. Project ris5 is eval"ated at least once per iteration and doc"mented in t)is
ta-le. 3)e ris5s of t)e (reatest ma(nit"de are listed first in t)e ta-le.
is4 an4in0
(!i0/) 3e%i&m)
5ow)
is4 Description an% $mpact 3iti0ation Strate0y an%6or Contin0ency Plan
-on)iguration anage!ent
<ppropriate tools will -e selected w)ic) provide a data-ase of $)an(e /e6"ests and a controlled versioned
repositor! of project artifacts.
<ll so"rce code% test scripts% and data files are incl"ded in -aselines. Doc"mentation related to t)e so"rce
code is also incl"ded in t)e -aseline% s"c) as desi(n doc"mentation. <ll c"stomer delivera-le artifacts are
incl"ded in t)e final -aseline of t)e iteration% incl"din( e#ec"ta-les.
3)e $)an(e /e6"ests are reviewed and approved -! one mem-er of t)e project% t)e $)an(e $ontrol
;ana(er role.
G"ll -ac5"ps are performed mont)l! and incrementals are performed ni()tl!.
,. *nne2es
['dditional material of use to the reader of the Software Development Plan. Reference or include an!
pro0ect technical standards and plans which appl! to this pro0ect. This t!picall! includes the :evelopment
1ase, plans for infrastructure, and product acceptance. $t also t!picall! includes Programming Buidelines,
:esign Buidelines, and other process guidelines. The text that follows is provided as an example.(
3)e project will follow t)e />P for Small Projects process% as tailored -! t)e project Development $ase.
$onfidential <$ompan! Name>% &01' Pa(e H of 10
<Project Name>
Version: <1.0>
Software Development Plan (Small Project) Date: <ddmmm!!>
<doc"ment identifier>
,t)er applica-le process plans are listed in t)e references section% incl"din( Pro(rammin( 7"idelines.
$onfidential <$ompan! Name>% &01' Pa(e 10 of 10