Positive Incline Mike Burrows (@asplake) moving on up, positively

November 28, 2014

Featureban updates

Filed under: Kanban,Uncategorized — Tags: , , , — Mike @ 3:43 pm

For the uninitiated, Featureban is a simple and fun kanban simulation game.

Minor tweaks to wording on the facilitation deck (slideshare, pdf; drop me an email if you’d like the source pptx file):

Featureban from Mike Burrows

There is now a metrics spreadsheet (xls):

Screen Shot 2014-11-28 at 13.22.28

If you or players change the rules in the interests of flow that’s fine, but bear in mind that the flow efficiency calculation assumes that work items require a touch time of two days. Today’s team cheated for a while and ended up with a calculated flow efficiency of 111%!

Fun (almost) guaranteed!

2014-11-28 09.57.57

6 Comments

  1. hi Mike,
    I love this.?This is quite useful as I’m mostly working on portfolio features…

    Could you please send me the deck on fearureban?

    Thank you!!

    Comment by Latha Swamy — November 28, 2014 @ 4:44 pm

  2. Sent. Anyone else interested can email me at mike@djaa.com

    Comment by Mike — November 28, 2014 @ 5:23 pm

  3. Thanks Mike. Really love the spreadsheet. TMO, Featureban is easy and very effective. It also benefits from the ’incremental disclosure’ in using three rounds, adding a slice more new insights each round. Adding the metrics is a cherry on the cake.

    Comment by Martien van Steenbergen — November 29, 2014 @ 1:39 pm

  4. Hi Mike,
    Might try this out in a training next week. What sort of guideline would you give as a good number of features, and how long would each round be to give good results? I assume round length is partly driven by how quickly teams get through there backlog.
    Karl

    Comment by Karl Scotland — December 5, 2014 @ 12:03 pm

  5. Hi Karl,
    You won’t regret it 😉 I usually start things off with a couple of features per person; teams can hold a replenishment event when needed afterwards. Later in the game (eg by the metrics section) we might re-use completed tickets to save time. It’ll take 10-15 minutes before every team has delivered their first couple of items, and there’s a debrief afterwards, so say around 20 minutes for that round. Similarly for subsequent rounds. The last time I ran it, we ran the metrics round multiple times, testing the impact of different rules (“policies”). Overall then, you can fit it in an hour but you can easily fill two. It’s flexible like that!

    Comment by Mike — December 5, 2014 @ 2:29 pm

  6. […] Featureban updates […]

    Pingback by Traduction du jeu Featureban de Mike Burrows | — February 2, 2015 @ 11:13 am

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Powered by WordPress