By Topic

There and Back Again: From Iterative to Flow ... and Back to Iterative!

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Cecilia Fernandes ; Caelum - Ensino e Inovacao, Sao Paulo, Brazil

Agile processes have been developed and used for a long time now as a guideline for teams to follow when they start a project - Scrum, eXtreme Programming, Kanban are well known examples. However, as the project evolves, it is natural that, as a response to its peculiarities, the process itself is tailored to satisfy that team's needs. This experience report tells the story of a team that chose to start the project with Scrum, and then gradually and with continuous improvement in mind, deconstructed the process in order to better fit it's context. Then as context changed, some of the decisions were undone, but our experience shows both decisions, removing a practice and bringing it back afterwards, brought benefits to the process given the circumstances that surrounded them.

Published in:

Agile Conference (AGILE), 2012

Date of Conference:

13-17 Aug. 2012