Skip to main content

Distributed Product Management with Innovation Games(TM)

My friends at Innovation Games have given me access to a set of really incredible online games that you can use for distributed "Iteration 0" or "Inception" activities, depending on what you call them. Try this one out, and let me know what you think! Cheers!

Bang for the Buck Prioritization:
Timing: 1 hour

Ingredients:
  • A list of backlog items (epics / stories) to prioritize.
Players (5..8 recommended):
  • Product Manager / Product Owner
  • Development Team
Directions:

Bang For the Buck

The goal of this game is to collaboratively rank a backlog based on estimated value and estimated cost. The y-axis is the value of an epic or story and the x-axis is the cost. Each axis is organized as a Fibonacci number. We typically use this game for release planning.

Clicking on this image, will start an “instant play” game at www.innovationgames.com. You'll see this image as the "game board" and an icon of a light bulb in the top left corner of this window. The light bulb represents the backlog items you want to prioritize. To add a backlog item onto the game board, simply drag it from the top left and describe it.

Now the fun begins! While any player can move a light bulb at any time, the game works best when the product manager focuses on getting the light bulbs in the right place vertically, while the development team puts the items in the right place horizontally.

Use the integrated chat facility to negotiate about the items. And any player can edit the items to keep track of the agreements of the team. This means that items will move around during the game as the value of an item increases or decreases or the development team considers various ways of implementing an item.

To get the final results of the game, simply download the Excel spreadsheet. All of the items and their Fibonacci values will be available to you for post-processing, including all of the chats.

Key Points:
  • This is not a learning game. This is a "do work" game. When you're done with this game, you'll be able to get a much better sense about how to prioritize your backlog items by reviewing them in clockwise order.
References
  • Scott Selhorst explains this game with more detail here.

Popular posts from this blog

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else.

Here's what you should think about:

1.Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that:
a.You need your user experience people (if applicable) and your analysts at the beginning of the project, as always, b…

The Agile Business Case

Many agile teams have never seen a business case, ever, and they may even be proud of it.

Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
Dialogue:
WBABA:   ...so in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …