The Definition of Done
adi.bio
The Definition of Done
1–10 of 18 posts
Re: The Definition of Done
#2If you wait til the deadline then you create synergies and alignment with management as to whether it’s done.
Re: The Definition of Done
#3The biggest trap is thinking something has to be perfect to be done. Imperfect or untested things can also be done. Call them AS-IS if you need to label it.
Re: The Definition of Done
#4LinkedIn leaking out.
Re: The Definition of Done
#5> So please tell me again, are you done?
Yes. I am done.
Is the story done? Of course. There is nothing else to do on that story because we broke things down into these minuscule story cards.
Is the feature done? Probably not. If you want to hold the “done” classification on the minuscule story until the roll-up of all the feature’s stories are “done“, merged, QA tested, deployed to staging, PM tested, deployed to users, and actually used … well, our “momentum” is gonna look terrible.
At some point I have to get this off my plate and move on. If you want this team’s engineers to babysit their stories until they land in users’ laps, that’s not gonna work. If you want all the stories to sit in operations’ hands until that point, you’re screwing their metrics.
Simply put: it ain’t that simple.
Re: The Definition of Done
#6> Done isn’t when your work is over. Done is when value is created in the world.
I don't get what the context behind this is? What's the intended goal of gatekeeping the word "done"?
For me, I normally come up into "is it done?" as a question when working on tickets in something like jira/trello/etc and there's some "done" column to move things to. Is "value in the world" useful for that context?
Like, "Oh yeah, Craig's finished implementing the API endpoints as per the spec, but we're leaving it in active until the front end team integrate it and it starts delivering real world value".
Re: The Definition of Done
#7The biggest trap is thinking something has to be perfect to be done. Imperfect or untested things can also be done. Call them AS-IS if you need to label it.
> … tested with multiple rounds of feedback and iteration, the PR is merged, your team’s related work is also done, and it is live in production and available to the users.
This article essentially wants perfection as a definition of “done.”
Re: The Definition of Done
#8LinkedIn leaking out.
Or maybe just someone who's done with scrum.
Re: The Definition of Done
#9I had an instructor, at a software project management course I attended, who kept saying "We need to know what 'done' looks like."
That's something that I've adopted as a personal mantra.
It doesn't just mean have all the proper boxes been ticked. It also means we're done adding stuff. Time to take out the 600-grit sandpaper, and start finish work.
Re: The Definition of Done
#10> Done isn’t when your work is over. Done is when value is created in the world. I don't get what the context behind this is? What's the intended goal of gatekeeping the word "done"? For me, I normally come up into "is it done?" as a question when working on tickets in something like jira/trello/etc and there's some "done" column to move things to. Is "value in the world" useful for that context? Like, "Oh yeah, Crai…
Yes, it's a bit tongue in cheek and exaggerated to highlight a common shortcoming in typical engineering parlance.
My aim was to encourage: - More precise language in engineering discussions - Greater accountability - Avoiding procrastination - Keeping your eye on the ball and not just on your PR getting merged