Software Development

Project Management
Session 22

Software Development Project

Management
Software Development Project Management (SDPM) is the
discipline of assessing the characteristics of the

software to be developed,
choosing the best fit software development
life cycle, and then choosing the appropriate
project management approach to ensure meeting
the customer needs for delivering business value as effectively
and efficiently as possible

Lets look at the PDQ case

Go through the caselet and try to identify the subsystems/modules and the constituent activities
For example: Order Entry can be one sub-system/module

The proposed information system can be divided into these

sub-systems:
3. Order Routing

1. Order Entry

2. Order Fulfillment
5. Inventory Management
4. Logistics Management

Goal (whether goal is

well-specified or not) and Solution (how you expect
to reach the goal is known or not known)
Assess the sub-systems in terms of

Justify your assessment

To which quadrant does

each of the sub-system
belong to?

Quadrant 4

Quadrant 3

Quadrant 1

Quadrant 2

Goal

Not Clear

Clear

Clear

Solution

Not Clear

Quadrant 1

Not Clear

are
familiar to the
organizations
Little change is
expected
Low Complexity

Quadrant 3

Quadrant 1

Quadrant 2

Goal

Software Projects

Quadrant 4

Clear

Clear

Hardware, software and

telecommunication
environments are evolved
and
familiar
Linear
and Incremental SDPM
Skilled
teams
availableprojects
for such
software

Solution

Not Clear

are suitable

Standard Waterfall Model

Rapid
Development
Waterfall Model

Linear SDPM

Linear SDPM
Characteristics
Clearly defined goal, solution and
requirements (usually internal projects, projects
that are not leveraged by market conditions)
Weaknesses
Few scope change requests
Routine and repetitive projects Less scope for
accommodating change
Uses established templates
Costs too much and takes
too long
Strengths
Elaborate documentation
Entire project is scheduled
Rigid Must follow
Resource requirements are
defined set of processes
known
Does not require most skilled Less focus on customer
value
resources
Team members can be
distributed (no necessity for colocation

Staged Waterfall Model

Incremental SDPM

Feature Driven Development Model

Incremental SDPM

Incremental SDPM
Characteristics
Same as Linear SDPM projects - Clearly
defined goal, solution and requirements
Release of deliverables is hastened to realize
value
Routine and repetitive projects Weaknesses
Even more documentation
Uses established templates
than linear SDPM
Rigorous compliance to
Strengths
set processes
Value realization at early
Elaborate documentation
stages
Requires more customer
Better use of scarce
involvement than linear
resources
SDPM
Can accommodate some
Decision making in
change requests between
partitioning of features
increments
and functions can be
Relatively more focus on
problematic
customer value than linear

Overlay of PMLC on SDLC?

Costs

Thats it for today

More to follow in the next session