Implementing Test Automation could be a challenge in a traditional Scrum environment. Does automation start in the same sprint, is it one behind, how is velocity measured for maintenance? These are just some questions that have plagued teams. To avoid some of these pitfalls, consider moving to a Kanban board for your Test Automation work requests composed by a centralized team. This central team would serve the Scrum teams and in true Kanban fashion. During this session, Jim Trentadue will identify some key problem areas of Test Automation within a Scrum methodology and provide real-world solutions to them. Jim will explain how a Kanban board is structured and what drives prioritization and the benefits the Kanban board provides to the Scrum teams and department overall. By implementing this approach, you could start to see teams more successful with test automation due to the work required going into a request before the work starts – without the worry of failing sprints. This approach would increase throughput as well as provide the broader perspective of automation across the department.