How We Continuously Improved
Everything so far was on the defense as we fought problems as they cropped up. After a few weeks, we saw team members kicking off their own refactoring initiatives and taking control of the board. Every change they made in their processes was reflected on the board. For example, the Test column was split into two to reflect manual testing. A triggering mechanism in the Build column indicated whether a partial (client) or a full build was needed. The Kanban board became a living process and galvanized the team’s commitment for each change.
We don’t always have all the information we need at once in software development. ...
Get Real-World Kanban 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.
