SPONSORS:






View RSS Feed

Ronak

True Agile - Principle - Handle Changing Requirements

Rate this Entry
by , 03-23-2015 at 11:02 AM (162 Views)
True Agile - Principle - Handle Changing Requirements

Welcome changing requirements, even late in development. Agile processes harness change for the customerís competitive advantage.

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 major things 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.
When I worked for a company with multiple 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.
In short, embrace the change to meet the customer expectations in a feasible manner.

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 03:48 AM.

Copyright BetaSoft Inc.