QA within a Scrum context has one big problem: stories tend to become testable only towards the end of a sprint, and often all at once! This can greatly reduce the amount of testing time available for each sprint. Kanban's 'stop starting, start finishing' principle, which encourages the team to limit work in progress and collaborate to get stories across the board, is potentially an ideal solution to this problem.
This talk discusses the benefits that Kanban brings to the QA process, including better dev-QA collaboration, faster feedback loops, and less wasted resource. James will also discuss the challenges and stumbling blocks of adopting Kanban for greenfield projects, and introduce a recommended workflow for effective QA within a Kanban context.