Software Project Management

Topic # 2
An overview of Project Planning
Step Wise: An Overview of Project
Planning
 Why do we need project Planning?
 Why do we need project planning Method?
 What are some of the project planning method?

2
Why do we need project planning?

 –Plans are of little importance, but planning is

 –Plans are nothing; planning is everything.

3
Why do we need project Planning?
◦ A detailed proposal for doing or achieving something.
◦ Decide on and arrange in advance.

 Project Planning
◦ The key to a successful project is in the planning.
◦ Creating a project plan is the first thing you should do
when undertaking any kind of project.

4
Why do we need project planning
Method?
 Methods provides a framework to think about all
the different aspects of project planning.

 It provides us with a checklist.

 It provides us with a recipe.

 It provides us with a hierarchy & time.

5
Phases of Project Planning / Process
Groups
 1. Scope the project.
◦ State the problem/opportunity.
◦ Establish the project goal.
◦ Define the project objectives.
◦ Identify the success criteria.
◦ List assumptions, risks, and obstacles.
 2. Develop the project plan.
◦ Identify project activities.
◦ Estimate activity duration.
◦ Determine resource requirements.
◦ Construct/analyze the project network.
◦ Prepare the project proposal.

6
 3. Launch the plan.
◦ Recruit and organize the project team.
◦ Establish team operating rules.
◦ Level project resources.
◦ Schedule work packages.
◦ Document work packages.
 4. Monitor/control project progress.
◦ Establish progress reporting system.
◦ Install change control tools/process.
◦ Define problem-escalation process.
◦ Monitor project progress versus plan.
◦ Revise project plans.
 5. Close out the project.
◦ Obtain client acceptance.
◦ Install project deliverables.
◦ Complete project documentation.
◦ Complete post-implementation audit
◦ Issue final project report.
7
Relationship between PM
& other methodologies

8
Why are some of the project
planning Methods?
 PRINCE 2
◦ Appendix A of Hughes and Cotterell.

 PMBOK
◦ Section 3.4 and 4.2 PM Body of Knowledge.

 Step Wise
◦ Chapter 2 of Hughes & Cotterell.

9
Project planning Methods /
PM Areas

10
Project planning Methods

 PMBOK

11
Step Wise – An Overview
 Step 0: Select project
 Step 1: Identify project scope and objectives
 Step 2: Identify project infrastructure
 Step 3: Analyze project characteristics
 Step 4: Identify project products and activities
 Step 5: Estimate effort for each activity
 Step 6: Identify activity risks
 Step 7: Allocate resources
 Step 8: Review/publicize plan
 Step 9: Execute plan
 Step 10: Execute lower levels of planning

12
13
Step Wise – An Overview
0
Select
project

1 Identify 2 Identify
project scope project
and objectives infrastructure

3
Analyse project
characteristics

to next slide

14
Step Wise – An Overview (cont’d)
from previous slide

4
Identify the
Review products and activities

5
Estimate efforts
Lower for activity
level For each
detail activity
6
identify
activity risks
from next slide
to next slide

15
Step Wise – An Overview (cont’d)

to previous slides from previous slide

10 7
Lower level Allocate
planning resources

9 8
Execute Review/
plan publicize plan

16
Step 1: Identify Project Scope and
Objectives
 Identify objectives and practical measures of the
effectiveness in meeting those objectives
 Establish a project authority

◦ To ensure the unity of purpose among all persons

parties

17
Step 2: Identify Project Infrastructure
 Identify relationship between the project and
strategic planning
◦ To determine the order of related projects (in the
organization) being carried out
◦ To establish a framework within which the system fits
 Identify installation standards and procedures
 Identify project team organization

18
Step 3: Analyze Project
Characteristics
 Project type: Distinguish the project as either objective-driven
or product-driven
 Analyse other project characteristics (including quality-based
ones)
 Identify high level project risks
 Take into account user requirements concerning
implementation
 Select general lifecycle approach in the light of the above
 Review overall resource estimates

19
Step 4: Identify Project Products and
Activities
 Identify and describe project products
◦ Identify all the products related to the project
◦ Account for the required activities
 Document generic product flows
◦ To document the relative order of the products
 Produce an ideal activity network
◦ Activity network shows the tasks that have to be
carried out as well as their sequence of execution for
the creation of a product from another

20
Step 5: Estimate Effort for Each
Activity
 Carry out bottom-up estimates
◦ need to estimate staff effort, time for each activity, and
other resources
 Revise plan to create controllable activities
◦ need to break a task into a series of manageable sub-
tasks

21
Step 6: Identify Activity Risks
 Identify and quantify the risks of each activity.

 Plan risk reduction and contingency measures

 Adjust overall plans and estimates to take account

22
Step 7: Allocate Resources (Staffing)
 Identify and allocate resources
◦ type of staff needed for each activity
◦ staff availabilities are identified

 Revise plans and estimates to take into account

23
Step 8: Review/publicize Plan
 Review quality aspects of the project plan
◦ To ensure each activity is completed with a quality
product
◦ Each activity should have ‘exit requirements’.

 Document plans and obtain agreement

24
EXAMPLE :
Step 0: Identify Project Scope and
Objectives
Example
◦ Step 0: Select a Project

25
Step 1: Identify Project Scope and
Objectives
Example
◦ Step 1: Identify Project Scope and Objectives

26
Step 2: Identify Project Infrastructure
Example
◦ Step 2: Identify Project Infrastructure

27
Step 3: Analyse Project Characteristics
Example
◦ Step 3: Analyse Project Characteristics
 For example DCSOffice
 Project Type: Product
 Characteristics: Office Tools
 Risk: Competition from Microsoft
 User Requirements: Must Emulate Open Office
 Life Cycle Approach: Water Fall Model
 Estimate Resources: Schedule, Efforts

28
Step 3: Analyse Project Characteristics
Example
◦ Step 3: Analyse Project Characteristics

29
Pain Curve

30
References
 Software Project Management (2rd Edition) by
Bob Hughes, Mike Cotterell
 The Mythical Man-Month by

Frederick P. Brooks
 A Guide to the Project Management Body of

Knowledge: Project Management Institute (PM I)

31