When Software is Done

Jeffrey remarks that he's working with a software team whose code is "done", that is, the organisation wants to keep using it but doesn't want to invest more in changing it. He and Squirrel reflect on when this make sense and how "software doneness" affects processes and measurements. SHOW LINKS: - Control Chart: https://en.wikipedia.org/wiki/Control_chart - Principles of Product Development Flow: https://www.pdma.org/page/review_principles_pr --- Our book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. 
 Email us at info@agileconversations.com