HKSM
technical performance measures
Objective, quantifiable indicators of a solution's technical behavior, monitored to confirm that components and subsystems satisfy defined technical requirements.
Key Points
- Quantitative metrics directly tied to technical requirements (e.g., throughput, latency, weight, reliability).
- Defined with targets and acceptable ranges, then tracked over time against planned values.
- Provide early warning of technical risk and trigger corrective or preventive actions.
- Decomposed by subsystem and verified through tests, prototypes, and integration builds.
Example
An agile team building an IoT device tracks response time (<= 200 ms), CPU utilization under peak load (<= 70%), wireless packet loss (< 1%), and battery life (>= 24 hours). Each sprint, they measure these technical performance measures and compare actuals to targets. When CPU utilization trends above 70%, they refactor code and optimize drivers to bring the design back within limits.
PMP Example Question
During development, a team tracks sensor accuracy, processor load at peak throughput, and end-to-end response time against planned targets to verify the design is on track. What are these metrics called?
- Business key performance indicators (KPIs)
- Technical performance measures used to verify components meet technical requirements
- Scope validation acceptance criteria
- Schedule performance indices (SPI)
Correct Answer: B — Technical performance measures
Explanation: These are quantifiable technical metrics compared to targets to ensure system components meet specified technical requirements.
