Overview of Agile and Lean

According to the Agile Manifesto, embracing change is a fundamental principle, even late in development. Changes are seen as opportunities to deliver greater value to customers.

The correct answer reflects the Manifesto's core value of responding to change over following a plan. Agile embraces change at any point in the development cycle, viewing it as a means to ensure customer satisfaction and competitive advantage.

The other options represent traditional, plan-driven approaches that contradict Agile principles:

• Requiring thorough documentation and stakeholder approval creates unnecessary bureaucracy and slows responsiveness
• Restricting changes to early phases contradicts Agile's adaptive nature and continuous improvement philosophy
• Requiring extensive analysis and formal approval boards creates barriers to quick adaptation and introduces unnecessary organizational overhead

The Agile approach promotes flexibility and adaptation throughout the entire development lifecycle, making change a natural and welcome part of the process rather than an exception that needs special handling.

The Agile Manifesto clearly states 'Working software over comprehensive documentation' as one of its core values.

This emphasizes that while documentation has its place and importance in software development, the primary focus should be on delivering functional, working software that provides value to customers.

Other answers are incorrect because:

Extensive and comprehensive documentation contradicts the Agile principle of lightweight documentation and can slow down development.

Treating documentation and working software as equal misrepresents the Agile value hierarchy where working software takes precedence.

Using documentation as the primary measure of progress conflicts with Agile's focus on delivering working features and actual business value as progress indicators.

The correct answer aligns perfectly with the Agile Manifesto's balanced view that documentation has value, while clearly establishing the higher priority of working software.

The Agile Manifesto emphasizes delivering working software frequently, specifically stating a preference for shorter timescales between a couple of weeks to a couple of months. This timeframe allows for quick feedback, early value delivery, and rapid adaptation to changes.

The other options are problematic because:

• Waiting for extensive QA and documentation reviews before delivery goes against agile's principle of reducing unnecessary process overhead

• Six-month delivery cycles are too long and contradict the agile principle of frequent delivery and quick feedback loops

• Monthly releases that require all features to be complete and approved create unnecessary delays and reduce flexibility

Frequent delivery in shorter cycles promotes better risk management, faster learning, and more opportunities to gather user feedback and make improvements.