My preference is for teams to not Showcase Stories that do not get DONE.
Stories are rarely nearly DONE
In several years of Scrum I’ve lost track of the amount of times that I have heard a Team say that a Story is nearly DONE or mostly DONE, almost DONE or 99% DONE or will be DONE very quickly after Showcase and then the Team still struggle with same Story for most of the next Iteration or longer.
What I tell teams is that if I hear any word prefixing the word DONE like “nearly” or “almost” that what my coaches ears really hear is the word “NOT” eg the Stories are NOT DONE.
Teams should not take credit for work that is not DONE
One of the main points of Showcase is to congratulate the Team for the hard work they have put in to getting their Stories DONE.
If a Team knows that they can Showcase NOT DONE Stories then they won’t work on the kinds of behaviours that enable them to get the maximum amount of Stories DONE in a given Iteration.
Being honest with stakeholders builds trust
It can be highly embarrassing for the Team if stakeholders see a NOT DONE Story at a Showcase and then a few weeks later they still cannot see the feature on the live site. Explaining why the team claimed something was finished when it wasn’t is a lot more difficult than admitting a Story didn’t get DONE in the first place.
The Teams reputation is not worth risking misleading stakeholders about one Story.
Having NOT DONE Stories is incredibly wasteful
Even if a Story is “99% DONE” it still has to go through the following process to get DONE in some future iteration.
- The PO must prioritise the Story again
- The Team must review and rewrite the story removing the parts that are not required and adding any missing detail and conditions of satisfaction
- If the Story is much larger than originally estimate then it may need to be split
- The Story must be re-estimated
- The Story has to be tasked out on the Team Board
- The Story must be coded
- The Story must be code reviewed
- The Story must be retested from scratch across all test cases on all devices and browsers
- The Story must be signed off
- Throughout the Iteration the Team must update JIRA/Rally, talk about the story at Standup and communicate with each other in a timely and effective manner to ensure it passes through the Team’s Iteration workflow.
In short, any story that does not get DONE, even stories that are “99% DONE” will still require a fair amount of work from several people in the Team in the next iteration. Teams should be aware of this and they should focus on getting the maximum number of Story Points DONE.
Why you might showcase NOT DONE Stories
One of the main points of Showcase is to inform the stakeholders on the progress of the work so that they can make good decisions about future work. Sometimes when a Story isn’t done there might be some value in showing this to the stakeholder, but if you do, make sure you are clear with them that they Story in question did not get DONE according to the teams Definition of DONE and that it will be replanned into a future Sprint if it is still a priority. Another reason to Showcase NOT DONE Stories would be to share any blockers the team have with stakeholders who may be able to help clear those blockers.