Safety Requirements Influence on Development Approach Selection
PMBOK v8 Definition
Safety requirements refer to the rigorous product safety standards that often necessitate a predictive development approach, as there is a need for significant up-front planning to ensure safety compliance. When deliverables have strict safety requirements, the predictive approach enables robust change control mechanisms and planned reevaluation between successive phases to maintain safety integrity throughout the project life cycle.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions about development approach selection, particularly in situational questions where you must determine whether a predictive or adaptive approach is optimal. It is commonly tested in combination with other deliverable variables such as degree of innovation, scope stability, and ease of change, requiring you to evaluate multiple factors simultaneously.
Key Points to Remember (for the exam)
-
Safety Requirements = Predictive Approach: Products with rigorous safety requirements (medical devices, aerospace, nuclear facilities) require significant up-front planning and robust change control → predictive approach is optimal.
-
Key Distinction: Safety requirements drive predictive approaches, while high uncertainty or innovation drives adaptive approaches. Never confuse these drivers.
-
Scope Stability Link: The less stable the scope, the more optimal an adaptive approach becomes. Safety requirements typically demand scope stability, reinforcing the predictive choice.
-
Regulatory Oversight: Large projects involving significant investment or regulatory oversight (common with safety-critical products) are suitable for predictive approaches.
-
Change Control Necessity: Safety-critical projects require robust change control mechanisms and planned reevaluation between successive phases → inherent to predictive approaches.
-
Common Confusion: Safety requirements are NOT about project safety (team safety, workplace hazards) but about product/deliverable safety compliance.
Typical PMI Exam Example
A pharmaceutical company is developing a new vaccine that must comply with strict FDA safety regulations. The project scope, schedule, cost, and quality requirements can be well defined early. Which development approach is optimal?
Answer: Predictive approach, because rigorous safety requirements demand significant up-front planning and robust change control to ensure safety compliance.
PMI Exam Traps
-
Trap: Confusing product safety requirements with project safety (workplace hazards, team safety)
- Reality: Product safety requirements = deliverable compliance standards; project safety = operational risk management
-
Trap: Assuming adaptive approaches are always better for innovation, even when safety requirements exist
- Reality: Safety requirements override innovation considerations; predictive is required regardless of innovation degree
-
Trap: Thinking safety requirements can be managed with iterative testing in adaptive approaches
- Reality: Safety compliance requires significant up-front planning and documentation, not just testing cycles
-
Trap: Mixing safety requirements with risk management (both appear in development approach selection)
- Reality: Safety requirements = specific product compliance need; Risk = general uncertainty management (adaptive may help manage risk)
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Degree of Innovation | Opposing Factor | When innovation is needed, adaptive may be optimal; but safety requirements override and mandate predictive |
| Requirements Certainty | Reinforcing Factor | Both safety requirements and high requirements certainty point toward predictive approach |
| Ease of Change | Reinforcing Factor | Safety requirements make changes difficult/costly → predictive approach is optimal |
| Delivery Options | Complementary Factor | Safety-critical deliverables often cannot be delivered in components; predictive approach supports progressive elaboration with controls |
Quick Review Questions
-
A project involves developing a medical implant device subject to strict regulatory safety standards. The scope is well understood. Which development approach is optimal, and why?
-
When safety requirements are present, what specific characteristics of the predictive approach become essential for compliance?
-
How does the presence of safety requirements interact with the degree of scope instability when selecting a development approach?
-
A project team wants to use an adaptive approach for a safety-critical aerospace component. What PMBOK v8 principle would argue against this choice?
-
What is the key difference between "safety requirements" as a deliverable variable and "risk" as a project variable in development approach selection?
PMBOK v8 Reference
Section 4.3.1 - Deliverables (Variables for Development Approach Selection) Section 4.2.1 - Predictive Approaches