Introduction

• General
  • What is a project?
  • What is project management?
  • What does a project management system consist of?
  • Project visualisation
  • Why breakdown a project?

Topics

• Simple process parts
  • Concept or idea
  • Feasibility study
  • Initiation
  • Specification
  • Design
  • Build
  • Implementation
  • Operation and review
• Basics
  • Project Notebook
  • Assumptions
  • Assumptions and constraints
• Problem statement
• Mission statement
  • Mission statement
  • Mission statement Simple approach
  • Mission statement Formal approach
• Strategy
  • Strategy
  • Selecting a strategy
  • Recording the strategy
• Scope
  • Scope
  • Scope areas affected
• Objectives
  • Objectives reasons for setting
  • Objectives should be
  • Customer analysis
• Deliverables
  • Deliverables
  • Exit criteria
  • Product specification
• Schedules
  • Work breakdown structure part 1
  • Work breakdown structure part 2
  • Work breakdown structure part 3
  • Types of plans
  • Schedules
  • Resources cost
  • Control system
  • The Gantt chart
  • Authority roles responsibilities
  • Authority
  • Risk areas
  • Benefits What are they
  • Terms of Reference
• Planning
  • Planning part 1
  • Planning need to answer
  • Introduction schedule overview
  • Task characteristics Work package
  • Task information
  • Milestones General
  • Milestones Deliverables
• Control
  • Why - what can go wrong?
  • Monitoring
  • General
  • What scope?
  • Time
  • Cost
  • Cost - common terms
  • Cost overspend
  • Cost cash flow
  • Progress reporting general
  • Progress reporting Project Board
  • Progress reporting what data?
  • Taking action what does this entail?
  • Assessing the situation
  • Resolving issues and problems
  • Contingency
  • Areas of review
  • Controlling change part 1
  • Controlling change part 2
  • Document control procedures
  • Project completion
  • Quality management plan overview
  • Plan - areas to define
• Quality
  • Quality management plan overview
  • Plan - areas to define
  • Statistical control
• Risk management
  • Overview
  • General approach
  • Health and safety
• Project review
  • The benefits
  • The report
• Project manager
  • Overview
  • Choosing the project team
  • People recruitment
  • Communication
  • Managing user expectations
  • Systematic approach
  • Empowerment
  • Appointment
  • Project organisation The Project Office
• Construction
  • Construction projects part 1
  • Construction projects part 2
  • Construction projects part 3
  • Construction projects part 4
  • Construction projects part 5
  • Construction projects part 6
  • Construction projects part 7
  • Construction projects part 8
  • Construction projects part 9
  • Construction projects part 10
• Reports
  • Writing reports part 1
  • Writing reports part 2
  • Writing reports part 3
  • Writing reports part 4
  • Writing reports part 5
• Manual methods
  • Time and duration
  • Precedence grid
  • Task flow charts
  • Task flow charts Activity-on-Node networks bubble diagrams
  • Task flow charts Activity-on-Node networks bubble diagrams
  • Task flow charts Activity-on-Arrow networks
  • Task flow charts Activity-on-Arrow networks arrow diagrams
  • Task flow charts Activity-on-Arrow networks arrow diagrams float v slack
  • Contingency 1 General
  • Contingency 2 The weather
• Resource
  • Resource procurement part 1
  • The schedule
  • Resource levelling part 1 summary
  • Resource levelling part 2 techniques
  • Reducing project durations
• Project management systems
  • Six sigma part 1
  • Six_sigma part 2
  • Six_sigma part 3
  • SCRUM part 1
  • SCRUM part 2
  • SCRUM part 3
  • Earned value management part 1
  • Earned value management part 2
  • Earned value management part 3
  • Earned value management part 4
  • Earned value management part 5
  • Earned value management part 6
  • Sensitivity analysis
  • PMBOK part 1
  • The Project Management Knowledge Areas part 2
  • The Project Management Knowledge Areas part 3
  • The Project Management Knowledge Areas part 4
  • The Project Management Knowledge Areas part 5

Detailed planning

• Overview
• Initial estimation simple cost plan
• Initial estimation high level plan first review
• Initial estimation high level plan second review
• Initial estimation budget cost plan
• Estimating overview
• Estimating why are estimates too long
• Estimating why are estimates too short
• Estimating data usage
• Dependencies 4 basic types
• Dependencies (schedule)
• PERT and slack (float)
• PERT part 1
• PERT part 2
• PERT part 3 Cumulative Probability graph
• Elapsed time example for a task
• Roles and responsibilities
• Responsibilities and resources
• The Gantt chart
• Constraints resource
• Critical path part 1
• Critical path part 2 choosing one
• Criticalpath part 3 eliminating one
• Critical path part 4 reducing durations

Is the customer satisfied?

You may well have produced your product to the correct specification, on time, within budget and to the right performance and quality criteria but is the customer happy with it?
You would hope so, but only the customer will tell you … find out by asking.
If he or she isn’t, find out why and review the issues.

It could be that there has been some serious breakdown in communication along the way.
Keep the customer informed and make sure there is no margin for ambiguity in any of the agreed documentation.
Serious problems should not arise if communication with the customer has been good and continuous.

Project closure is not just about handing over the product to the customer.
When a product is transferred there are many other aspects that must be addressed.

For example:

The product may be fine at handover but the customer will likely want support to make sure that it works in the field for a reasonable time without problems.
There may be customer staff training to consider.
There may be long term support for parts, training (less likely) and general repairs.
These aspects must be considered an allowed for.

Conduct a project review

As well as the product the project process must be wound down and finished in a controlled manner.
This would entail a project review that would cover:

It is advisable for the project management team to carry out a post mortem to try to measure the success of the project.

Assuming the products and reports are out of the way, how else do you measure success?
Customer feedback is vital for the product itself.
In addition, there will be business measures.
Has the project met all of the criteria as set out in the Business Case as for PRINCE2®?
This would include overall costs which may have been influenced by any delays.

Are there any other areas of work to complete?
This would include identifying and recording all support work.
It would also include the completion of all reports or staff issues etc.

What lessons has the project learnt?

This could cover:

• For future projects
• Other projects still running
• General business issues
• The processes used
• The skill set of personnel
• Training plans etc

Project closure is covered under PRINCE2 [see ‘The Complete Project Management plus PRINCE2’] within the process ‘Closing a Project (CP)’.

PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.