How do Agile teams handle changes to requirements?

While changing requirements may pose a considerable threat with some development methodologies, agile development makes changes more manageable.

Published: 25 Aug 2010

Agile methodologies are known to embrace change, but doesn't this come with a price? What happens when other groups have dependencies? Won't changes late in the cycle wreak havoc with the schedule?

Embracing change doesn't mean changing willy-nilly in the middle of developing a user story. We work in small increments, and deliver frequently in short iterations. If our customer sees some early deliverables and decides to make changes, we can do that in the next iteration, maybe only one or two weeks away.

Here's a recent example from my team. Our application automates all aspects of managing 401(k) plans. Our product...

Step 2 of 2:

You forgot to provide an Email Address.

This email address doesn’t appear to be valid.

This email address is already registered. Please log in.

You have exceeded the maximum character limit.

Please provide a Corporate Email Address.
- I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.
Please check the box if you want to proceed.
- I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.
Please check the box if you want to proceed.

owner asked for a new report to show a detailed history of employee deferral election requests for all employees within a given plan, and the date each request was approved. As we started on the story and did some research, we realized that an employee's deferral election could also be changed by someone other than the employee, such as the plan sponsor or a third-party administrator. Our system did not log details about those changes, and it was a lot of work to add that functionality. We delivered the report as per the original requirements, but in the next sprint, we did all the work to capture the missing information in the database and provide it on the report.

When I worked for a company with 25 Scrum teams, the daily Scrum of Scrums and the automated continuous build kept teams communicating. If one team "broke the build," they knew about it immediately and addressed it right away. Production releases occurred quarterly, with time built in at the end of each release cycle to resolve any integration issues.

Next Steps

How to hold effective Agile sprint planning meetings

10 tips for effective change management in Agile

How to tame ever-changing requirements in software development

10 Scrum benefits and how to realize them

How to implement Scrum the right way

Agile Project Management

Agile FAQ: Get started with these Agile basics