Quote Posted on
Reblogged with permission from Preetam De, the original author of this content, as a contributor to blogagility.com. Originally published on The Dark Horse on September 2, 2016.
While reading Invest on an Epic Story and get the job Done, there was a discussion about how the done checklist can be formulated with mandatory and optional sub-tasks. This article can be considered as the prequel which forms the basis of that implementation. A question we always come across while explaining how to define Done for a Story is –
What is “Done” or “Done Done”? How much is enough?
I am teaching Leading SAFe with my co-instructor Jose (Joe) LaTorre USMC (Ret.) this Friday! The kit is prepared! We have some prep work to do still but I am SUPER EXCITED about teaching the course! Thanks to the Scaled Agile, Inc. folks for the support and to my gracious and eager to learn clients at ESC!
Going to have to figure out how to virtualize this concept.
I have been working with the agile teams for a long time. Agile has gifted a lot of meetings viz. planning, grooming, retrospective, etc. Retrospectives are one of the most powerful and often the most ignored meetings as they end up as boring and ineffective. Hence, a lot of engagement and innovation is required to reinvent the retrospectives. I came across Rory’s story cubes and thought to ‘experiment’ the same in my retros.
I purchased a few boxes of cubes and mixed the same to have diverse stories: 9 cubes in a box as per the recommendation.
When I introduced the cubes to my first team say Team X: they migrated to the exploring mode — started seeing the different faces of the cubes. Then, they rolled the same. The first time it was too much silence.Then, we played the second iteration. To my surprise: amazing stories…
View original post 579 more words