Showing posts with label agile games. Show all posts
Showing posts with label agile games. Show all posts

May 7, 2012

We Bring the Post-its – You Do the Learning

"But one is forced to translate thought into action and action into object… …I am not a teacher who tells his students only to think. I say: act; do something: I ask for result. It may take different forms. It can have the form of sound, or someone can do a book, make a drawing or a sculpture. I don’t care…" Joseph Beuys, 1969
A startup begins with an entrepreneur, having an idea and a question: “How to initiate a change in the world, that a growing business evolves around the initial vision?”. There is no single method or best practices which can guarantee success of such a difficult venture, yet there are several thinking tools which may be helpful when bringing a startup to live. Among others I believe these three are particularly useful for a startup venture: 
  • Design Thinking to understand the user's needs and explore potential solutions
  • Scrum to develop shippable chunks of product in a disciplined and collaborative way and
  • Lean Startup to systematically innovate and bootstrap the ecosystem of an enterprise.
Reading books and blogs to understand these frameworks is essential, though getting the concepts right is comparatively easy in contrast to applying them solving real world problems, which can only be learned by practicing. It takes a few minutes to explain the ingredients of Scrum, doing it just fairly well requires weeks, if not months of continuous practice and learning from failures. Although games and simulations can't substitute fully first hand experience they are a great alternative to expensive trial and error learning on the job.

Just a few days before the Startup Camp 2012 I met with Ahmet Emre Acar and Stefan Wolpers to think about how we may create such a practical learning experience. Our idea to teach Design Thinking, Scrum and Lean Startup was pretty simple: we create the space, define the rules of a game, bring the post-its and cards while the audience will do the learning. In detail the question of “how might we create a first hand learning experience of Design Thinking, Scrum and Lean Startup, where people can use the frameworks and tools in a failure safe environment of a game but still have the chance to generate insights from realistic situations within a few hours of being together on a workshop?” appeared to be quite challenging.  After an afternoon prototyping we became confident that a role- or card game could probably work and started to design the workshop. We decided to split the sessions into first Design Thinking and second Scrum and Lean Startup and experiment with different formats independently but link them via a joint registration/preparation and a shared vision as well as persona.


Plan of the Game Part II
By designing the event we wanted to make use of the frameworks themselves. The workshop should help entrepreneurs to become more successful and we used our network for a story share-and-capture session to identify common success and failure modes. From that we synthesized first a point of view, consisting of the persona Kai, the CEO who wants a vision become reality. Given that the game’s principle is to gather and share insights by applying elements of the frameworks while moving towards the vision of "a new platform to bring people, ideas & capital together to further innovation and create new startups.“. So the teams would be confronted with questions like finding the right hypothesis to validate, building the minimal viable product for testing the hypothesis, growing an agile organization and last but not least organizing themselves while getting started with a minimum of input from outside.

We were so curious how the frameworks, which are rooted in comparable mindsets, would complement one another when used by groups working practically on the challenge. Our hope was that learning from each other and direct experience by just doing would be much more fun than listening to us talking and presenting slides. Since the time we had to prepare the event was short, we were a little nervous, if our first prototype would provide just enough structure for a collaborative game to evolve was really enough.

Fortunately the workshop attracted an experienced and diverse crowd, were about half of the people had applied some days before for a specific role on the game and thus became already familiar with some concepts doing a warm-up exercise I had send around. During the first part of the workshop the teams played a Design Thinking card game to explore user needs, formulate a point of view including a persona as input for the second part of the session. Then after a short briefing of the game structure and mission: “While building the minimal viable product guided by this vision and growing a lean and agile organization the mission of the game is to generate the maximum of insights for the minimum of bucks” the three groups headed off into their first Sprint in the second session. Each startup-team played on their board on the wall consisting of a Product Backlog, Task Board, Org Chart and Insights. For building the minimal viable product we brought large print-outs of the paper prototyping helper kit. For building the organization we used the free Meddlers game by Jurgen Appelo with the additional roles of CEO and User. Everyone could choose a role before the start, switch and extend the role but teams could also hire more members, e.g. Users, just from the attendees of the conference. To trigger hiring, growing the organization and to add randomly complexity, teams had to throw a dice to add skill constraints to each user story during planning. Only stories that fit the team's skill set were allowed to move into the sprints. Each role had a cost assigned but the budget was unlimited and had to be tracked by the CEO. A tough 20 minute sprint structure kept the whole group moving. The main places to gather insights in the form of neon-orange Post-its were testing with people who had the  role ‘User’ whenever possible and Retrospectives during the Sprints. 

One of our main goals was to convey the experience when self organized teams evolve from individuals working together and how timeboxing helps to establish a cadence for groups moving forward under high uncertainty, which actually worked really well on this event. It had helped surely that we involved participants before the workshop by asking them to work on a warm-up challenge. Nevertheless I believe the atmosphere of the conference and kind of people who joined our workshop contributed a lot to the success of the experiment. The teams generated some great insights and thus proved our assumption that most learning will just happen, when people reflect what they experience together and share their knowledge. 

