AGILE COMMUNITY © MindTree 2011
AGILE MYTH 7
Changes Can Happen On a Daily Basis
Agile Manifesto values ‘Responding to Change’ over ‘Following a Plan’. This does not mean that Agile manifesto supports frequent or daily changes. In fact, it indicates that responding to changes is more important than following a plan. What does it mean?
When is the last time you executed a software project with frozen requirements? A vast majority of projects we execute do involve changes to requirements and design. Quite often we accommodate our plans to suit changing requirements and design. This does not mean that we become highly flexible to absorb changes on a daily basis.
Traditional methodologies consider Too much of rigidity motivates us to complete all originally signed-off requirements and consider changes after project completion.
upfront planning. Agile believes in justenough planning because Agile teams and stakeholders understand that change is inevitable.
No stakeholder who has invested in a software project will reward you or appreciate you for following the original plan and failing to deliver valuable software. So, we need the ability to embrace change
In Agile projects, changes are monitored and controlled
as we move forward and adjust our plans to deliver
at iteration level. After
value to business users or customers. How do we do
there must not be any change. If there is
this in Agile? We do this by performing detailed planning when we start an iteration or Sprint. Meanwhile, we maintain a high-level project plan. This
iteration planning,
any change, it has to be approved by project sponsors at the highest level.
helps us respond to changes as they progress.
AGILE MYTHS BUSTED
14