What and when do we check Project Progress?
- Checking is continuous and iterative, not a single point in time
- Highlighting problems early leads to less costly fixes and prevents project slippage
- Do not wait for Milestone events or Project Meetings to report faults, failures or deviations form schedule
- Record negative issues on an issues log
- Take guidance from risk assessments, stakeholder interests and power, the schedule of tasks and from task holders
- Become a Goal oriented Project Team member and not blame cultured, thus focus on the solutions not the problems or faults
- At team meetings use a SWOT analysis representing the current situation
The checking or studying part of a Project is an iterative process that includes measuring progress and performance at task, activity and project levels and includes reporting of achievements.
The desired output of this stage is therefore checking that the schedule of tasks and the activities are on time, to the right quality and right cost level to the satisfaction of relevant stakeholders. For instance a task may be carried out to the satisfaction of the Project team members but the end user may not be entirely satisfied and therefore the earlier you know about this potential problem, the less cost it will be to rectify and the sooner it can be fixed.
We have already mentioned milestones and checkpoints are their to celebrate achievement and check progress. If progress is being stalled then interventions can take place to get the project back on track, so milestone events and checkpoints are essential along the way to achieving your Project Goal.
Record any observed issues in your issue log so that this can be discussed with the project team. If results are positive, the project can continue in the same way. If results are not positive, however, consult the project manager or sponsor about potential corrective action. This is an iterative process that should continue until you have achieved full implementation of the project and achieved the Project Goal.