Technical Performance Analysis: Objective Measures and Schedule Comparison

Technical Performance Analysis: Objective Measures and Schedule Comparison

PMBOK v8 Definition

Technical Performance Analysis compares technical accomplishments during project execution to the schedule of technical achievement. This analysis requires the definition of objective, quantifiable measures of technical performance, which can be used to compare actual results against targets. Such technical performance measures may include weight, transaction times, number of delivered defects, storage capacity, etc. Deviation can indicate the potential impact of threats or opportunities.

Why It Matters for the Exam

This concept frequently appears in PMI exam questions related to the Monitoring and Controlling Process Group, specifically within Monitor and Control Project Performance. PMI tests your ability to distinguish Technical Performance Analysis from other performance analysis techniques (cost, schedule, financial) and to identify which objective measures qualify as valid inputs for this analysis. Expect scenario-based questions where you must select the appropriate analysis method based on the type of data available.

Key Points to Remember (for the exam)

  • Core Purpose: Compares actual technical results to planned technical milestones, not schedule dates or budget figures
  • Required Input: Objective, quantifiable measures—not subjective opinions or qualitative assessments
  • Common Measures: Weight, transaction times, number of delivered defects, storage capacity
  • Key Output: Deviation identification, which signals potential threats or opportunities
  • Process Linkage: Part of Monitor and Control Project Performance (Monitoring and Controlling Process Group)
  • Common Confusion: Technical Performance Analysis ≠ Schedule Performance Analysis; schedule compares dates, technical compares achievement of technical specifications
  • Data Source: Work performance data collected during project execution feeds into this analysis

Typical PMI Exam Example

A project team is developing a new satellite. The technical baseline specifies the satellite must weigh 2,500 kg. During execution, the team measures the current prototype at 2,800 kg. The project manager performs Technical Performance Analysis, comparing the actual weight against the target. The 300 kg deviation indicates a potential threat (overweight satellite may fail launch requirements) requiring corrective action.

PMI Exam Traps

  • Trap: Confusing Technical Performance Analysis with Schedule Performance Analysis (SPI/EVM)

  • Reality: Technical Performance Analysis compares technical accomplishments to technical achievement targets; schedule analysis compares actual dates to planned dates

  • Trap: Thinking Technical Performance Analysis uses subjective measures like "customer satisfaction"

  • Reality: Only objective, quantifiable measures qualify—weight, transaction times, defects, storage capacity

  • Trap: Believing deviation always indicates a problem (threat)

  • Reality: Deviation can indicate potential impact of threats or opportunities—positive deviations may signal opportunities

  • Trap: Assuming this analysis is part of Quality Management

  • Reality: While related, Technical Performance Analysis is specifically part of Monitor and Control Project Performance, not the Manage Quality process

Important PMI Connections

Related ConceptRelationship TypeExam Attention Point
Monitor and Control Project PerformanceParent ProcessTechnical Performance Analysis is a tool/technique within this process
Work Performance DataInputRaw data collected during execution feeds the analysis
Work Performance InformationOutputAnalysis produces information about completion status and deviations
Financial Performance MeasuresComplementary ConceptFinancial measures track costs/funding; technical measures track technical achievement
Test and Inspection PlanningRelated ActivityPlanning defines how technical measures will be verified and validated

Quick Review Questions

  1. A project manager compares the actual transaction processing time of a new software system to the target of 2 seconds per transaction. Which type of analysis is being performed?

  2. A deviation in Technical Performance Analysis can indicate the potential impact of what two categories of events?

  3. What is the key difference between Technical Performance Analysis and Schedule Performance Analysis?

  4. Which of the following would NOT be a valid measure for Technical Performance Analysis: weight, transaction times, stakeholder satisfaction score, number of delivered defects?

  5. In which Process Group does Technical Performance Analysis primarily occur?

PMBOK v8 Reference

Section 2.5 - Monitoring and Controlling Performance Domain (Technical Performance Analysis)