2.1.3. Principles 7-9: Tailoring, Quality, Complexity

💡 First Principle: A successful project approach is not rigid but is intentionally adapted to the project's unique context, with quality built in from the start and a strategy for navigating inherent complexity.

Scenario: You are assigned to lead two projects. One is a highly regulated construction project with fixed requirements, and the other is a software development project with high uncertainty. You apply the 'Tailoring' principle to select a predictive lifecycle for the first and an adaptive lifecycle for the second, embedding 'Quality' practices appropriate for each, and using iterative techniques to 'Navigate Complexity' in the software project.

This part discusses principles related to adapting approaches, embedding quality, and navigating complex project environments.

7. Tailor Based on Context

• Definition: Adapt the project management approach, lifecycle, processes, tools, and artifacts to the unique needs of the project, organization, and environment.
• First-Principle Rationale ("Why"): No single approach works for all projects. Tailoring optimizes efficiency, effectiveness, and value delivery.
• Practical Application: Selecting the appropriate development lifecycle, scaling governance, adjusting communication frequency or methods, choosing relevant tools. See Section 3.1.

8. Build Quality into Processes and Deliverables

• Definition: Focus on preventing defects and ensuring fitness for purpose through proactive measures and attention to technical excellence.
• First-Principle Rationale ("Why"): Quality is more effectively and cheaply achieved through prevention rather than inspection and rework. It ensures deliverables meet needs.
• Practical Application: Implementing Definition of Done, using quality planning/assurance techniques, incorporating feedback loops, considering Cost of Quality, refactoring. Quality is planned in, not inspected in.

9. Navigate Complexity

• Definition: Acknowledge, explore, and adapt to complexity arising from human behavior, system interactions, uncertainty, and ambiguity.
• First-Principle Rationale ("Why"): Many projects are inherently complex; ignoring or oversimplifying complexity leads to failure.
• Practical Application: Using iterative and incremental approaches, employing modeling/simulation, breaking down complex problems into smaller parts, fostering diverse perspectives. Embrace adaptive techniques.

⚠️ Common Pitfall: Treating "quality" as a final inspection phase. The principle emphasizes building quality into every step of the process to prevent defects, not just find them at the end.

Key Trade-Offs:

• Prescription vs. Flexibility (Tailoring): Following a standard organizational process provides consistency, but tailoring it to the project's specific needs can improve efficiency and effectiveness. The trade-off is finding the right balance.

Reflection Question: How does the principle of 'Navigating Complexity' justify the need for 'Tailoring Based on Context'?