Overview of Project Management

DIBYESH GIRI
MCA-06,[ Puna University
]Nepal
 1.1 Overview of Project Management

Project Management brings Resources together &

Optimizes the Resources necessasory to
“successfully complete” the Project.

Resources
4. Skill, talent & Cooperative efforts of people.
5. facilities
6. Tolls & equipments
7. Information systems & techniques
8. Money.
The concept of Project Management as a discipline
was developed in U.S. Space program in 1960’s.
 1.1 Overview of Project Management
The Project Charting Techniques
1. Gantt Charts
2. PERT & CPM
Gantt Chart
Slack Time
A
C 1
T
I 2
V
I 3
T
I 4
E
S 5

5 10 15 20 25 30

Time in Days
 1.1 Overview of Project Management
Gantt Chart

• Gantt Chart – The technique is named after Henry

Gantt, the industrial engineer who introduced the
procedure in early 1900’s.
• Gantt chart shows the flow of activities in sequence as
well as those that can be under the way at the same
time.
• Limitation – Gantt chart doesn't show the
interdependencies of activities.
 1.1 Overview of Project Management -
Planning Time Aspect of a Project

• Objective – To determine the shortest time to complete

the project.
The steps in planning the time aspect are
3. Begin with Work Break down Structure.
4. Determine the time required to complete each sub unit.
5. Determine in what sequence the sub unit must be
completed.
6. Which sub units may be under way at the same time.
 1.1 Overview of Project Management -
Planning Time Aspect of a Project

A Mathematical model
Tm – The most probable time
To – The optimistic (Shortest) time – 1%
Tp – The pessimistic (Longest) time – 99%
Te – The calculated time estimate

Formula is
To + 4Tm + Tp
Te = 6
 1.2 Project Organization &
1.3 Planning a S/W Projects
Software Management

System Engineering Administration

Software Architecture Software Development Software Assessment

Quality is everyone’s job, integrated into all activities and checkpoints.

Each team takes responsibility for a different quality perspective.
 1.2 Project Organization &
1.3 Planning a S/W Projects
Software Management – The project management team
is an active participant, responsible for producing as well as
managing.
Artifacts
• Business Case
• Software development Plan
• Status assessments
Activities
• Customer interface
• Planning, progress monitoring
• Risk management
• Software process definition
• Process improvement
 1.2 Project Organization &
1.3 Planning a S/W Projects
• System Engineering
Artifacts
• Vision Statements
• Requirement set
Activities
• Requirement elicitation
• Requirement Specification
• Use case modeling
 1.2 Project Organization &
1.3 Planning a S/W Projects
• Administration
Artifacts
• Work breakdown structure
Activities
• Financial forecasting, reporting
• WBS definition, administration
 1.2 Project Organization &
1.3 Planning a S/W Projects
• Software Architecture – The architecture team is
responsible for real artifacts and for integration of components.
Artifacts
• Architecture description
• Release specifications
• Design set
Activities
• Demonstration planning
• Analysis Design
• Architecture prototyping
• Architecture documentation
• Demonstration coordination
• Component design
• Make/bye/reuse analysis
 1.2 Project Organization &
1.3 Planning a S/W Projects
• Software Development- The development team owns
the component construction and maintenance activities.
Artifacts
• Design set
• Implementation set
• Requirements set
• Deployment set
Activities
• Component design
• Component Implementation
• Component testing
• Component maintenance
 1.2 Project Organization &
1.3 Planning a S/W Projects
• Software Assessment – The assessment team is
separate from development. This structure fosters an independent
quality perspective and focuses a team on testing and product
evaluation activities concurrent with on-going development.
Artifacts Activities
• Deployment set -Release assessment
• SCO database -Use case/scenario testing
• User manual -Change management
• Release description -Transition to user
• Environment -System administration
• Deployment documents -Environment configuration
-Environment maintenance
-Tools meting
 1.4 Project Management Life Cycle

Project Development Life Cycle

1 2 3 4
Defining Planning Implementing Completing
The The The The
Project Project Project Project

Activity
Level

Time
 1.4 Project Management Life Cycle

• Project Life Cycle – Each project moves through a

predictable life cycle of four phases calling different
skills from the project manager.
• During a project life, management focuses on three
basic parameters
1. Quality Specification
2. Cost Budget
3. Time Schedule (On or before the deadline)
 1.5 Risk Management
