Chapter 8
Write Your Plan
Organizing the Plan
Guideline for Writing an Software Development Plan
(SDP):
Start with the Software Project Outline (SPO) to ensure
consistency.
Completely finish each section.
Use previous SDPs for reference, consistency, and lessons
learned.
Consider the tone of the plan so that you convey confidence that
the project will be successful.
Note sections that you have questions about so that they can be
discussed with reviewers and the team.
Plan to revise the SDP, and follow through with the revisions.
The plan belongs to the team, not to you, so leave your ego
home.
Copyright 2004 by Pearson Education, Inc.
Software Project Outline
Copyright 2004 by Pearson Education, Inc.
Software Development Plan
Copyright 2004 by Pearson Education, Inc.
Organizing the Plan
Start With the SPO to Ensure Consistency.
Make your SDP be an accurate expansion of
the SPO by starting with the information
contained in the SPO.
Cross reference the information with the SPO
to make sure it accurately relates to and
expounds on information in the SPO.
Copyright 2004 by Pearson Education, Inc.
Organizing the Plan
Completely Finish Each Section.
In order for the SDP to be considered
complete, all open issues need to be resolved.
Avoid including abstract statements about
open issues so that any resolution of the issue
will fit the abstraction.
Copyright 2004 by Pearson Education, Inc.
Organizing the Plan
Use Previous SDPs for Reference,
Consistency, and Lessons Learned.
The best way to write a document for the first
time is to use an example.
Your example SDP should convey the correct
format, style, and content that you can follow.
Copyright 2004 by Pearson Education, Inc.
Organizing the Plan
Consider the Tone of the Plan.
Your SDP will be a reflection of your view of
the project.
Make certain you convey a positive attitude
about the project.
Acknowledge the difficult tasks the team has
ahead and your confidence in your team to be
successful.
Copyright 2004 by Pearson Education, Inc.
Organizing the Plan
Note Sections You Have Questions About.
Keep a separate list of questions that you
have about your SDP.
Later, when seeking help from reviewers, your
notes can help keep them focused and
prompt alternative ideas and approaches.
Copyright 2004 by Pearson Education, Inc.
Organizing the Plan
Plan to Revise the SDP.
SDP revision should be included as part of
your normal tasks as project manager.
If updating the SDP is not routine, then, most
likely, it will not be done at all.
Copyright 2004 by Pearson Education, Inc.
Organizing the Plan
The Plan Belongs to the Project Team,
Not You.
Even though you are responsible for writing
and maintaining the SDP, don’t forget that it is
a script that your team will be working from
throughout the project.
View the SDP as a team document, and you
will be better able to change it as the project
progresses.
Copyright 2004 by Pearson Education, Inc.
Covering All the Bases
In order to write your SDP, your need to
be sure you have covered all the important
topics needed to launch the project.
Your SDP should put your team in a
strong position to start the project.
Copyright 2004 by Pearson Education, Inc.
Covering All the Bases
Project Overview
This section of the SDP draws the important
high-level portions of the project together.
High-Level Functionality
This section of the SDP outlines the
significant functions the software product will
perform to meet customer needs.
Copyright 2004 by Pearson Education, Inc.
Covering All the Bases
Project Staffing
This section of the SDP describes the
software engineering roles the team will
require and the number of personnel that will
be applied to the project.
Software Process
This section of the SDP is used to give an
overview of the software process the project
will use.
Copyright 2004 by Pearson Education, Inc.
Covering All the Bases
Schedule and Effort Estimates
This section of the SDP contains a high-level
project schedule with immovable milestones
and synchronization points which will illustrate
the project’s path to you team.
Measurements
This Section of the SDP specifies what
measurements are collect when and by
whom, and where they are stored during this
project.
Copyright 2004 by Pearson Education, Inc.
Covering All the Bases
Risks
This section of the SDP sets the tone for risk
identification throughout the project. It should contain
the top risks, their likelihood, and their impact.
Software Tools
This section of the SDP specifies the tools to be used
on this project and relates each tool to the task and/or
product the tool supports.
Copyright 2004 by Pearson Education, Inc.
Covering All the Bases
Hardware, Software, and Personnel
Support
Thissection of the SDP outlines needs and
support in each area where supported may be
needed.
Copyright 2004 by Pearson Education, Inc.
Reviewing the Plan
Steps to Reviewing an SDP:
1. Select experienced project managers and get their
commitment to participate.
2. Distribute the SDP to project managers and allow
them time to review it.
3. Schedule an SDP review meeting where you
present the SDP and gather feedback from all
reviewers.
4. Document the changes you made and the feedback
you didn’t use from the review so you can consider
both during project assessment.
Copyright 2004 by Pearson Education, Inc.
Reviewing the Plan
Get Experienced Project Manager to
Review the SDP.
Use the experience of other project managers
to your advantage.
Get several managers to review the SDP and
then attend a meeting where you present the
SDP as you would during project launch.
Copyright 2004 by Pearson Education, Inc.
Reviewing the Plan
Distribute the SDP for Review.
Be sure to distribute the plan early enough so
that there is adequate time to review it.
Your meeting will be less effective if your plan
is not reviewed properly before your meeting.
Copyright 2004 by Pearson Education, Inc.
Reviewing the Plan
Schedule an SDP Review Meeting.
Remember that project managers are busy,
so make getting feedback on your plan as
easy as possible.
A meeting is great for getting feedback, as
you are responsible for recording data not the
other project managers.
Copyright 2004 by Pearson Education, Inc.
Reviewing the Plan
Document the Input and Changes.
Document all input your receive, as well as
any changes you decide to make based on
that input.
These notes will help you in your next project
when used as part of the project assessment
phase.
Copyright 2004 by Pearson Education, Inc.
Chapter Key Points
A Software Development Plan needs to adhere
to a specific organization and content.
Changes typically impact many parts of the
SDP.
Each part of the plan has relationships to other
parts of the plan, so changes must be done
carefully and thoroughly.
Reviewing the SDP is a critical and needed part
of preparing to manage a project.
Copyright 2004 by Pearson Education, Inc.
