According to the Agile Practice Guide and the PMBOKGuide, the choice of an adaptive lifecycle depends on the nature of the work. Support and maintenance environments are characterized by high variability and the need for a " pull-based " system.
* Why Choice C is correct: Kanban is the ideal method for " continuous flow " work where tasks cannot be planned in time-boxed iterations (like Scrum Sprints).
* Work in Progress (WIP) Limits: The scenario states the team cannot start new issues until they finish existing ones. This is the core principle of WIP limits in Kanban. By limiting how much work can be " In Progress, " the team prevents bottlenecks and ensures they focus on completing tasks before taking on new ones.
* On-Demand Planning: Since support issues are unpredictable, Kanban allows the team to pull the next highest-priority item from the backlog as soon as capacity becomes available, rather than waiting for a new sprint cycle.
* Analysis of other options:
* A (SAFe): The Scaled Agile Framework (SAFe) is designed for large-scale, multi-team development. The description provided in the option ( " it does not allow for scaling " ) is factually incorrect, as SAFe is specifically built for scaling.
* B (Extreme Programming - XP): XP is a software development methodology focused on technical excellence (e.g., pair programming, test-driven development). While it emphasizes quality, it does not fundamentally dictate the flow of work for unpredictable support issues as effectively as Kanban.
* D (Scrum): Scrum relies on Sprints (time-boxes). If a team cannot plan their work even for a week, Scrum ' s " Sprint Planning " becomes impossible. Furthermore, the statement that Scrum allows for " completing the whole architecture up front " is incorrect; that describes a Waterfall
/Predictive approach, whereas Scrum is iterative.
In a production support environment, the Lead Time and Cycle Time metrics used in Kanban provide the visibility needed to manage a reactive workload without the overhead of rigid sprint structures.

According to the PMBOKGuide, the Estimate Costs process is the process of developing an approximation of the monetary resources needed to complete project work. This process uses a specific set of tools to ensure accuracy and consensus.
* Expert Judgment and Decision Making (Choice D): These are both core Tools and Techniques for the Estimate Costs process.
* Expert Judgment: Involves consulting individuals or groups with specialized knowledge in similar projects, accounting, or specific technical domains to provide insight into cost variables.
* Decision Making: Specifically Voting, is used to reach a consensus among team members or stakeholders regarding the cost estimates, especially in environments where multiple perspectives are needed to finalize an approximation.
* Lessons Learned Register and Cost Aggregation (Choice A): The Lessons Learned Register is an Input (specifically a Project Document), not a technique. Cost Aggregation is a tool and technique, but it belongs to the Determine Budget process, where activity cost estimates are summed up to establish a cost baseline.
* Project Schedule and Resource Requirements (Choice B): Both of these are Inputs to the Estimate Costs process. The project manager looks at the schedule and resource requirements to understand what needs to be estimated, but they are not the tools used to calculate the costs.
* Three-point Estimating and Risk Register (Choice C): While Three-point Estimating is a valid tool for this process, the Risk Register is an Input. The information in the risk register (such as potential threats or opportunities) informs the estimate, but it is not a technique for calculating the cost itself.
By utilizing Expert Judgment and Decision Making, the project manager ensures that the estimates are not just mathematical calculations but are tempered by professional experience and team agreement, leading to a more realistic and defensible project budget.

According to the PMBOKGuide (Project Management Body of Knowledge), specifically within the Project Resource Management knowledge area (historically Human Resource Management), the Staffing Management Plan (a component of the Resource Management Plan) defines how team members ' requirements will be met.
* Training Needs (Option D): This component of the plan identifies the strategies to help team members acquire the necessary competencies to perform project work. If team members lack the required skills or if the project would benefit from them holding specific certifications, the plan must outline the training, workshops, or certification programs required to bridge that gap. This ensures the team has the specialized knowledge to benefit the project ' s success.
* Recognition and Rewards (Option A): This section outlines the criteria for and the strategy for rewarding and recognizing team members for their performance and contributions. While obtaining a certification might lead to a reward, the " way to obtain " the certification itself is a training function.
* Compliance (Option B): This component focuses on strategies for ensuring the project complies with applicable government regulations, union contracts, and other established human resource policies.
* Staff Acquisition (Option C): This describes how the project team members will be acquired (internally or externally), the costs associated with each level of expertise, and the recruitment timelines. It does not focus on the ongoing development or certification of the staff once they are on the team.
In the PMI framework, identifying Training Needs is a proactive step in the Develop Team process, aimed at enhancing the overall competencies of the project stakeholders and the functional team.

According to the PMBOKGuide, project management involves iterative planning as more information becomes available. This specific iterative technique is formally known as rolling wave planning.
Rolling wave planning is a form of progressive elaboration where the work to be accomplished in the near term is planned in detail, while the work far in the future is planned at a higher level.
* Mechanism: It is a functional application of the " progressive detailing " mentioned in the question. As the project progresses and more risks and requirements are identified, the " wave " moves forward, and the high-level plans are decomposed into detailed work packages.
* Context: This is particularly useful in projects where the full scope is not entirely clear at the start (such as RandD or software development) or in high-uncertainty environments.
* A. Expert judgment: This is a tool and technique used in almost every project management process.
While experts may help with detailing a plan, " expert judgment " refers to the specialized knowledge or training used to make a decision, not the process of progressive detailing itself.
* C. Work performance information: This is an output of various controlling processes (like Control Schedule or Control Costs). it is the processed data used to make decisions, but it is not a planning technique.
* D. Specification: A specification is a document that describes the requirements, design, or behavior of a product or service. While a specification can be detailed progressively, it is a document/input, not the act of detailing the overall management plan.
Rolling wave planning is the primary technique used to achieve Progressive Elaboration. In the PMI framework, this acknowledges that as a project evolves, the project management team gains a better understanding of the objectives and deliverables, allowing them to manage the project with greater " granularity " over time.

In the Collect Requirements process of the PMBOKGuide, selecting the right elicitation technique depends on the nature of the requirement. Cross-functional requirements are those that impact multiple departments, systems, or stakeholders simultaneously (e.g., a security feature that affects IT, Legal, and end-users).
* Why Choice C is correct: Facilitated Workshops (also known as Joint Application Design/Development or JAD sessions) are specifically designed to bring together key cross-functional stakeholders.
* Consensus Building: Because cross-functional requirements often involve conflicting needs from different departments, a workshop allows for real-time negotiation and resolution.
* Efficiency: Instead of conducting separate interviews, the Business Analyst can get all relevant parties in one room (or virtual space) to define the requirement collectively.
* Discovery: Interdependencies between departments often surface during the dialogue that happens in a workshop setting, which might be missed in isolated sessions.
Analysis of other options:
* A (Focus groups): These bring together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product. While useful, they are more about " sentiment " than the rigorous technical and functional negotiation required for cross-functional alignment.
* B (Prototyping): This is a method of obtaining early feedback on requirements by providing a working model. It is a " validation " tool rather than an initial elicitation method for complex, multi-departmental logic.
* D (Interviews): Interviews are excellent for deep dives with a single stakeholder. However, they are notoriously poor for cross-functional requirements because the interviewer hears only one perspective at a time, making it difficult to spot contradictions between departments until much later.
Key Concept: The Project Management Institute (PMI) identifies facilitated workshops as a primary tool for developing a shared understanding. When requirements " cross lines " on an organizational chart, the collaborative environment of a workshop (Choice C) is the most effective way to ensure the requirement is complete, accurate, and agreed upon by all parties.