Chapter 8. Sustained engineering
By James Waletzky
Most teams that release a product or service to customers perform software maintenance after release. An effective team minimizes defects during development, but some level of post-ship fixes are inevitable. This situation poses problems even for a mature team in its need to prioritize and schedule unplanned maintenance work in conjunction with developing product road map features (new development). What is an effective model for dealing with this distraction from new feature development, hereafter known as “sustained engineering” (SE)? I’m sure you already guessed—Kanban.
The model I recommend for using Kanban to address post-release defects has several aspects. The teams involved need to define ...
Get Agile Project Management with 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.
