How This Improved Collaboration
These two policy statements—definition of ready for development and definition of ready for system test—have significantly improved collaboration between the teams. This improvement stood out clearly when I did a short survey to check what people thought about all the process changes so far.
In the past, when we just started doing Kanban, each specialty team focused mostly on “their” part of the project board. The requirements analysts looked only at the left part of the project board and considered themselves “done” with a feature when a requirements document had been written. The developers looked only at the middle of the board, and the testers looked only at the right. The testers weren’t involved in writing ...
Get Lean from the Trenches now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
