Be the first to like this
Once you start using SCRUM and its time-boxing approach there is a natural urge to put everything into the sprint to get better control of it: initial analysis, architecture, testing, meetings, etc... However, it turns out that it’s not that simple and some tasks are just not meant to be handled in sprint. In this session we will explore how usage of SCRUM evolved in one of the development teams in Baltic Amadeus while working on a big enterprise solution and how we managed to stabilize sprint scope by offloading particular development tasks to KANBAN. We will also show what stages each user story must pass to make it work well in an enterprise environment.