Welcome to The Rabbit Hole, the definitive developers podcast. If you are a software developer or technology leader looking to stay on top of the latest news in the software development world, or just want to learn actionable tactics to improve your day-to-day job performance, this podcast is for you.
203. Definition of Done
Today we are speaking about getting things done! What does it mean when we say something is done and how can you and your team get a better handle on the concept for better products? At times, as developers, we might feel like we are done as soon as the code is written and passed, but in reality, there are more steps in the process, and to get to a real state of being finished we need to formulate a proper framework or checklist for being done! This is one of the issues with working with different teams, as responsibility can sometimes get a bit lost, and so putting some time in, to develop an appropriate way to measure completion can lead to fewer issues and confusion down the road. In today's episode, we also look at the important aspects of feedback and corrections, and how 'done' might be a relative term, especially as your products gets increasingly complex. So for all this and a few more thoughts on how you can move things into that beautiful 'done' column, come with us, down the Rabbit Hole!