Online College Courses for Credit

4 Tutorials that teach Monitoring Time
Take your pick:
Monitoring Time

Monitoring Time

Author: Jeff Carroll

This lesson provides an overview for monitoring project schedule

See More
Fast, Free College Credit

Developing Effective Teams

Let's Ride
*No strings attached. This college course is 100% free and is worth 1 semester credit.

29 Sophia partners guarantee credit transfer.

312 Institutions have accepted or given pre-approval for credit transfer.

* The American Council on Education's College Credit Recommendation Service (ACE Credit®) has evaluated and recommended college credit for 27 of Sophia’s online courses. Many different colleges and universities consider ACE CREDIT recommendations in determining the applicability to their course and degree programs.


Video Transcription

Download PDF

Hi, I'm Jeff. And in this lesson, we'll learn how a project manager monitors the time spent on a project. A project schedule must be updated often. And the status of the schedule must be reported to the stakeholders and to the team.

In order for the project manager to gain the information they need on the project's progress, team members must report on the time or effort spent on assigned tasks. The project manager can then compare the actual time spent to the estimates created during the planning phase.

For example, this is a time sheet report that shows the actual effort on a task to test email operations for a mobile email application, and the estimates on the task from the planned schedule. There are two ways to record the actual time spent on a task. The team member can record the actual time or efforts spent on task usually in hours or days. Or they can record the percent complete on the task.

Or they can record both, which is the most accurate way to gain knowledge on the schedule progress. Reports on percentage complete can be highly subjective, though. Experience workers will be able to estimate the amount of work done better than inexperienced workers, for example. And it will be up to the project manager to account for these discrepancies.

To compensate for the subjectivity, the project manager can make following comparisons-- compare the actual percent complete for a task or deliverable to the overall task or deliverable. If a task is 90% complete, but the deliverable is not nearly ready for review, then that is an issue. Compare the actual percent of effort used relative to the original effort estimate.

If a task is 50% complete, but the hours spent on the task is already equal to the estimated effort for the task, then that is an issue. Compare the actual percent of time used relative to the original timeline estimate. If two weeks have already been spent on task, and the original estimate was three weeks of time, but the task is only 25% complete, then there is an issue.

Once a project manager has these details, they can then determine if these issues must be resolved by action on the part of the team, the project manager, or the stakeholders. Remember our example where a task was 50% complete, but the hours spent in effort was already equal to the hours estimated for the task?

A solution might be resource realignment, which may result in a team member spending more time and effort on a task with the goal of meeting time and percentage check marks. Or this could mean bringing on a new individual to help complete the task. And in some cases, scope may need to be reduced for the work. In that case, stakeholders would need to be involved in the decision.

Organizations will have different requirements for the frequency by which status on tasks are tracked, the methods used to track the schedule, and the frequency that status reports are created about the schedule. When a project is behind schedule, more frequent updates may be required. While monitoring a schedule, the project manager must always be aware of impacts to the critical path.

If you recall from an earlier lesson, the critical path is the longest chain of sequential dependent tasks on the project. This indicates how long a project will take to complete. Since the critical path defines the end-date for the project, it's essential to monitor and manage the tasks on this path closely.

Tasks not on the path should also be managed, so as not to impact the tasks on the path. For example, let's assume that we have a project to develop a new customer complaint form for a website. The critical path diagram might look like this.

The longest sequential path through the project is 13 days. It's not a good idea to take resources from critical path tasks to assist with non-critical path tasks. For example, unless the task to write user instructions takes longer than 13 days, it will not impact the critical path. If the design form task takes seven days instead of five days though, the critical path is impacted, and does increase by two days also.

For our example project, let's assume that we take action to bring the schedule back in line with the original overall time estimate. We do this by adding resources to the program form task to drop the time to complete the work to three days. The network diagram would then look like this, and we would be back to 13 days for our critical path and our overall project time.

If overruns continue to occur, a project manager might need to recommend changes to the project scope in order to bring the project back into alignment with the schedule. This is done through change management. And we'll discuss this in detail in another lesson.

So that's all for this lesson. Good job. In this lesson, we learned how to monitor a project schedule and how to monitor and update the critical path. Thanks for listening. And have a great day.

Notes on "Monitoring Time"


Source: Image of female project manager, Creative Commons, Kelly Eddington; Image of timesheet1, timesheet2, critical path diagram, Creative Commons, Jeff Carroll; Image of arrow, images by Video Scribe, License held by Jeff Carroll; Image of project schedule, Public Domain,; Image of 50 percent, Public Domain,