performance measurement

Quantitative metrics that describe how a system behaves in operation, capturing its physical and functional characteristics.

Key Points

  • Focuses on operational behavior such as latency, throughput, capacity, reliability, and error rates.
  • Should be objective, repeatable, and tied to acceptance criteria or nonfunctional requirements.
  • Collected regularly (e.g., per iteration) to reveal trends, forecast issues, and guide improvements.
  • Works best when defined with clear units, targets, thresholds, and automated collection in CI/CD.

Example

An agile team delivering an API tracks 95th percentile response time, requests per second, CPU/memory usage, and error rates each sprint. When response time rises above 500 ms at expected load, they add backlog items to optimize database queries and introduce caching until the metric consistently meets the target.

PMP Example Question

Which of the following best represents performance measurement for a new streaming service?

  1. 95th percentile video start-up time under 2 seconds at 50,000 concurrent users
  2. Team velocity improving from 30 to 35 story points per sprint
  3. Stakeholder satisfaction score of 8/10 after release
  4. A complete Definition of Done for all backlog items

Correct Answer: A — metrics describing system operational behavior

Explanation: Option A is a quantitative metric of how the system performs under load, reflecting its operational physical and functional characteristics; the others are not direct measures of system operation.

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


Take Control of Project Performance!

HK School of Management helps you go beyond status reports and gut feelings. In this advanced course, you will learn Earned Value Management (EVM) to measure progress, forecast outcomes, and take corrective action. Learn how WBS quality drives performance, how control accounts work, and how to use EAC, TCPI, and variance analysis. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More