Actual Duration

The elapsed calendar time from the moment an activity actually starts to the project’s data (status) date if it is still underway, or to its actual finish date if it has been completed.

Key Points

  • Measured in calendar units (e.g., days or weeks), not effort hours.
  • Begins at the activity’s actual start; ends at the data date if in progress or at the actual finish if complete.
  • Grows with each status update until the activity is finished.
  • Compared with planned and remaining duration to evaluate schedule performance.

Example

An activity begins on January 5 and finishes on January 14. The Actual Duration is 10 calendar days (Jan 5–Jan 14). If on January 12 the activity were still in progress and the project’s data date were January 12, the Actual Duration at that time would be the calendar time from Jan 5 to Jan 12.

PMP Example Question

Which statement best describes Actual Duration for a schedule activity?

  1. The time scheduled between the planned start and planned finish dates.
  2. The calendar time from the actual start to the data date if in progress, or to the actual finish if complete.
  3. The total labor hours expended by team members on the activity.
  4. The forecasted time needed to complete the remaining work.

Correct Answer: B — Calendar time from actual start to the data date or actual finish

Explanation: Actual Duration measures elapsed calendar time based on what has actually occurred, not planned dates, effort hours, or forecasts.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your career!

HK School of Management provides world-class training in Project Management with AI and Agile Methodologies. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More