According to the PMBOKGuide and the Agile Practice Guide, the involvement of stakeholders in adaptive (agile) environments differs significantly from predictive (waterfall) environments. In agile projects, requirements are discovered and evolved throughout the life cycle, making stakeholder proximity a critical success factor.
* Continuous Engagement: In an adaptive life cycle, the customer, sponsor, and other stakeholders provide ongoing feedback on functional prototypes and increments of the product. This ensures that the product being built continues to align with business needs, even as those needs change.
* Scope Management: Because the scope is not " frozen " at the start, the Product Owner (representing the customer/business) must be continuously engaged to prioritize the backlog, clarify requirements during iteration planning, and provide immediate feedback during daily stand-ups or informal reviews.
* Validation: Formal validation of scope occurs at the end of every iteration (e.g., Sprint Review), but the
" continuous " nature of their engagement prevents the team from drifting away from the customer ' s true requirements.
Analysis of other options:
* A. Involvement only during initiation: This is incorrect for any methodology, but especially agile.
Scope in agile is refined throughout the project, not just at the beginning.
* B. Minimal involvement: Agile thrives on " Customer Collaboration over Contract Negotiation " (Agile Manifesto). Minimal involvement is often a leading cause of project failure in adaptive environments.
* D. Only during phase or deliverable reviews: While reviews are formal touchpoints, limiting engagement only to these events mimics a predictive approach and loses the " adaptive " advantage of real-time course correction.
Per PMI standards, continuous engagement reduces the risk of scope creep and ensures that the most valuable features are delivered to the customer as early as possible.