Agile Scrum in a Sprint: Forget the Theory and have your first Agile Scrum Team up and running in just two weeks: Leverage Scrum continuous improvement ... Scrum Business Transformation Book 1) by Michael Dempsey

Author:Michael Dempsey
Language: eng
Format: azw3, epub
Publisher: UNKNOWN
Published: 2017-06-29T07:00:00+00:00

Agile Principle 3: Time Waits For No Man!

In Agile development, requirements evolve, but timescales are fixed.

This is most pertinent in thinking about sprint work. The duration of the sprint is fixed. When a sprint begins, the team chooses the work that they will complete in the sprint and makes a commitment to the amount of work.

Things change and Scrum allows for change, but lets the team choose how to handle it. Requirements can change, priorities can shift quickly in the business and Agile allows for those changes. The team can take on additional work as long as it doesn’t impact their goal or commitment for the sprint. If it will, then something else has to come out of the sprint in order to take the new work in. Simply: something comes in, something goes out. That way the team is still focused on their delivery to a commitment. If the team feels it is too late in the sprint to make a change without impacting the commitment, either they have the power to reject the change until next sprint or if the change is so big and important, the sprint might need to be canceled altogether.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.