According to the PMBOK® Guide (6th and 7th Editions), Tailoring is the deliberate adaptation of the project management approach, governance, and processes to make them more suitable for the specific environment and the work at hand.
When a team debates using iterative, predictive, adaptive (Agile), or hybrid methods, they are specifically tailoring the Life Cycle Approach. This is a fundamental tailoring decision that determines how the project will move from initiation to closure.
Why Life Cycle Approaches is the correct aspect of tailoring:
Methodology Selection: For a " highly visible technologically advanced " product like AI, a predictive (waterfall) approach might be too risky due to high uncertainty. An iterative or hybrid approach allows the team to build and test parts of the AI tool in cycles.
Strategic Fit: Tailoring the life cycle ensures that the cadence of delivery matches the complexity of the product.
Hybridization: Hybrid approaches specifically combine elements of different life cycles (e.g., predictive for the product launch marketing and agile for the software development).
Analysis of Distractors:
B (Resource availability): This aspect of tailoring focuses on the physical and team resources available (e.g., co-located vs. virtual teams). While resources influence the life cycle, the debate about " iterative vs. hybrid " is a structural life cycle question.
C (Project dimensions): This refers to the size, complexity, and importance of the project. While these dimensions inform the decision to use a specific life cycle, they are the reason for tailoring, not the aspect of the project being tailored in this scenario.
D (Technology support): This typically refers to the tools and systems used to manage the project (like PMIS or collaboration software), rather than the overarching methodology or life cycle framework.
