Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

67% Positive

Analyzed from 184 words in the discussion.

Trending Topics

#done#story#until#stories#tested#users#things#minuscule#feature#merged

Discussion (4 Comments)Read Original on HackerNews

jagged-chisel•about 1 hour ago
> 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.

aetherspawn•about 2 hours ago
The 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.
jagged-chisel•about 1 hour ago
> … 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.”

jmiskovic•about 2 hours ago
LinkedIn leaking out.
AdityaAnand1•about 1 hour ago
Or maybe just someone who's done with scrum.
_3u10•about 2 hours ago
If you wait til the deadline then you create synergies and alignment with management as to whether it’s done.