• Risk concern future happenings
• Risk is defined as an exposure to the change of injury or loss
• Possibility that something negative may happen
• S/W Projects negatives
i.e. Adverse effect on 1.Cost 2.Quality 3. Schedule
• Risk management is to minimize the impact of risk on above
three.
• Risk management is generally done by the project
management.
• Risk management can be considered as dealing with the
possibilities and actual occurrence of these events that are
not regular or commonly expected.
 1.5 Risk Management
• Commonly expected events: e.g. going on leave or some
requirement changing – such things are handled by normal
project management.
• So in a sense, risk management begins where normal project
management ends.
• It deals with events that are infrequent, some what out of the
control of the project management.
• The idea of risk management is to minimize the possibility of
risks materializing if possible, or to minimize the effect of risk
actually materilizing.
• The risk management has to deal with identifying the
undesirable events that can occur, the probability of their
occurring, and the loss if an undesirable event does occur.
 1.5 Risk Management
Risk Management Activities
Risk Identification
Risk
Assessment Risk Analysis
Passive
activity
Risk Risk Prioritization
Management

Risk Management Planning

Active
activity
Risk Resolution
Risk
Control
Risk Monitoring
 1.5 Risk Management
1.5.1 Identification of Risks

Check Lists
Risk
Decision Driver Analysis
Identification

Assumption Analysis

Decomposition
 1.5 Risk Management
1.5.1 Identification of Risks
• Risk identification consists of listing all of the risks that can
adversely affect the successful execution of the project.
• Identifying risk early provides the management with a lot of time to
efficiently handle the risks.
• Risk identification is a systematic attempt to specify threats to the
project plan.
• By identifying known and predictable risks, the project manager
takes a first step towards avoiding them when possible and
controlling them when necessary.
• One method for identifying risks is to create a risk item checklist.
 1.5 Risk Management
1.5.1 Identification of Risks
Check list
• Product Size - risks associated with the overall size of the software
to be built or modified.
• Business impact – risks associated with constrains imposed by
management or the marketplace.
• Customer characteristic – risks associated with the sophistication of
the customer and the developer’s ability to communicate with the
customer in a timely manner.
• Process definition –software process has been defined and is
followed by the development organization.
• Development environment – availability and quality of tools to be
used to build the product.
• Technology to be built- complexity of the system – newness
• Staff Size and experience – overall technical and project experience
of the s/w engineer.
 1.5 Risk Management
1.5.2 Risk Analysis
Performance Models

Cost Models

Risk
Network Analysis
Analysis

Decision Analysis

Quality Factor Analysis

 1.5 Risk Management
1.5.2 Risk Analysis
Risk analysis is the next task that involve the subjective analysis of the
risks identified. Risk analysis can be done by estimating the worst
case value of the size and all the cost drivers and then estimating
the project cost from these values. Using the worst case effort
estimate, the worst case schedule can easily be obtained.
The other approaches for risk analysis includes studying the probability
and the outcome of possible decisions (decision analysis).
Understanding the task dependencies to decide critical activities and
the probability and cost of their not being completed on time
(network analysis).
Risks on various quality factors for reliability and usability (quality factor
analysis).
Evaluating the performance early through simulation, etc. if there are
strong performance constrains on the system (performance
Analysis).
 1.5 Risk Management
1.5.3 Risk Planning & Monitoring

Buying Information

Risk Avoidance

Risk Transfer
Risk
Planning
Risk Reduction

Risk element Planning

Risk Plan Integration

 1.5 Risk Management
1.5.3 Risk Planning & Monitoring
Plans are developed for each identified risks that needs to be
controlled. Many risks might be combined together for the
purpose of planning, if they require similar treatment. A basic risk
management plan has five component.
2. Why the risk is important and why it should be managed;
3. What should be delivered regarding risk management and when
4. Who is responsible for performing the different risk management
activities.
5. How will the risk be adopted or the approach be taken.
6. How many resources are needed.
 1.5 Risk Management
1.5.3 Risk Planning & Monitoring

Milestone Tracking

Top-10 Tracking
Risk
Monitoring
Risk reassessment

Corrective Action
 1.5 Risk Management
1.5.3 Risk Planning & Monitoring
Risk monitoring is the activity of monitoring
the status of various risks and their control
activities. Like project monitoring, it is
performed through the entire duration of
the project like many monitoring activities,
a checklist is useful for monitoring.