How Late Is That Task?
Analyzing a schedule to determine which tasks are late is an important responsibility for all project managers. PMs routinely analyze the schedule to evaluate the impacts of late tasks. Scheduling data fuels the decisions made by the PM to ensure successful project outcomes.
While many Microsoft Project (MSP) fields are built in, there aren’t any fields that calculate where the task should be by now. In addition, for a resource-loaded schedule, a late task can negatively affect resource management (work). Furthermore, the built-in fields cannot answer questions like “How much work should have been done by now?” or “What is the remaining work from time now?”
This article describes a schedule monitoring technique using MSP’s custom fields to find out exactly how much time (work hours) a task is behind. I encourage for everyone to explore using MSP’s custom fields.
How Late Is Late?
“A schedule defends from chaos and whim. A net for catching days.”
— Annie Dillard, The Writing Life (1989)
PMs routinely review schedules in MSP and make informed decisions based on the data contained therein. But imagine if the data could be tailored and more specific to the PM’s needs. Using MSP’s built-in views, fields and reports, it is relatively easy to find which tasks are late and to assess if those
Please log in or sign up below to read the rest of the article.