Vous êtes sur la page 1sur 25

Software Project

Management
30/Sept/2012

Contents

Case Study
Project definition
Project Management
Need for Software Project Management
Software project success factors
Project Life cycle
Project Stakeholders
Organizational Structure & Project Characteristics
Project Management Processes and Groups
Typical Project Phases
Software Development Processes
Proposed Course Outline
Recommended Books and Websites

Case Study

The product is developed envisaging the requirements of the Department of Correction (DOC) and
Board of Probation & Parole (PBPP) for the US states

The solution is designed so as to cater to the Correction departments of other states in the US

Solution approach
The products software architecture is based on the .NET 3.5 Framework and the Windows
Enterprise Platform model

The overall scope of the project has been divided into 3 core functional groups defined based
on functionalities provided by legacy system & business areas
Core

1 (C1) : Functionalities present in all the existing mainframe applications

Core

2 (C2) : Functionalities present in existing applications in varied platforms

Core

3 (C3) : Functionalities present in existing parole board applications

Case: Governance &


Communication
Client Org.

Service
Provider
Org.

Stra
t

DOC

ABC

Executive
Management

Monthly Meetings

DOC
CIO

Quality
Staffing
Metrics, Trends & Casual
Analysis
Future Work

ABC
Delivery Head

al

DOC

ABC
Project
Management

al

Project Status
Status Reports
Issue Resolution
Reviews

n
atio

Project Manager
& Process owners

er
Op

Weekly Meetings

al

Ope
rati
on

Executive Management Review


Health Check on Service Delivery
Achievements
Setting Strategic Directions

tic
Tac

Tac
tica
l

Executive
Management

gic
ate
Str

egi

Quarterly Strategic
Meetings

Case: Timelines
2010

2009

2011

2012

2013

Phase-I
C1, R-1
C1,Commissary
R-1

Go Live on
Apr 2012

Go Live on
6th Dec 2010

Commissary
Go Live on
March 2013

C1, R-2
Start Date
1st Feb 2010

C1, R-3
C1, R-2+
C2, R-1
C2, R-2
C3, R-1
C3, R-2

Project
A

project is a temporary endeavor undertaken


to create a unique product or service

Defined beginning and end


Every project is different
Different from operations

Progressive

Elaboration

Progressive progress in steps


Elaborated worked out thoroughly

Project Management
Application

of

Knowledge
Skills
Tools
Techniques

To manage project work


Scope
Time
Cost
Risk
Stake holder expectations
& identified requirements

Project Management process


Iterative progressive elaboration

Project Management
Processes

Project management processes

describe, organize, and complete the work of the project.


are applicable to most projects,
specify and create the projects product.

Project management processes can be organized into five


groups of one or more processes each:

Initiating processesauthorizing the project or phase.


Planning processesdefining and refining objectives and selecting the best of the
alternative courses of action to attain the objectives that the project was undertaken to
address.
Executing processescoordinating people and other resources to carry out the plan.
Controlling processesensuring that project objectives are met by monitoring and
measuring progress regularly to identify variances from plan so that corrective action
can be taken when necessary.
Closing processesformalizing acceptance of the project or phase and bringing it to
an orderly end

Project Management
Relationship with other Management Disciplines

Project Management
Related Endeavors

Program is a group of projects managed in a coordinated way to


obtain benefits not available from managing them individually
Sub-projects projects divided into smaller components (logical
modules) for better management
Project Portfolio Management selection and support of
projects/programs investments. These investments are based on

Organizations strategic plan


Available resources

Why Do Software Projects Fail


How

many times a bridge has collapsed while


you are walking on it?

How

many times your famous software


package has crashed while you are using it?

Is

it because bridges are made of concrete,


steel etc. and the software are not?

One possible answer:


People

have been building bridges for many


thousands of years.
People have been developing software for
about 50 years..
In other words;

Building a bridge has a formal standardized


process
Software development doesnt have such
formalized discipline.

Software Project Statistics 1979

Why this happens?


Is

it due to technical reasons?

"For the overwhelming majority of the bankrupt


projects we studied, there was not a single
technological issue to explain the failure.
DeMarco & Lister, Peopleware

Why this happens?

"I believe the hard part of building software to be


the specification, design and testing of this
conceptual construct, not the labor of representing
it and testing the fidelity of the representation."
Frederick P. Brooks, "No Silver Bullet"

Software Project Statistics


Present Day

The average cost of the Challenged projects is 189% of their


estimated budget!

Why is it so hard to succeed?

What are key issues

Poor project management

Planning, Tracking, Control

Problems in communications
Teamwork issues
Resource allocations
Lack of risk identification
Time management issues
Lack of user involvement
Lack of top management involvement

Keys Project Success Factors

Top management support

Sound methodology

Solid leadership

User involvement
Clients'
involvement
right from the
start

You should know where you are going!


No universal method. Having some
methodology is fine.
But always select the most effective
method.
Capitalize on your expertise.

Awareness of the subject


Full commitment
Understanding the crew
Expecting setbacks
Steadiness
Knowing what to expect at which time
Staying vocally and visibly behind the
project

Complete understanding of the subject


(functionally and technically)
Leading from the front,
Motivating,
Convincing,
Excellent Communicator

Project Life Cycle

Used to define the beginning and end of a project


Used to link the project to the ongoing operations of the
organization
Collection of phases
Each phase has a deliverable

ETVX/RECI
Transition between phases

The phases overlap

Fast tracking
Used to expedite

Typical Project Phases

Project stakeholders
Performing organization
Management Skills:
Customer
Leading
Communicating
Project Manager
Problem Solving
Team members
Influencing
Negotiating
Vendors
Sponsor
Conflict of Interest All difference should be
resolved in favor of the customer

Organizational structure vs
Project characteristics

Software Development
Processes

Waterfall
Modified Waterfall
Prototype
V Process Model
Spiral
RAD
COTS
Agile

Choose Your Life Cycle

Varies by project
Opt for iterative or incremental
How well are requirements understood?
What are the risks?
Is there a fixed deadline?
How experienced is the team or customer?

Social Economical
Environmental Influences

Standard compliance is non mandatory


Regulation compliance is non mandatory
Internationalization
Culture Influences
Social- Economical-Environmental Sustainability

Vous aimerez peut-être aussi