Scribd
Upload
28 views7 pages

Chapter 24 To 28: Software Project Management

The document discusses the key components of a software project plan, including identifying users and stakeholders and their needs, assigning team members to tasks, creating a statement of work describing deliverables, listing available resources, developing a work breakdown structure and estimates, and scheduling tasks to manage risks. The project manager is responsible for planning and guiding the project.

Uploaded by

Anum Safdar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
28 views7 pages

Chapter 24 To 28: Software Project Management

The document discusses the key components of a software project plan, including identifying users and stakeholders and their needs, assigning team members to tasks, creating a statement of work describing deliverables, listing available resources, developing a work breakdown structure and estimates, and scheduling tasks to manage risks. The project manager is responsible for planning and guiding the project.

Uploaded by

Anum Safdar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Chapter 24 to 28

Software Project Management

Project Management

The project manager plans and guides


the software project

The project manager is responsible for


identifying the users and stakeholders and
determining their needs
The project manager coordinates the team,
ensuring that each task has an appropriate
software engineer assigned and that each
engineer has sufficient knowledge to
perform it
To do this well, the project manager must be
familiar with every aspect of software
engineering
2

Identifying Needs

The project manager drives the scope of the


project.

The project manager should identify and talk to the


main stakeholder
The effective way to show stakeholders that their
needs are understood and that those specific needs
will be addressed is with a vision and scope
document

Project Plan

The project plan defines the work that will be


done on the project and who will do it. It
consists of:

A statement of work (SOW) that describes all work


products that 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 needed for the product and their availability
A work breakdown structure and a set of estimates
A project schedule
A risk plan that identifies any risks that might be
encountered and indicates how those risks would be
handled should they occur
4

Statement of Work

The statement of work (SOW) is a


detailed description of all of the work
products which will be created over the
course of the project. It includes:

A list of features that will be developed


A description of each intermediate
deliverable or work product that will be built.
The estimated effort involved for each work
product to be delivered

Resource List

The project plan should contain a list of


all resources that will be used on the
project.

A resource is a person, hardware, room or


anything else that is necessary for the
project but limited in its availability
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
6

Estimates and Project


Schedule

The project plan should also include estimates


and a project schedule:

A work breakdown structure (WBS) is defined. This is


a list of tasks which, if performed, will generate all of
the work products needed to build the software.
An estimate of the effort required for each task in the
WBS is generated.
A project schedule is created by assigning resources
and determining the calendar time required for each
task.

You might also like