• Understand the nature of projects and why projects succeed or fail.
• Understand the needs of the project’s client and how these needs can be articulated within a project plan.
• Understand the reporting needs of different project stakeholders and create reports to satisfy these needs.
• Be able to create real-world robust project plans.
• Be able to read a project’s schedule and optimise this to meet the needs of various project stakeholders.
• Be able to baseline, track, analyse and replan a project to keep it on track.

This initial section introduces what Project Management is about. Project failure and the need for planning is discussed, along with basic risk assessment. Human issues and roles & communication are explained, along with the relationships between time, cost and quality. Expenditure within a project lifecycle is explained. An exercise creates a project methodology and a basic test determines initial PM knowledge.

• What is a project?
• Why do so many projects go wrong?
• Types of projects
• Project Management methods
• Why is there a need for phases?
• Risk assessment of the project
• Human issues
• Communication within the team
• Creating a feedback mechanism

From an initial understanding, the project can now take shape. Levels of detail are explained and tasks are defined at appropriate levels. Hierarchical relationships are defined using a Work Breakdown Structure approach. How tasks relate to one another is discussed, along with the amount of effort involved in accomplishing them. With what & how determined, when the tasks take place is worked out. Tasks that determine the project timing are emphasised, along with those with free time. Who will accomplish the work is added to the project and schedules created for individuals. Resource conflicts are discussed and resolved, together with cost implications. Practical exercises determine Work Breakdown Structures; Network Diagrams; Critical Path Analysis and basic Resource Levelling.

• The delegation of project tasks
• The three project resources
• Defining what to do
• Creating a Work Breakdown Structure
• Determining how to accomplish work
• How much work is involved?
• How do jobs relate to one another
• Determining when things happen
• Tasks with spare time
• Assigning resources and costs
• Who does what when
• Trouble-shooting resource problems
• Resolving resource problems
• Control of project costs

With the project planned, it is essential that it is kept on track. An update cycle and its frequency are discussed, together with practical recommendations to ensure its success. Methods of tracking are explained both for what has happened and how much is left to do. Effects of the past are reflected in future and compared to what should have been. Replanning techniques are discussed. An exercise takes actual progress and provides for creative opportunities to get back on schedule.

• The importance of control
• Determining an update cycle
• Determining when, what and how to track
• The need to update regularly
• Capturing actual and remaining work
• Progress comparisons against originals
• Getting back on track
• Staying on track

This final section discusses what happens when the main project work is over. Methods for making it better next time are illustrated; relative to delegates own project environments. A re-run of the initial PM test refines skills acquired during the course.

• Why review the past?
• Lessons learned for future projects