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.

ICS/OT Incident Response Drills and Exercises

An incident response plan is only a theory until the people who must use it have run it under pressure. This course helps OT engineers, operations leaders, IT responders, and security teams turn a plan on paper into a tested capability.

Define safe states and manual fallback before an incident forces the decision. Build escalation paths, tabletop exercises, and scenarios that expose the gaps a document review cannot find.

Then turn the results into evidence: an after-action report, owned improvements, recovery checks, and a drill cadence that keeps the program alive after the exercise ends.

24 lessons, 2.4 hours. US$47 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Response Drills and Exercises course preview

Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management, not on Udemy.

See What Is Included