software management

• 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

• 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.

Estimates and project schedules will be
discussed in detail in later slides.

• Planning Works Distributions in Project

• PRINCE 2
• Various Approaches Towards

Identifying Project Activities
• Activity-based approach (WBS)
• Product-based approach
• Hybrid approach
• Activity-based Approach
• Use Work Breakdown Structure (WBS)

to generate a task list
• WBS involves

• identifying the main tasks
• break each main task down into subtasks

• The subtasks can further be broken down
into lower level tasks.

• Work Breakdown Structure
• Activity-based Approach Pros & Cons
• Advantages

• More likely to obtain a task catalogue that
is complete and is composed of non-
overlapping tasks

• WBS represents a structure that can be
refined as the project proceeds

• The structure already suggests the
dependencies among the activities

• Disadvantage

• Very likely to miss some activities if an
unstructured activity list is used

• Product-based Approach
• Product Breakdown Structure (PBS)

• To show how a system can be broken
down into different products for
development

• Product Flow Diagram (PFD)

• To indicate, for each product, which
products are required as ‘inputs’

Advantages

• Less likely to miss a product unexpectedly
from a PBS

• Product-based Approach – An example
• Hybrid Approach
• A mix of the activity-based approach

and the product-based approach
• More commonly used approach
• The WBS consists of

• a list of the products of the project; and
• a list of activities for each product

• Hybrid Approach (cont’d)
• Hybrid Approach (cont’d)
• IBM in its MITP methodology suggests

5 levels

• Level 1: Project

• Level 2: Deliverables (software, manuals

etc)
• Level 3: Components
• Level 4: Work-packages
• Level 5: Tasks (individual responsibility)

• References
• Bob Hughes and Mike Coterell. (2010).

Software Project Management-Fifth

Edition. McGraw Hill Publishing

(Chapter 2)
• Kathy Schwalbe. 2007. Information

Technology Project Management (5th

ed.). Course Technology Press, Boston,

MA, United States.

Any
Questions

?