07 - Project Planning.2012

8/11/2019 07 - Project Planning.2012

1/25

2010 wibas GmbHFor internal use only - 1 -

Turning Visions into Business.

Project Management07 Project Planning


2/25


1 Project Planning Overview


3/25


Establish and maintain plans that define project activities

Establish Estimates(SG 1)

Develop a Project Plan(SG 2)

Obtain Commitmentto the Plan

(SG 3)

Planning-Data

Project-Plans

Project Monitoring andControl


4/25



Estimates of project planning parameters are established and

maintained

Estimate theScope of the

Project

(SP 1.1)

EstablishEstimates of

Work Product

and Task

Attributes

(SP 1.2)

DetermineEstimates of

Effort and Cost

(SP 1.4)

Define theProject Life

Cycle

(SP 1.3)

Planning-Data


5/25



Typical Work Products for Establishing Estimates

SP 1.1 Estimate theScope of the Project

1. Task descriptions

2. work package

descriptions

3. WBS

SP 1.2 EstablishEstimates of Work

Product and Task

Attributes

1. Technical approach

2. size and complexity of

tasks and work products3. Estimating models

4. Attribute estimatesSP 1.4 DetermineEstimates of Effort and

Cost

1. Estimation rationale

2. Project effort estimates

3. Project costs estimates

SP 1.3 Define the

Project Life Cycle1. Project life-cycle

phases

Planungs-Daten


6/25


Develop a Project Plan(SG 2)

A project plan is established and maintained as the basis for

managing the project

Establish theBudget and

Schedule

(SP 2.1)

Plan for ProjectResources

(SP 2.4)

Plan for DataManagement

(SP 2.3)

Identify theProject Risks

(SP 2.2)

Planning-Data

Plan forNeeded

Knowledge and

Skills

(SP 2.5)

PlanStakeholder

Involvement

(SP 2.6)

Establish theProject Plan

(SP 2.7)

Project-PlansProject Monitoring

and Control


7/25


Develop a Project Plan

(SG 2)

Typical WP for Developing a Project Plan

SP 2.1 Establishthe Budget and

Schedule

1. Project Schedules

2. Schedule

dependencies

3. Project budget

SP 2.4 Plan for ProjectResources

1. WBS work packages

2. WBS task dictionary

3. Staffing requirements

based on project size andscope

4. Critical facilities/equipment

list

5. Process/workflow

definitions and diagrams6. Program administration

requirements list

SP 2.3 Plan for Data

Management1. Data management plan

2. Master list of managed data

3. Data content and format

description4. Data requirements lists for

acquirers and for suppliers

5. Privacy requirements

6. Security requirements

7. Security procedures8. Mechanism for data

retrieval, reproduction, and

distribution

9. Schedule for collection of

project data10. Listing of project data to

be collected

SP 2.2 Identify theProject Risks

1. Identified Risks

2. Risk impacts and

probability of

occurence

3. Risks priorities

Planning-Data

SP 2.5 Plan for NeededKnowledge and Skills

1. Inventory of skill needs

2. Staffing and new hire

plans

3. Databases (e.g., skills and

training)

SP 2.6 PlanStakeholder

Involvement

1. Stakeholder

Involvement Plan

SP 2.7 Establish theProject Plan

1. Overall Project Plan

Project-PlansProject Monitoring

and Control


8/25


Obtain Commitment to the Project Plan(SG 3)

Commitments to the project plan are established and maintained

Review Plansthat Affect the

Project

(SP 3.1)

ReconcileWork and

Resource

Levels

(SP 3.2)

Obtain PlanCommitment

(SP 3.3)

Project-Plans


9/25


Obtain Commitment to the Project Plan (SG 3)

Typical WP for Obtaining Commitment to the Project Plan

SP 3.1 Review Plnas thatAffect theProject

1. Record the reviews of plans

that affect the projectSP 3.2 Reconcile Work andResource Levels

1. Revised methods and

corresponding estimating parameters

(e.g., better tools, use of off-the-shelfcomponents)

2. Renegotiated budgets

3. Revised schedules

4. Revised requirements list

5. Renegotiated stakeholder

agreements

SP 3.3 Obtain PlanCommitment

1. Documented requests for

commitments

2. Documented commitments

Project-Plans


10/25


Project Planning is the basis for managing the project

Why do we do it?

! Cover all projects activities

! Provides the basis

for performing and controllingthe project's activities

Advice and Guidance

! Plan with results

! First estimate, then plan the schedule

! Make all plans consistent and

maintain the plans over the projectlife cycle.

!

Plan for corrective actions.

! Identify projects stakeholders and their roles and use the Project Lifecycle for identifying

the dates for stakeholder involvement.

! Obtain commitment of all stakeholders including team members.


11/25


2 Schedule


12/25


The work of the work breakdown structure is now scheduled

Scheduling means to arrange the work of the work breakdown structure suchthat time, budget and resource constraints are fulfilled.

Scheduling is typically done using a precedence diagramming method, e.g: aGANTT chart or a project network diagram.


