Professional Documents
Culture Documents
LESSON 2:
SOFTWARE
PROJECT
Applied
Software Project
PLANNING
Management
04:02:39 a.m.
WHO
NEEDS SOFTWARE?
Most software is built in organizations for people with
specific needs.
A stakeholder is a anyone who has an interest (or stake) in the software
being completed
A user is someone who will need to use the software to perform tasks.
Sometimes stakeholders will be users; but often the stakeholder will not use
the software.
04:02:40 a.m.
STAKEHOLDER:
-
SPONSOR
CUSTOMER
FUNCTIONAL/MANAGERS
PROJECT MANAGER
PROJECT TEAM MEMBER
04:02:40 a.m.
CLASSIFYING STAKEHOLDERS
Example: Classifying stakeholders an airline
booking system
An international airline is considering introducing a new
booking staff
Secondary stakeholders: customers, airline
management
Tertiary stakeholders: competitors, civil aviation
staff
04:02:40 a.m.
behaves as expected
04:02:41 a.m.
PROJECT MANAGEMENT
The project manager plans and guides the software
project
The project manager is responsible for identifying the users and
04:02:41 a.m.
IDENTIFYING NEEDS
The project manager drives the scope
of the project.
Why?
The project manager should identify and talk to the main
stakeholder
The effective way to show stakeholders that their needs
04:02:41 a.m.
VISION
AND
SCOPE
DOCUMENT
A typical vision and scope document follows an outline like
this one:
1. Problem Statement
a) Project background
b) Stakeholders
c) Users
d) Risks
e) Assumptions
04:02:41 a.m.
04:02:42 a.m.
sentences.
04:02:42 a.m.
10
04:02:42 a.m.
11
session.
It could include external factors that may impact the project, or
04:02:42 a.m.
12
made.
Often, these assumptions are generated during a Wideband Delphi
should be ready before the Delphi meeting and used as the basis for estimation.
If Wideband Delphi is not being used to generate the assumptions, the
04:02:43 a.m.
13
time, money, and resources on the project. The best time to write the
vision statement is after talking to the stakeholders and users and
writing down their needs; by this time, a concrete understanding of
the project should be starting to jell.
04:02:43 a.m.
14
List of features
A feature is as a cohesive area of the software that fulfills a specific need by providing a set
of services or capabilities.
Any software package in fact, any engineered product can be broken down into features.
The project manager can choose the number of features in the vision and scope document
by changing the level of detail or granularity of each feature, and by combining multiple
features into a single one.
It is useful to describe a product in about 10 features in the vision and scope document ,
because this usually yields a level of complexity that most people reading it are comfortable
with.
Each feature should be listed in a separate paragraph or bullet point. It should be given a
name, followed by a description of the functionality that it provides. This description does not
need to be detailed; it can simply be a few sentences that give a general explanation of the
feature. However, if there is more information that a stakeholder or project team member
feels should be included, it is important to include that information.
04:02:43 a.m.
15
Scope
of phased
release (optional)
Software
Project
Management
Sometimes software projects are released in phases: a version of the software with some
subset of the features is released first, and a newer, more complete version is released
later. This section describes the plan for a phased release, if that approach is to be taken.
This is useful when there is an important deadline for the software, but developing the
entire software project by that deadline would be unrealistic. The most common way to
compromise on this release date is to divide the features into two or more releases.
see dependencies between features that are not clear to the stakeholders and project
manager.
After the phased release plan is written down and agreed upon, the project team should
always be asked to re-estimate the effort and a new project plan should be generated
(see below). This will ensure that the phased release is feasible and compatible with the
organization's priorities.
04:02:44 a.m.
16
04:02:44 a.m.
17
comments.
The document can also be inspected (see Chapter 5).
it is important that the project manager follow up with each individual
person and work to understand any issues that the reviewer brings up.
The project manager should make sure that everyone agrees that the final
document really reflects the needs of the stakeholders and the users.
Once the document has been reviewed and everyone agrees that it is
REVIEW
VISION
SCOPE
complete, theTHE
team is unified
toward aAND
single goal
and the project can be
planned.
DOCUMENT
04:02:44 a.m.
18
PROJECT PLAN
will be produced and a list of people who will perform that work
A resource list that contains a list of all resources that will be
04:02:44 a.m.
19
04:02:45 a.m.
20
RESOURCE LIST
The project plan should contain a list of all resources that
The resource list should give each resource a name, a brief one-line
description, and list the availability and cost (if applicable) of the
resource
04:02:45 a.m.
21
project schedule:
04:02:45 a.m.
22
RISK PLAN
A risk plan is a list of all risks that threaten the project,
04:02:45 a.m.
23
04:02:46 a.m.
24