SOFTWARE PROJECT MANAGEMENT

TOPIC:INTRODUCTION

By:
P.Jagannadha Varma, B.Tech,M.Tech,(PhD)
Associate Professor, Department Of CSE,
LENDI INSTITUTE OF ENGINEERING & TECHNOLOGY
Syllabus:
UNIT -I:Introduction
▸ Project, Management, Software Project Management activities, Challenges in software projects, Stakeholders,
Objectives & goals
▸ Project Planning: Step-wise planning, Project Scope, Project Products & deliverables, Project activities, Effort
estimation, Infrastructure
OUTCOME: Identify the theoretical and methodological issues involved in modern software engineering project
management
UNIT -II: Project Approach
▸ Lifecycle models, Choosing Technology, Prototyping Iterative & incremental Process Framework: Lifecycle phases,
Process Artifacts , Process workflows
OUTCOME: Select and use project management frameworks that ensure successful outcomes.
UNIT -III: Effort estimation & activity Planning
▸ Estimation techniques, Function Point analysis, SLOC, COCOMO, Use case-based estimation ,
Activity Identification Approaches, Network planning models, Critical path analysis
OUTCOME: Estimate project cost and perform cost-benefit evaluation among projects
2
Syllabus:(Cont..)
UNIT -IV: Risk Management
▸ Risk categories, Identification, Assessment, Planning and management, PERT technique, Monte
Carlo approach
OUTCOME: Document and evaluate outcomes of risk management plans
UNIT -V: Project Monitoring & Control, Resource Allocation
▸ Creating a framework for monitoring & control, Progress monitoring, Cost monitoring, Earned value Analysis,
Defects Tracking, Issues Tracking, Status reports, Types of Resources, Identifying resource requirements, Resource
scheduling
OUTCOME: Identify project goals, constraints, deliverables, performance criteria, control needs, and resource
requirements in consultation with stakeholders.

3
What is Project Management?

“ .
Project management is the art of matching a project's goals, tasks,
and resources to accomplish a goal as needed. We say "as needed"
because one has limited time, money, and resources (human and
machinery) with which to accomplish a goal. One can think of a project as a
process.
Project management is the science (and art) of organizing the
components of a project, whether the project is development of a new
product, the launch of a new service, a marketing campaign, or a wedding.
A project isn't something that's part of normal business operations. It's
typically created once, it's temporary, and it's specific. As one expert notes,
"It has a beginning and an end." A project consumes resources (whether
people, cash, materials, or time), and it has funding limits.

4
Project Definition:
•Project is a one-time, multitask job with a definite starting point, definite ending
point, a clearly defined scope of work, a budget, and usually a temporary team
•When the project is finished it must be evaluated to determine whether it
satisfies the objectives and goals.

Project Constraints
Scope (S): The magnitude or size of the project
Performance requirements (P): technical and functional
Cost (C): Cost to do the job / project
Duration (T): Time required for the project

Mathematically C = f(P,T,S)

5
PROJECT EXAMPLES
Civil Infrastructure IT Projects: Others

•Bridges •Networking •New Vehicle Design

•Roads •Data Centre •New Product Launch
•Dams •CRM •Campaign
•Metro •SDLC •Change in Organization
•Power •Maintenance Structure
•Real Estate •Product •And so on..
•and so on… Implementations
•BPO
•And so on..

6
PROJECT CHARACTERISTICS

Non Planning is
Routine Characteristics Required
Tasks

Specific Large &

Objectives Complex
to be met

7
PROJECT CHARACTERISTICS: (Cont..)

Time Resources
Span Characteristics are limited

Temporary Work is
Work group In Several
Phases

8
What Makes Software Project Different?

Time Resources
Span are limited

Temporary Work is
Work group In Several
Phases

9
Software Project Management Activities:

10
ISO 12207 SDLC

11
CATEGORIZING SOFTWARE PROJECTS

Time Resources
Span are limited

Temporary Work is
Work group In Several
Phases

12
STAKEHOLDERS
Stakeholders are the people involved in or affected by the project actives. Stakeholders include

•The project sponsor and project team

•Support staff
•Customers
Time
•Users Resources
Span
•Suppliers
are limited
•Opponents to the project

Stakeholders can be categorized as

•Internal To Project Team

•External To Project Team But within Same Organization
•External To Both Project Team and Organization
Temporary Work is
Work group In Several
Phases

13
CHALLENGES IN PROJECT MANAGEMENT
There are various types of projects undertaken by the software industry and equally as many
challenges

•Globalization causing high competition.