13/25


A GANTT Chart is a horizontal bar chart developed by Henry L.

Gantt


14/25


A project network diagram shows the activities as boxes and the

dependencies between them


15/25


Both diagrams provides a graphical view of the project, predict

the time required to complete the project, and show which

activities are critical to maintaining the schedule

! ES - earliest start time: the earliest time atwhich the activity can start given that its

precedent activities must be completed first.

! EF - earliest finish time, equal to the earliest

start time for the activity plus the time required

to complete the activity.! LF - latest finish time: the latest time at which

the activity can be completed without delayingthe project.

! LS - latest start time, equal to the latest finish

time minus the time required to complete the

activity.

Task Name

Duration

(ES) Earliest Start Earliest Finish (EF)

(LS) Latest Start Latest Finsih (LF)


16/25


Calculating the critical path by determing the earliest start and

finish dates and the latest start and finish date! To calculate the earliest start and finish date, start from the first task. For each task, add

the duration to the earliest start (ES) to get the earliest finish (EF). For all successors, the

largest input EF becomes the ES.

! To calculate the latest start and finish date, start from the last task. For each task, subtractthe duration from the latest finish (LF) to get the latest start (LS). For all predecessors, the

smallest LS becomes the LF.

Initiate Build Cycle

1

Develop Support Material

1

Develop Heater Module

5

Develop Printing Module

3

Develop Reader Module

7

Perform System Testing

2

Plan Deployment

2

Confirm Build Cycle

2


17/25


A plan is more than a schedule

A plan addresses technical as well as management activities.

A plan consists of:

! Budgets, schedules, and milestones

! data management

!

risk identification

! resource and skill requirement

! stakeholder identification and interaction (stakeholders are all roles involved in the project)

The overall project must be kept as a separate document (e.g. a maintainedproject definition) that serves as an entry point for new team members, quality

assurance and senior management.


18/25


A plan needs commitment from all relevant stakeholders

otherwise the plan is likely to fail

! A plan must be aligned with other plans that affect the project (e.g. plans of other initiatives,

of suppliers, etc.)

! A plan must be aligned with the actual resources (budget, time, people, infrastructure).

! A plan must be agreed to by the team performing the work.


19/25


o a pr n


20/25


Exercise: 1h Scrum (1/2)

Task and Results:

1.

Sprint Goal: You are invited by a Business Angel tomake him a solution proposal (make a demo whathe will get)

Preparation Instructions:

! Explanation

! In the groups, decide who is Product Owner andwho is ScrumMaster (PM)

! Product Owner prepares Backlog for the Sprint

!

Teams set up place to work (get paper, pens,!

)

! Scrum Masters set up Sprint Board, Burndown

Chart,!.


21/25


Exercise: 1h Scrum (2/2)

Task and Results:

1.

Sprint Goal: You are invited by a Business Angel tomake him a solution proposal (make a demo whathe will get)

Instructions:

! 10 min: Grooming: Estimate the Product Backlog

Items

! 10 min: Sprint Planning I

! 10 min: Sprint Planning II

!

Conduct 3 days

10 min. work

2 min Standup

! 10 min Sprint Review

! 10 min Sprint Retrospective

-------------

! 10 min: debrief


22/25


Review Scrum against CMMI

Do:

! FOR SPi = SP 1.1 SP 3.3

3-4 people pick SPi and write answer to HowScrum implements Spi

UNTIL timebox ends

Timebox: 15 min


23/25


Team 1 Team 2 Team 3 Team 4 Team 5 Team 6

Team did deliver

Product Owner (PO)satisfied

ScrumMaster ensuredtimes strictly

Change Request (CR)rejected

Only ScrumMasterdiscussed CR with PO

Standup with 3questions

ScrumMaster did not dowork

Review of the work


24/25


Revision History

Rev.

no.State Date Comments Responsible

1.1 Finished 03.10.2004 Initial version Malte Foegen

1.2 Finished 21.06.2006 Revision History added, SEI Partner logo included, current template Malte Foegen

1.3 Finished 23.12.2007 Layout updates, added Scrum slides Malte Foegen

1.4 Finished 19.01.2008 Added sprint exercise and deleted other exercises Malte Foegen

1.5 Finished 23.01.2009 Added Sprint Review Slide Malte Foegen

1.6 Finished 18.01.2010 Updated layout Malte Foegen

1.7 Finished 21.01.2011 Extracted Scrum slides Malte Foegen

1.8 Finished 03.02.2012 New exercises Malte Foegen

Target status: finishedTemplate-Version: 2.11


25/25


Otto-Hesse-Str. 19 B 64293 Darmstadt Germany Phone +49 / 6151 / 50 33 49 - 0 Fax +49 / 6151 / 50 33 49 33 www.wibas.com

Hintermettlen 7 6318 Walchwil Switzerland Phone +41 / 41 / 51122 - 90 Fax +41 / 41 / 51122 - 91 www.wibas.ch

Documents

07 - Project Planning.2012