An exercise for exploring activities across interfaces and timeline, responsibilities, with an example focusing on Product Owner and Team. This can be used as part of setting up Team Rules for an Agile Team or a Kanban System Design. see http://yuvalyeret.com/2012/01/31/explore-product-owner-team-responsibilities-exercise/ as well
2. Objective – Explore
Interfaces between two
groups
For example – Product Owner and
Team
@yuvalyeret
3. First Step – Post Up
Activities regardless of
who/when
Example – all activities related
to the lifecycle of a Feature in
an Agile Team
@yuvalyeret
4. Shortcut? Come with a
prepared list
Why Not? Advantage of letting
participants come up with the list
is they digest the material better…
and you start from their
processes…
@yuvalyeret
5. Second Step – When?
Where does each activity lie in the lifecycle? Use
horizontal team estimation game - this means
coming up with a continuum of activities where
starting point is to the left side, ending point is to
the right side (to be compatible with a typical
Kanban Story Board)
@yuvalyeret
6. Third Step – Who?
Which activity is associated with who?
Use vertical team estimation game to drive a consensus
among the team.
The meaning of vertical is that you don’t touch the left-right
placement, just the top-bottom.
@yuvalyeret
7. Debrief
Have a discussion about what this
means, what are the surprises,
does this make sense, what you
would like to experiment with.
@yuvalyeret
8. Consider using this to
“Make your Process Policies Explicit”
2 3 5 2
3
Definition of Done: Definition of Done: Definition of Done: Definition of Done: Definition of Done:
• Goal is clear • code clean and • All tests passed • User signed off •system running
• First task checked in truck • All tests test env on prod env for 1
defined • Integrated & documented • user guide day error free
regression tested upated
@yuvalyeret