10
@yuvalyeret Yuval Yeret Kanban Lead - AgileSparks @yuvalye ret Interfaces Exploration Exercise

Exploring interfaces exercise

Embed Size (px)

DESCRIPTION

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

Citation preview

Page 1: Exploring interfaces exercise

@yuvalyeret

Yuval Yeret Kanban Lead - AgileSparks

@yuvalyeret

Interfaces Exploration

Exercise

Page 2: Exploring interfaces exercise

@yuvalyeret

Objective – Explore Interfaces between two groups

For example – Product Owner and Team

Page 3: Exploring interfaces exercise

@yuvalyeret

First Step – Post Up Activities regardless of who/when

Example – all activities related to the lifecycle of a Feature in an Agile Team

Page 4: Exploring interfaces exercise

@yuvalyeret

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…

Page 5: Exploring interfaces exercise

@yuvalyeret

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)

Page 6: Exploring interfaces exercise

@yuvalyeret

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.

Page 7: Exploring interfaces exercise

@yuvalyeret

Debrief

Have a discussion about what this means, what are the surprises,

does this make sense, what you would like to experiment with.

Page 8: Exploring interfaces exercise

@yuvalyeret

Consider using this to “Make your Process Policies Explicit”

2 3 5 2 3

Definition of Done:• Goal is clear • First task

defined

Definition of Done:• code clean and

checked in truck

• Integrated & regression tested

Definition of Done:• All tests

passed• All tests

documented

Definition of Done:• User signed off

test env• user guide

upated

Definition of Done:• system running

on prod env for 1 day error free

Page 9: Exploring interfaces exercise

@yuvalyeret

Applications?

PM-R&D, DEV-TEST, DEV-OPS, MANAGER-TEAM, Outside of Product

Development…