How Our Process Worked
Change management needed to see an overview of the current active release (in the Current Release lane) as well as upcoming change requests (in the Not Assigned lane) on the Kanban board. Each lane had its own priority: tasks higher on the board had higher priority. Notice the Follow Up section on the board—that is where services are verified in production after changes are released.
Let’s take a closer look at how work flowed through the board. Each lane represented a specific priority and demand type. Tickets in each lane had a specific color to make it easy to visualize what was happening. We could see progress on non-urgent ...
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.
