
Technical Risk: Technology Advances, Availability, Reliability, and Scheduling
PMBOK v8 Definition
Technical risk is defined in PMBOK v8 as a category of project risk that relates to technology, including advances in technology (Section 53), availability and reliability of technology (Section 156), and the impact of technology on scheduling (Section 56). Technical risk encompasses uncertainty around whether technology will perform as expected, whether required technology is available and reliable when needed, and how technological factors affect project schedule performance. This risk category is identified during the Identify Risks process (Section 95, 137-138) and managed through the Plan Risk Responses and Implement Risk Responses processes.
Why It Matters for the Exam
Technical risk appears frequently on the PMI exam in questions about risk identification, risk categorization, and risk response planning. Expect scenario-based questions where technology failures, availability constraints, or reliability issues create schedule impacts or performance deviations. The exam tests your ability to recognize technical risk as a distinct category and to apply appropriate strategies, particularly when technology availability and reliability affect project timelines.
Key Points to Remember (for the exam)
- Definition: Technical risk relates to technology performance, availability, reliability, and scheduling impacts
- Key Sources: Technology advances (Section 53), availability and reliability of technology (Section 156), and scheduling dependencies on technology (Section 56)
- Identification Tool: Risk breakdown structure (RBS) prompt lists help identify technical risk categories (Section 191)
- Performance Analysis: Technical performance analysis (Section 205) measures actual performance against planned technical parameters
- Testing Connection: Test and inspection planning (Section 205) directly addresses technical risk by verifying product performance and reliability
- Common Confusion: Technical risk is NOT the same as schedule risk—technical risk focuses on technology uncertainty, while schedule risk focuses on timing uncertainty. However, technical risk can cause schedule delays
- Exam Tip: When you see "technology advances," "availability," "reliability," or "scheduling" linked to technology in exam questions, think TECHNICAL RISK
Typical PMI Exam Example
A construction project uses new drone technology for site inspections. The drone technology is still emerging, and the team is unsure about its reliability in adverse weather conditions. The project schedule depends on timely inspection results. The project manager identifies this as technical risk because it involves technology availability and reliability affecting scheduling. The appropriate response is to develop contingency plans for manual inspections if the drone technology fails.
PMI Exam Traps
-
Trap: Confusing technical risk with schedule risk
Reality: Technical risk is about technology uncertainty; schedule risk is about timing uncertainty. Technical risk can cause schedule impacts, but they are separate risk categories -
Trap: Thinking technical risk only applies to software or IT projects
Reality: Technical risk applies to ALL industries—construction (material performance), manufacturing (equipment reliability), engineering (design validation) -
Trap: Assuming technology availability and reliability are the same thing
Reality: Availability means technology is accessible when needed; reliability means it performs consistently. Both are distinct aspects of technical risk (Section 156) -
Trap: Forgetting that test and inspection planning is a technical risk response
Reality: Testing and inspections (Section 205) are proactive responses to technical risk—they verify performance and reliability before full deployment
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Test and Inspection Planning (Section 205) | Response to Technical Risk | Testing verifies technology performance and reliability; often tested as a risk response strategy |
| Technical Performance Analysis (Section 205) | Monitoring Tool | Measures deviation from technical targets; detects technical risk triggers early |
| Risk Breakdown Structure (Section 191) | Identification Tool | RBS prompt lists include technical risk categories; helps ensure comprehensive identification |
| Identify Risks Process (Section 95, 137-138) | Source Process | Technical risk is identified during this process using prompt lists and brainstorming |
| Implement Risk Responses (Section 95, 98, 100) | Response Process | After identifying technical risk, responses are implemented to address technology uncertainties |
Quick Review Questions
-
A project manager identifies that a new software platform may not be available when needed for system integration testing. What type of risk is this?
-
During which process would a project team use a risk breakdown structure prompt list to identify technical risks related to technology reliability?
-
What is the relationship between technical risk and test and inspection planning?
-
A project experiences schedule delays because a critical technology component failed reliability testing. Is this a technical risk, a schedule risk, or both?
-
When analyzing technical risk, what tool measures actual technology performance against planned performance parameters?
PMBOK v8 Reference
Section 53 - Technology Advances Section 56 - Technology and Scheduling Section 135 - Technical Risk Section 156 - Technology Availability and Reliability Section 205 - Test and Inspection Planning, Technical Performance Analysis Section 191 - Risk Breakdown Structure and Prompt Lists