57086 Contract and Project Management 5 David Sowden, The University of Hull
57086 Contract and Project Management5
David Sowden, The University of Hull
557086 Contract and Project Management
Introduction to Processes - Controlling a Stage
David Sowden, The University of Hull
Overview
–Controlling a Stage• Fundamental principles• Contexts• Process description• Work Packages• Assessing progress• Capturing Project Issues• Capturing Project Issues• Examining Project Issues• Reviewing Stage Status• Reporting Highlights• Taking Corrective Action• Escalating Project Issues• Receiving Completed Work Packages
–
4
Controlling a Stage THE BASICS
Report progress to
Project BoardEscalate
problems to Project Board
Take corrective action
Authorise work
Confirm work
completion
Capture progress
information
Review progress, quality work, issues
and risk status
Analyse the impact of
issues
Capture and log issues
Relationships of Processes
5
Starting a Project
Directing a Project
Initiating a Project
Managing a Stage
Boundary
Controlling a Stage
Managing ‘Product’ Delivery
End
Closing a Project
Icons
6
Guidelines - Rules, Policies,instructions that should be followed
Resources - tools, systemsor materials required to complete a task
New risk raised
New issue raised
Directing a Project
Controlling a Stage (1)
7
Stage authorisedDirecting a Project
Authorise a Work package
Update Configuration item RecordsUpdate Issue Register
PID
Update Quality RegisterUpdate Stage Plan (current)
Issue RegisterConfiguration Management Strategy
Update Risk Register
Exception Plan approved
Directing a Project
Project Board advised
Directing a Project
Completed Work Package
Managing ‘Product’ delivery
New issueraised
Managing ‘Product’ delivery
Managing ‘Product’ delivery
Project Controls
Quality Management Strategy
Controlling a Stage (2)
8
Review Work Package statusWork Package authorised
Update Configuration Item Record(s)Update Issue RegisterUpdate Risk Register
Checkpoint Record(s)
Update Stage PlanUpdate Work Package(s)
Quality RegisterRisk RegisterStage PlanTeam Plan(s)
Controlling a Stage (3)
9
Receive completed Work PackagesStatus reviewed
Update Configuration Item Record(s)
Configuration Item Records
Update Stage Plan
Quality Register
Stage Plan
Controlling a Stage (4)
10
Review the stage statusWork Packages received
Update Issue ReportUpdate Issue RegisterUpdate Lessons Log
Checkpoint Record(s)
Update Risk RegisterUpdate Stage Plan
Quality RegisterIssue RegisterPIDBenefits review Plan
Controlling a Stage (5)
11
Report StatusStage status reviewed
Create Highlight report (current Period)Checkpoint Record(s)Daily LogHighlight Report (previous period)Lessons LogQuality Register
Controlling a Stage (6)
12
Capture and examine issues and risksStatus reported
Update Daily LogUpdate Issue RegisterUpdate Issue Report
PIDUpdate Risk Register
Business CaseConfiguration Management StrategyCommunication Management StrategyProject plan
Controlling a Stage (7)
13
Escalate issues and risksissues and risk examined
Update Exception ReportUpdate Issue RegisterUpdate Risk Register
Issue RegisterUpdate Issue Report
Issue ReportPIDBusiness CaseRisk Register
Controlling a Stage (8)
14
Take corrective actionissues and risk escalated
Update Configuration Item Record(s)Update Daily LogUpdate Issue Register
Configuration Item Records
Update Issue ReportUpdate Risk Register
Daily LogIssue RegisterIssue ReportRisk Register
Controlling a Stage (9)
15
Take corrective action
Project end approaching
Work Package delivery authorised
Exception raised
Request for advise
Stage Boundary approaching Managing a Stage Boundary
Directing a Project
Directing a Project
Managing Project Delivery
Closing a Project
section 4
section 7
section 4
section 6
section 8
TASK
Review stage management within your project
Have Work Packages been created and issued?
Have all the Team Managers agreed their Work Packages?
Have completed product been produced in accordance with the Work Package and Product Description?
Have the relevant Configuration Items Records been created/updated?
Has the Quality Register been maintained?
Were any products handed over as part of a phased delivery?
Has the Risk Register been maintained?
Has the Issue Register been maintained?
Has the Stage Plan been updated with actuals and revised forecasts?
Has the Daily Log been maintained?
Have Checkpoint Report been received fro each issued Work Package at the frequency and in the format agreed?
Was progress (actual and forecast) checked against agreed tolerances?
If tolerances were forecast to be exceeded, were the escalated to the Project Boards?
If corrective actions were required, were they logged, implemented and tracked?
Was the Business Case periodically checked for ongoing viability?
Were Highlight Reports created and issued in accordance with agreed reporting format and frequency?
Do Issue Reports exist for all issues being handled formally?
Do Exception Reports exist for all exceptions raised to the Project Board?
Has the Lessons Log been updated with any new lessons?
CHECK