According to the Agile Practice Guide and the PMBOK Guide, the iterative approach is specifically designed to improve quality through frequent feedback loops and the reduction of waste (rework).
Continuous Feedback: In an iterative environment, the team delivers small, functional increments of the product to the users or stakeholders at the end of every iteration (Sprint). This allows users to interact with the product and provide immediate feedback.
Clarification and Refinement: By seeing the product evolve, users can clarify their requirements and identify misunderstandings early. This ensures that the team isn ' t building the " wrong " thing based on a static, potentially misinterpreted document from months ago.
Small Batch Sizes: Working in short cycles (iterations) means that if a defect or a misunderstanding is found, it is limited to the work done in that short timeframe. This makes it significantly easier and cheaper to fix, thereby increasing the overall Quality of the Product and the Quality of the Process.
Built-in Quality: Agile emphasizes " shifting left " on quality, meaning testing and review happen concurrently with development rather than as a separate phase at the end.
Analysis of other options:
Option A: This is incorrect. Agile teams actually do more frequent planning (Iteration Planning, Daily Stand- ups, Backlog Refinement) than traditional teams; the planning is simply spread out rather than done all at once.
Option B: In an adaptive/iterative environment, the project manager (or team) documents goals progressively.
" Documenting in advance " is a characteristic of Predictive (Waterfall) management, which often struggles with quality if requirements change.
Option C: This is factually incorrect. Iterative development requires more frequent testing, as testing is integrated into every iteration. Waiting until the end of the project for testing is a high-risk Waterfall approach.
Per PMI standards, the iterative life cycle increases quality by ensuring a shared understanding of requirements through constant stakeholder engagement and the ability to pivot based on real-world usage and feedback.