Time
•Older legacy systems and infrastructure issues. Resources
Spanrates and time to market pressures.
•Adoption are limited
•Internal sourcing or outsourcing.
•Sufficient software requiring specific expertise.
•Integration and interface issues.

Work
•Multiple software bug testing & resolution iterations.
Temporary is
•Multiple and complex user level requirements.In Several
Work group
Phases
•Difficulty attracting and retaining applicable talent.
•ROI (return on investment).

14
SETTING OBJECTIVES
‘What do we have to do to have a success?’

15
SETTING OBJECTIVES
‘What do we have to do to have a success?’

• Need for a project authority

▹ Sets the project scope
▹ Allocates/approves costs
• Could be one person - or a group
▹ • Project Board
▹ • Project Management Board
▹ • Steering committee

16
OBJECTIVES
Informally, the objective of a project can be defined by completing the
statement:

The project will be regarded as a success if………………………………

Rather like post-conditions for the project Focus on what will be put
in place, rather than how activities will be carried out

17
OBJECTIVES:(Cont..)
Defined objectives should be SMART

18
GOALS:
These are steps along the way to achieve the objective. Informally, these can be defined by completing the
sentence…
▹ Objective X will be achieved If the following goals are all achieved
▹ A……………
▹ B……………
▹ C…………… etc
▹ Often a goal can be allocated to an individual.
▹ Individual may have the capability of achieving goal, but not the objective on their own e.g.
▹ Objective – user satisfaction with software product
▹ Analyst goal – accurate requirements
▹ Developer goal – software that is reliable

19
MANAGEMENT:
Management can be defined as all activities and tasks undertaken by one or more persons
for the purpose of planning and controlling the activities of others in order to achieve
objectives or complete an activity that could not be achieved by others acting independently.
▹ Management functions can be categorized as
▹ Planning
▹ Organizing
▹ Staffing
▹ Directing
▹ Controlling

20
MANAGEMENT CONTROL:

21
PROJECT PLANNING:

22
PROJECT PLANNING:(Cont..)

Step 0: Select Project

Step 1: Identify project scope and objectives

Step 1.1 : Identify objectives and practical measures of the effectiveness in meeting
those objectives
Step 1.2 : Establish project authority
Step 1.3 : Stakeholders analysis – Identify all stakeholders in the project and their
interest.
Step 1.4 : Modify objectives in the light of stakeholder anaylsis.
Step 1.5 : Establish method of communication

23
PROJECT PLANNING:(Cont..)

Step 2 : Identify project infrastructure

Step 2.1 : Identify relationship between the project and strategic planning
Step 2.2 : Identify installation standards and procedures.
Step 2.3 : Identify project team organization.

Step 3 : Analyze project characteristics.

Step 3.1 : Distinguish the project as either objective- product driven

Step 3.2 : Analyze other project characteristics ( including quality –based ones)
Step 3.3 : Identify high level project risks.
Step 3.4 : Take into account user requirement concerning implementation.
Step 3.5 : Select development methodology and life cycle approach.
Step 3.6 : Review overall resources estimates

24
PROJECT PLANNING:(Cont..)
Step 4 : Identify project products and activities

Step 4.1: Identify and describes project products ( or deliverables )

25
PROJECT PLANNING:(Cont..)
Step 4 : Identify project products and activities

Step 4.2: Document generic product flows

26
PROJECT PLANNING:(Cont..)
Step 4 : Identify project products and activities

Step 4.3: Recognize Product Instance.

Step 4.4: Produce Ideal Activity Network.

Step 4.5 : Modify the ideal to take into account need for stages and checkpoints.

27
PROJECT PLANNING:(Cont..)

Step 5: Estimate effort for each activity.

Step 5.1: Carry out bottom-up estimates

Step 5.2: Revise plan to create controllable activities.

Step 6 : Identify activity risks.

Step 6.1 : Identify and quantify activity based risks

Step 6.2 : Plan risk reduction and contingency measures where appropriate
Step 6.3 : Adjust overall plans and estimates to take account of the risks

28
PROJECT PLANNING:(Cont..)
Step 7 : Allocate resources

Step 7.1 : Identify and allocate resources

Step 7.2 : Revise plans and estimates to take into account resource constraints

29
PROJECT PLANNING:(Cont..)

Step 8 : Review / Publicize plan

Step 8.1 : Review quality aspects of the project plan.

Step 8.2 : Document plans and obtain agreement.

Step 9 & 10 : Execute plan / lower level of planning

Once the project is underway, plans will need to be drawn up in greater detail for
each activity as it becomes due. Detailed and lower level of planning of the the later
stages will need to be delayed because more information will be available nearer
the start of the stage.

30
THANKS!
Any questions?
You can mail me at:
▸[email protected]

31