From feedback we have learned that the two sessions need to be more integrated, especially the teams should be kept stable to make the most out of interleaving Design Thinking, Scrum and Lean Startup. The Sprints were too short and we should plan more time for debriefing. We also should plan time for a dry run at the start. We need a better map that explains the game. We need to find a way how to make the diverse roles more realistic and encourage growing an agile organization which actually didn’t work so well. We need to add more challenges from Lean Startup, even though at least one team managed to collect insights from showing product to users within the short time they had. The others actually experienced by failing to do so a common pattern of optimizing product development but failing to spin the whole feedback loop. And it was much fun to see the CEOs pitching their vision to people outside the workshop for ‘hiring’ more users for their team and struggling to keep in touch with their product development. 

The Startup Camp 2012 was a great space to have a shot at the methodologies in a startup like context and to gather at least some valuable practical insights on how it feels to use these tools and why they may be useful. What struck me most was how quick the groups developed an individual style working together for such a short time. The bottom line is that trusting the audience and having a real minimum of structure felt right for this event. For us it was the ideal environment to test our first prototype of the learning game, which we will continue to develop further using the thinking tools themselves. Thanx for everyone, who was taking part in this experiment!

January 8, 2012

Empower the Product Owner

"Let's empower the product owner role fully!  If the product owner is the one ultimately responsible for the results of the product in the marketplace, then they are the "source and decision-maker" for things like budget, scope, approach, market/product timing.  These were things PMs respresented before but PMs were always just "middle men."  With agile, we put that work where it naturally occurs  –  with the PO.  So, when we're thinking of the "PM stuff" that Scrum does not prescribe, think of the role of PO  (plus, the role of the trash bin, because that's also where some "PM stuff" goes)."  Lyssa Adkins, Post in Lyra Mentor Group 2011
Planning an agile team structure is fun - redistributing the power as a result of introducing Scrum within an organisation is a delicate topic. Getting real with implementing the roles is where the hard work starts including the discussion about empowerment. How far can a product owner and thus a Scrum team go, where is the limit of their empowerment? How much do the managers trust their freshly born product owners and what responsibilities will they delegate to them and to which level? The product owner role links the agile organization with the rest of the company (world) which may be less or not agile at all. Thus the answers to these questions highly depend on the context's level of agility and may not be black and white but grey  –  and may evolve over time. 

Jurgen Appelo provides a simple yet powerful game called Delegation Poker to shed light on this grey area and foster an open discussion about the delicate issue of empowerment. The result of using this tool is an authority board which defines the level of freedom for Scrum teams and visualizes the walls within self organization may happen. Here is what I have learned using the tool with managers and product owners within an agile transformation. I plan two or even three iterations – timeboxed to 60 –120 minutes – with different focus depending on the size of the group and level of agreement about the management style within the group. One first dry run helps to get a clear picture of how the group wants to work together, an understanding of the work to be delegated and of the meaning of the delegation levels. It's also fun to use the winning element in this round so everyone tries to understand what delegation level may be best suited for the whole group. Another question that should be raised during the first round is how he delegation level will be implemented thus questions like 'uups agreement sounds so nice – we all want to be very polite right? – but isn't that a hell of work if we have to discuss about every user story in detail?'. 

The second round focuses on getting real with the responsibilities and their delegation level thus requires that everyone in the group understands the work of the product owner. A simple diagram mapping the flow from an idea to product increment helps to identify the most interesting spots for discussing the delegation level. 

It's essential to make clear how to deal with multiple hierarchy levels, e.g. CTO, product owner and direct line manager of the product owners. A simple diagram will do the job to clarify which hierarchy level is represented at the poker table. The full chain of power delegation being present in the game is necessary for coming up with binding results. Surprising differences between middle and higher management may surface during the game and result in insightful discussions about leadership style. Nevertheless the resulting authority board is most useful when the product owners (or any other group it is designed for) can take it and look up their level of freedom thus the discussion should be focused on the delegatees and not so much on the different viewpoints of the managers who delegate. 


The expected timeframe the authority board is supposed to be valid or will be revisited again should be made clear in advance: is the group discussing about the status quo or crafting a vision for the future or just the next step which includes a small challenge. I prefer not to use the winning mode oft he game when creating the final authority board and to have rather a discussion about deviations like in planning poker instead of truncating the highest delegation levels with the minority rule.

Delegation poker is fun to play, yields a common understanding of the responsibilities and makes the new level of freedom transparent for the Scrum teams when turning the organisation upside down during an agile transition. 

With the authority board in place the group has a starting point for implementing and re-adjusting empowerment when needed. And last but not least betting in a group together on the delicate issue of empowerment helps building the interlocking roles of product owner and agile manager.

References