Abstract :
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.
Keywords :
continuous improvement; iterative methods; project management; software prototyping; team working; Kanban; Scrum; agile processes; continuous improvement; eXtreme Programming; team needs; Companies; Computer bugs; Context; Planning; Production; Programming; Software; agile; contextual practices; continuous improvement; development; iterative process; retrospective; team;
