Software Project

Management
Lecture No. 01
SOFTWARE PROJECT MANAGEMENT
KEY TOPICS

I. Overview of Project Management

II. Software Development Fundamentals
III. Processes
IV. Organization
V. Planning
VI. Estimation
VII. Work Breakdown Structure
VIII.Scheduling
IX. Risk and Change Management
X. Quality
XI. Application Tools
XII. Commissioning & Migration
Recommended Readings

Software Project Management

By E.M. Bennatan

Software Engineering
By Roger S. Pressman

A Guide to the Project Management Body of

Knowledge (PMBOK Guide)
Recommended Websites

Software Project
 www.maxwideman.com
 www.4pm.com
 www.bettermanagerment.com
 www.e-programme.com
 www.managementhelp.org
 http://project-management.informationeering.com
…
Software Project Management

Overview of Project Management

1. Introduction & Fundamentals

Software Project Management

I. Overview of Project Management

i. Management
ii. Project management
iii. SW project management
iv. Project (Definition, Characteristics,
Dimensions)
v. Goals of Project Management
vi. Project Phases
vii. Software Project Lifecycle
viii.Cost and Cost management
Software Project Management

I. Overview of Project Management

ix. Project versus Program management

x. Project Success
xi. Trade-off triangle (time, cost, quality)
xii. Technical Fundamental
xiii.Project Management Skills
xiv.Project Management knowledge areas
xv. Team Leadership
xvi.Project Organization
Software Project Management

Management

Project
Management

Software
Project
Management

Time, Budget, Quality

What is Management?

Basically, the management involves the

following activities:

1. Planning: Deciding what is to be done

2. Organizing: Making arrangements
3. Staffing: Selecting the right people for the job
4. Directing: Giving instructions
5. Monitoring: Checking on progress
6. Controlling: Taking action to remedy hold-ups
7. Innovating: Coming up with new solutions
8. Representing:Liaising with users, etc.
What is Project Management?

 Project Management is accomplished through

the use of the processes such as:

1. Initiating Process Group: Defines and authorizes the

project or phase
What is Project Management?

 Project Management is accomplished through

the use of the processes such as:
2. Planning Process Group: Defines and refines
objectives and plans the best alternative courses of
action to attain the objectives and scope that the
project or phase was undertaken to address.

Following are the key points to be considered for

planning purpose:
• Determine requirements
• Determine resources
• Select lifecycle model
• Determine Product features
strategy
What is Project Management?

 Project Management is accomplished through

the use of the processes such as:
3. Executing Process Group: Integrates people and other
resources to carry out the project management plan
for the project or phase.

4. Monitoring & Controlling Process Group: progress is

regularly measured and monitored to identify
variances from the project management plan, so that
corrective action can be taken: (Monitoring the work
being done and Tracking COST, EFFORTS &
SCHEDULE)
What is Project Management?

 Project Management is accomplished through

the use of the processes such as:

5. Closing Process Group: formalizes acceptance of the

product, service, or result and brings the project or
phase to an orderly end.

Project management is application of knowledge, skills,

tools and techniques to meet project requirements

The more you know about your project, the better you are
able to manage it
What is Software Project Management?

Software Project Management is distinct from

managing any other project due to complexity
involved in the development process:

 Product: Composed of many programs, functions, routines and

subroutines that integrate and perform the
intended functions.

 Visibility: The product has no shape or size that can be

measured.

 Monitoring: Traditional measurement of performance cannot be

applied to software.
What is Software Project Management?
Software Project Management is distinct from
managing any other project due to complexity
involved in the development process:

 Sensitivity: As software applications are growing

mission critical, the margin for error is
severely limited.

 Quality Assurance: Techniques to streamline and

measure SW development are
comparatively new and as yet
not calibrated for error free use.
Project Definition
 What is Project?
Dictionary definition
AAplanned
plannedactivity
activity
Unique
Aim /Task/ Purpose
Limited Time Scale
 Progressive Elaboration Developing
Developingthoroughly
thoroughlyinin
steps,
steps,and
andcontinuing
continuingsteadily
steadily
 Project Managers by
byIncrements.
Increments.

Examples
Coach
Coachofofaateam,
team,captain
captainofof
 Developing a new product or service aaship
Effecting a change in structure or style ship
Developing an information
& control system
Constructing a facility
Goals of Project Management
Three Project Goals

Performance

Time Cost

Expectations of clients are not an additional target,

but an inherent part of the project specifications
Goals of Project Management

Required Performance
Performance
Target
Budget Limit

Cost

Due Date

Time (Schedule)
Project Characteristics
Projects differ significantly from the ongoing operations
within a company.

Projects can be part of overall Programs and shouldn’t be

