Dallas, TX USA
Aug. 13, 2012 to Aug. 17, 2012
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/Agile.2012.34
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.
Context, Production, Planning, Computer bugs, Software, Companies, Programming, continuous improvement, contextual practices, retrospective, agile, team, development, iterative process
Cecilia Fernandes, "There and Back Again: From Iterative to Flow ... and Back to Iterative!", AGILE, 2012, 2012 Agile Conference, 2012 Agile Conference 2012, pp. 103-110, doi:10.1109/Agile.2012.34