Defining Done: Why it's Hard and What to do About It

The next time someone asks, “Is it done?” don’t answer with a half–baked guess.


Is the software done yet? This seemingly innocent question is asked countless times on almost every software project, but an inaccurate answer could sink your team, your project, or even your career. In this session, Mitch Lacey explains why answering the done question has been so difficult in the past. He then shares tips for establishing a common understanding of done upfront. Mitch ends with an exercise you can use to define what your own team means by, “It’s done.”


Recorded at Norweigian Developers Conference (NDC), June 2011, Oslo, Norway.