confused with such.

A Program is an exceptionally large long-range objective

that’s broken down into a set of projects.

Specific characteristics of a project include:

 Temporary
 Unique
 Specific Purpose
 Multi Disciplinary
 Conflict Ridden
Project Dimensions

Process

Product &
People PROJECT Technology

Product &
Customer
Project Dimensions
People
Principles Of Staffing A Project
Top Talent
– Better and fewer people
Job Matching
– Fit the tasks to skills, and motivate
Career Progression
– Help, not force people self-actualizing to work
where they are more experienced / or needed
Project Dimensions
People
Principles Of Staffing A Project
Team Balance
– People complement and harmonize each other
Misfit Elimination
– Problematic team members are eliminated and
replaced ASAP
Team Organization
Important who works with whom
Motivation
Bad motivation, bad outcomes, less work
Project Dimensions
Process
 Rework Avoidance
 Do not do things twice

Quality Assurance
 Two purposes: product has a certain level of
quality once released; detect errors ASAP

Development Fundamentals
 Develop same thing with fewer people or in
shorter period of time
Project Dimensions
Process
Risk Management
 Avoid disasters

Resource Targeting
 Guiding resources as appropriate

Lifecycle Planning
 Helps targeting resources, always keep in mind

Customer Orientation
 Develop Software that somebody wants!
Project Dimensions
Product & Technology
 80 / 20 –Rule
 Fix time scale: snip off 20% of features (leave 80%), save 20%
time
 Product Size
 Larger product - longer time, new requirements, features, ...cut
size ½, save effort 60%
 Product Characteristics
 Performance, memory use, robustness, reliability (Check
acceptance/responsiveness of the Product?)
 Prioritize features
Development Tools
 Object Orientation / Structural Programming
Project Dimensions (V)
Product And Customer

No product (outcome), no project!

AbilityTo
Ability ToProduce
ProduceAdditional
AdditionalValue
ValueTo
ToThe
The
Customer
Customer

Operative
Operative Funds
Funds Competitive
Competitive
efficiency
efficiency position
position
Project Phases

All projects are divided into “Phases”

All phases together are known as the

“Project Life Cycle”

Each phase is marked by completion of

“Deliverables”
Software Project Lifecycle
A Set Of Activities, Which Occur More Or Less
In An Order

 Phase 1 -> Phase 2 -> … -> Phase N

Usual Phases

Definitions And Analysis

Design
Implement / Produce
Test / Release
Core Software Project Phases
Software
Concept

Requirement
Analysis

Architectural
Design

Detailed
Design

Coding and
Debugging

System
Testing

Deployment and
Maintenance
Costs and Cost Management (I)

Time And Money

 When Financing Estimation Was Made?
 Usually Estimation Is Made Too Low

S-curve

Early Phase - Less Costs;

Mid Phase – Huge Costs ;
Late Phase - Less Costs
Plans are (usually) made at the beginning
Costs and Cost Management (II)

Categorize Costs

 Salaries (With Overhead)

 Travel
 Consumables
 Equipment
 External Services
 Other Expenses
– Annually/Periodically
Project vs. Program Management

Mostly differences
Longer than of scale
projects

PROGRAM
Definitions Often a number
vary of related
projects
Example: Program
Manager for MS
Word
Project vs. Program Management

A co-coordinated
PROJECT portfolio of projects that
change organizations to
achieve benefits of
strategic importance.

A
. temporary organization
that is needed to produce a
unique and pre-defined
outcome or result at a pre-
specified time using pre-
determined resources. PROGRAM
Project Success

Project is successful once:

Quantity & Quality Time

Financial

RESULTS ARE
RESULTS ARE ACHIEVED
ACHIEVED
Trade-off Triangle
Fast, Cheap, Good. Choose two

Product
Jul-05

M T W T F S S

1 2 3 4 5 6

7 8 9 10 11 12 13

14 15 16 17 18 19 20

21

28
22

29
23

30
24

31
25 26 27
Cost

Schedule
Technical Fundamentals

Requirements

Analysis

Design

Construction

Quality Assurance

Deployment
Project Management Skills

 Leadership
 Communications
 Problem Solving
 Negotiating
 Influencing the Organization
 Mentoring
 Process and Technical Expertise
Project Management Knowledge Areas

1. Project integration management

2. Scope
3. Time
4. Cost
5. Quality
6. Human Resource
7. Communication
8. Risk
9. Procurement
Summary

I. Overview of Project Management

i. Management
ii. Project management
iii. SW project management
iv. Project Definition
Summary

I. Overview of Project Management

v. Project versus Program management

vi. Project Success
vii. Trade-off triangle
viii.Technical Fundamental
ix. Project Management Skills