<<Project Name>>

Development Plan
Customer Name
Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that
should be placed in each section of this template. Then delete the Guidance and
replace the placeholder within <<Begin tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
'eading ( ) Arial Bold (* font
'eading + ) Arial Bold ,talic (- font
'eading . ) Arial Bold (. font
'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
345+(5+3(-
2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MAKES NO ARRANTIES! E"PRESS OR
IMP#IED! IN T$IS DOC%MENT&
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
345+(5+3(-
Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title 1e%elopment 0lan
Author
6reation 1ate
8ast 9pdated
345+(5+3(-
Table of Contents
$ummar"..........................................................................................................................
1e%elopment :b;ecti%es.................................................................................................
:%erall 1eli%er" $trateg"................................................................................................
Tradeoff Approach...........................................................................................................
<e" 1esign Goals...........................................................................................................-
1e%elopment and Build =n%ironment............................................................................-
Guidelines and $tandards...............................................................................................-
7aming.......................................................................................................................>
6oding........................................................................................................................>
2ersioning and $ource 6ontrol.......................................................................................>
1ail" Build 0rocess........................................................................................................>
Roadmap.........................................................................................................................*
6omponents....................................................................................................................*
6omponent 1escriptions........................................................................................*
6omponent Teams..................................................................................................*
6omponent 1esign.................................................................................................*
6omponent Ac?uisition and 1e%elopment.............................................................*
6omponent @ualit"................................................................................................4
6onfiguration and 1e%elopment Aanagement Tools.....................................................4
Tool (..........................................................................................................................B
1escription.............................................................................................................B
Team.......................................................................................................................B
Risk Aanagement...................................................................................................B
Tool +..........................................................................................................................B
1escription.............................................................................................................B
Team.......................................................................................................................B
Risk Aanagement...................................................................................................B
Reuse..............................................................................................................................B
1esign 0atterns...............................................................................................................C
1e%elopment Team Training..........................................................................................C
1e%elopment Team $upport...........................................................................................C
345+(5+3(- 3
%Intro'uct(on to t)e Template
Descr(pt(on& The 'evelopment (lan describes the solution development process
used for the pro)ect. This plan compliments the functional specifications that provide
the technical details of what will be built. This plan provides consistent guidelines and
processes to the teams creating the solution.
*ust(+(cat(on, 'ocumenting a development process indicates that the team has
discussed and concluded on a consistent structure and direction to be used during
the development process. This documentation allows developers to be productivel
focused on creating the solution. 'evelopment guidelines and standards promote
meaningful communication among the team*s+, as the will reference a common
approach and processes. ,t also facilitates reuse among different groups and
minimi-es the dependenc upon one individual or group.
.Team Role Pr(mar-, Development. The 'evelopment /ole manages the process
of creating the development plan. The focus of the 'evelopment /ole during this
process is to consider how ke aspects of the development process should be
undertaken. This ma include incorporating e0isting standards and protocols *coding
standards, architecture references, etc.+ that are re1uired b participating
organi-ations. ,t ma also include establishing trade2off priorities and budget
restrictions.
Team Role Secon'ar-, Pro/ram Mana/ement provides input to the overall deliver
strateg, ke design goals, and trade2off approach. As (rogram Management is
responsible for managing the overall solution design, it must verif that the
development plan can meet the goals and re1uirements of the entire solution and
that ke development goals and processes are captured and prioriti-ed appropriatel.
Test needs to understand the development approach and how the will work with the
development team. Test will need details on the dail build process and the order in
which components will be built in order to develop a viable test plan.34
345+(5+3(-
Summar-
%Descr(pt(on, (rovide an overall summar of the contents of this document.
*ust(+(cat(on, #ome readers ma need to know onl the highlights of the plan, and
summari-ing creates that user view. ,t also enables the full reader to know the
essence of the document before the e0amine the details.4
<<Begin tet here!!
Development O0ject(ves
%Descr(pt(on, The 'evelopment 5b)ectives section defines the primar drivers that
were used to create the development approach and the ke ob)ectives of that
approach.
*ust(+(cat(on, ,dentifing the drivers and development ob)ectives signals to the
customer that Microsoft has carefull considered the situation and created an
appropriate development approach.4
<<Begin tet here!!
Overall Del(ver- Strate/-
%Descr(pt(on, The 5verall 'eliver #trateg section describes the overall approach
to delivering the solution. (otential approaches could be a staged deliver, 6depth2
first,7 6breadth2first,7 6features then performance,7 etc.
*ust(+(cat(on, Considering and concluding on deliver options demonstrates that the
team has assessed the business and technolog environments and matched those
with an appropriate deliver strateg.
.Team Role Pr(mar-, Pro'uct Mana/ement contributes to the overall deliver
strateg since it must align with customer e0pectations. Pro/ram Mana/ement
provides direction for the overall deliver strateg based on the content of the
vision$scope document. Development provides input to the overall deliver strateg
based on the content of the functional specifications documents.
Team Role Secon'ar-, Test uses the overall deliver strateg to structure their test
plan.34
<<Begin tet here!!
Tra'eo++ Approac)
%Descr(pt(on, The Tradeoff Approach section defines the approach that will be taken
for making design and implementation trade2off decisions *e.g. trade features for
schedule, trade features for performance, etc.+.
345+(5+3(- +
*ust(+(cat(on, The content of this section sets the guidance for making trade2offs
throughout the pro)ect. These trade2offs should be established up front with the
customer and then be reassessed throughout the life of the pro)ect.4
<<Begin tet here!!
Ke- Des(/n 1oals
%Descr(pt(on, The 8e 'esign 9oals section identifies the ke design goals and their
priorit. :0amples of design goals include&
'esign for operabilit
'esign for securit
'esign to ensure sufficient customer return on investment
*ust(+(cat(on, ,dentifing and prioritising design goals ensures that the team has
carefull considered the business re1uirements and converted those into a
framework that provides conte0t for the overall development strateg.4
<<Begin tet here!!
Development an' 2u(l' Env(ronment
%Descr(pt(on, Te 'evelopment and Build :nvironment section describes the
development and build environment and how it will be managed. ,nclude information
on such things as source code control tools, design tools re1uirements, 5#, or other
on2board software installed. ;ou ma put the description of the environment
infrastructure in the 'eploment plan instead.
*ust(+(cat(on, A plan for creating the development and build environment will ensure
that it will be put in place before development begins. A plan for managing the
environment ensures that it is stable and supportive to the development and build
processes.
.Team Role Pr(mar-, Release Mana/ement is responsible for ensuring that the
development and build environment aligns with the e0isting and planned
infrastructure. ,n situations where release provides specific input into the
development plan, then traceabilit of this input must be mapped back to the
deploment plan.
Team Role Secon'ar-, Development will verif that the development and build
environment meets the needs for their tools.34
<<Begin tet here!!
1u('el(nes an' Stan'ar's
%Descr(pt(on, The 9uidelines and #tandards section lists and provides references to
all standards and guidelines to be used b the pro)ect. Add addition sub2sections as
needed for the pro)ect.
345+(5+3(- .
*ust(+(cat(on& :stablishing guidelines and standards before development work
begins ensures that all development team members are made aware of the
e0pectations placed upon them.4
Naming
%Descr(pt(on, The <aming section lists and provides references to the naming
conventions used for the pro)ect.4
<<Begin tet here!!
Coding
%Descr(pt(on, The Coding section lists and provides references to the coding
conventions used for the pro)ect.4
<<Begin tet here!!
3ers(on(n/ an' Source Control
%Descr(pt(on, The !ersioning and #ource Control section describes how versioning
and source control will occur. This should include identification of the specific tool that
will be used and how developers are e0pected to use it.
*ust(+(cat(on& :stablishing these processes before development work begins
ensures that all development team members are made aware of the e0pectations
placed upon them.4
<<Begin tet here!!
Da(l- 2u(l' Process
%Descr(pt(on, The 'ail Build (rocess section describes the incremental and iterative
approach for developing code as well as for 6builds7 of hardware and software
components. ,t also describes how the dail build process will be implemented.
*ust(+(cat(on, The dail build process ensures the stabilit of the total solution,
through the use of ample test data, before it is released into production. =re1uent
builds provide validation that all of the code is compatible and allows the various sub2
teams to continue their development and testing iterations.
.Team Role Pr(mar-, Development drives the dail build process. This should be
based on well2defined, documented processes in con)unction with versioning and
source control.
Team Role Secon'ar-, Test needs to understand the dail build process and
specificall how the will receive updated builds. This information will be incorporated
into the Test plan. Release Mana/ement provides input to the dail build process
since the are responsible for the infrastructure that makes the builds possible.34
<<Begin tet here!!
345+(5+3(- -
Roa'map
%Descr(pt(on, The /oadmap section describes the order in which the solution
components will be delivered.4
<<Begin tet here!!
6omponent 1escription 6ritical 1ates Team (:wner)
Components
%Descr(pt(on, The Components section provides a high2level description of the set of
solution components and how the will be developed.
*ust(+(cat(on& This section provides the work breakdown structure for the
development process. ,t ensures that all development team members are clear on
their role and responsibilities, the methods to be used for their tasks, and how the
tasks results will be assessed for 1ualit.4
Component Descr(pt(ons
%Descr(pt(on, The Component 'escriptions section describes all ke components in
the solution, including their purpose, histor, and references to their specifications.4
<<Begin tet here!!
Component Teams
%Descr(pt(on, The Component Teams section identifies who will be responsible for
developing each component.4
<<Begin tet here!!
Component Des(/n
%Descr(pt(on, The Component 'esign section provides an outline of the design
process for each component.4
<<Begin tet here!!
Component Ac4u(s(t(on an' Development
%Descr(pt(on& The Component Ac1uisition and 'evelopment section identifies an
components that are to be ac1uired, identifies their sources, and shows how the fit
into the solution. ,t also describes the processes and the procedures used to
integrate ac1uired and built solution components together.4
<<Begin tet here!!
345+(5+3(- >
Component 5ual(t-
%Descr(pt(on, The Component >ualit section describes the measures for ensuring
that all components meet 1ualit e0pectations. ,t includes a description of the
following processes&
'esign /eview
Code /eview
Component Testing4
<<Begin tet here!!
Con+(/urat(on an' Development Mana/ement Tools
%Descr(pt(on, The Configuration and 'evelopment Management Tools section
identifies all the development tools the team will emplo over the pro)ect?s lifespan.
This should include tools for all phases and dimensions of the pro)ect *development,
testing, documentation, support, operations, deploment, etc.+
*ust(+(cat(on& All team members should consistentl appl the development tools.
#electing the tools during the planning phase ensures this consistenc.4
<<Begin tet here!!
Sample tool table:
Aicrosoft ,nternet
=plorer
Aicrosoft ,nternet
,nformation $er%er
Aicrosoft 6:AD Aicrosoft $@8
$er%er
9ser $er%ice
6omponents
Tools: 2isual$tudio.7et# 2isual
Basic *.3#
2isual 6DD *.3
Technolog": 1'TA8#
2B$cript# Acti%eE
6ontrols
Tools: 2isual$tudio.7et
Technolog": A$0.7et# 2B$cript
7ot Applicable 7ot Applicable
Business $er%ice
6omponents
Tools: 2isual Basic *.3
Technolog": Acti%eE 6ontrols
7ot Applicable Tools: 2isual Basic *.3
Technolog": 6:A# Acti%eE
1ata :b;ects (A1:)
7ot Applicable
1ata $er%ice
6omponents
7ot Applicable 7ot Applicable Tools: 2isual Basic *.3
Technolog": 6:A# Acti%eE
1ata :b;ects (A1:)
Tools: 2isual $tudio *.3
Technolog": $@8# $tored
0rocedures
1eplo"ment Tools
$"sprep =rwin
Testing Tools
App6enter Test App6enter Test App6enter Test App6enterTest
Tool 1
Descr(pt(on
%Descr(pt(on, The 'escription section provides a description of Tool @ and its
application.4
345+(5+3(- *
<<Begin tet here!!
Team
%Descr(pt(on, The Team section identifies who will be utili-ing the tool.4
<<Begin tet here!!
R(s6 Mana/ement
%Descr(pt(on, The /isk Management section identifies the risks associated with this
tool and an necessar plans to reduce or mitigate the risks.4
<<Begin tet here!!
Tool 2
Descr(pt(on
Descr(pt(on, The 'escription section provides a description of Tool 2 and its
application.4
<<Begin tet here!!
Team
%Descr(pt(on, The Team section identifies who will be utili-ing the tool.4
<<Begin tet here!!
R(s6 Mana/ement
%Descr(pt(on, The /isk Management section identifies the risks associated with this
tool and an necessar plans to reduce or mitigate the risks.4
<<Begin tet here!!
Reuse
%Descr(pt(on, The /euse section describes the overall approach for reusing solution
components.4
<<Begin tet here!!
Des(/n Patterns
%Descr(pt(on, The 'esign (atterns section identifies the design patterns *templates+
the team will use for this pro)ect and it identifies their sources. The team ma ac1uire
design patterns from both e0ternal and internal sources and the ma create new
design patterns.4
<<Begin tet here!!
345+(5+3(- 4
Development Team Tra(n(n/
%Descr(pt(on, The 'evelopment Team Training section identifies the training
necessar for the development team to ensure members will be successful
developing the solution.
*ust(+(cat(on, (lanning for an necessar training earl in the pro)ect will ensure that
sufficient time and resources are budgeted. This planning will also identif pro)ect
tasks *training+ that must occur before development work begins.4
<<Begin tet here!!
Development Team Support
%Descr(pt(on, The 'evelopment Team #upport section identifies the various tpes of
support the development team will re1uire, the sources of that support, the amount of
support of each tpe the will re1uire, and the estimated schedule for support.
*ust(+(cat(on, The earl identification of support re1uirements will ensure that the
are in place before development work begins.4
<<Begin tet here!!
345+(5+3(- B