Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I know that in agile requirement changes should not only be planned for but also embraced. But I still don't know agile how to handle these changes.

share|improve this question

marked as duplicate by MichaelT, GlenH7, gnat, Marjan Venema, Glenn Nelson Nov 8 '13 at 18:05

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

You shouldnt cross post but instead wait for you question to be migrated. Please go back and delete the original question if it is no longer required. – Dave Hillier Nov 8 '13 at 16:23
I think different development model has different way to deal with changing requirement? for example, Lean and prescriptive? – WindowReachSky Nov 8 '13 at 16:53
Agreed, as much as I think this is a basic question that could be answered with 30 seconds on google, it is distinct from the one it is marked as duplicate of. – Dave Hillier Nov 9 '13 at 20:05

"Responding to change over following a plan", Is one of the four points of the Agile Manifesto.

In a typical methodology, such as Scrum, there are a number of tools that help do that. You don't deliver everything in one hit, instead deliver incrementally, incorporating feedback into the product backlog.

The Product backlog is a prioritised wish list of features that the product owner wants. Unlike a specification, this isn't fully detailed and can be changed at the product owners discretion. The highest priority items are elaborated enough such that development can be executed and may be selected for the next Sprint.

During a Sprint developers commit to deliver a selection of the high priority items and it is at this point that changes are typically locked down. A Sprint typically lasts 1-4 weeks (I most frequently see 2 week sprints). At the end of a Sprint, there should be a potentially shippable product.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.