• “Fun, Energizing, Informative I liked adjustments during the day to our plan – nice! Facilitators checked in to see where group was at (all day – during games too)” – Alistair McKinnell, Agile Coach
• “Engaging, Fun, Self-discovery High energy personalities in delivery; not sitting all day and mixing the groups up” – Colin Bowern, Technology Coach and Solutions Architect
• “Fun, Engaging, Educational I liked the split from play to how to facilitate; the mixture of games and game lengths; the flexibility to adapt to the needs of the group” – Sarah, Coach
• “Engaging, Fun, Insightful I liked talking about different roles; it was laid back and fun; good energy and inspiring. – Nick Faulkner, Team Lead
• “Fun, Insightful, Amazing We adjusted as we moved through the day and we took longer where there was value” – Alex Aitken, Consultant

Mistake #1 – Too many games

It all started a week before when participants met online to play the Innovation Games® Buy A Feature game to select what games we would play. Gino Marckx and I provided a menu of 20+ games. The prices? We use the number of minutes for a session. It was a public game, so feel free to check out our results or run your own games.

The first mistake was that we had too high a budget when playing Buy A Feature. I had worked out the approximate number of minutes and decided to budget 30% of the time so we would be a little under the total time. Problem was I forgot to change the default from 40% so we ended up with too many minutes.

How would you recover?

Gino and I used dot voting to prioritize the games selected so that we would play the most important ones first. Here is what we came up with. (Note: no votes for team games since we did this right at the start before the voting). The games are listed from top to bottom based on “ROI” (dots/time).

Mistake #2 – Budgeted times off by 40%

As the day progressed, it became clear that the time budgets we had allocated were too low. Way too low.

How do we know this? Well, having just finished a Kanban workshop, I created a control chart to track actual time in comparison to budget time. See photo below.

Root causes?

1. When we were having valuable debriefs we kept going, rather than keep to our timebox.
2. After each game was finished, we had a game facilitation discussion to talk about when you might play the game, setup needed, tips and tricks, etc. People found this very valuable.
3. The games are tiring and people needed more breaks than planned.
4. The two big games – Business Value Game (BVG) and Yellow Brick Road really benefit from having 2 hours instead of 1.5 hours. This is consistent with my earlier playings of BVG.
5. Some of the games we were less familiar with.

The Games We Played

Here is a quick review of the games we played and when to use them. The full list of games is here.

Team Formation and Energizing

Constellations (30 min) is used to share team perspectives around values and beliefs. The information allows team members to help each other through challenge areas and provide hooks to talk about problems. We also played Tribes as a warmup but don’t have a description for this.

MarketPlace (60+ min) is used to inform team members about skills help by one another. This helps on many levels. First, you know where people are coming from. Second, you learn what skills and capabilities they bring to the project. Third, you may notice other things about them that can help the project succeed. Fourth, appreciating skills creates a powerful connection between the team members.

Play these games with all team members when you start working with them.

Product Backlog Management

Business Value Game (90+ min) helps players understand different views of value and think about the challenges of modeling business value. In particular it gets players to think about how to keep customers happy and balance technical improvements with feature delivery. It also hammers home the importance of reviewing acceptance criteria. Play this game with Product Managers/Owners and everyone involved in backlog prioritization.

Emergent Design

Marshmallow Challenge (45 min) helps players understand the benefits of incremental and evolutionary design. Teams that balance planning with experiments and learning about the problem domain do a lot better than teams that do a lot of upfront planning and no learning. Play this game to shift away from Big Design Up Front. This is suitable for all team members and especially important for Product Managers/Owners and Architects/Designers.

Developing Coaching Skills

Yellow Brick Road: Fresh Insights through peer coaching (90+ min) allows people to develop their coaching and observation skills so that they can help one another. A side effect of the game is that people can solve real problems. This is a good game to play with ScrumMasters, internal coaches and managers.

Value of working in small batches

Penny Game (30 min) is a fast and effective demonstration of how customer responsiveness can be improved through delivery of work in small batch sizes. It also highlights the importance of identifying organizational impediments to productivity and selecting high priority stories first to maximize ROI. I like to play the game when introducing teams to Agile and Lean/Kanban – especially to motivate user stories vs. big requirements.

Concurrent Projects delay delivery

Name Game (10 min) shows how delivering to multiple client projects at a time will give the perception of responsiveness but will lengthen delivery times. Great game to play with managers, project managers and Product Managers/Owners.

Multi-tasking reduces effectiveness

Multi-tasking (10 min) is a quick pen and paper exercise that illustrates how multi-tasking reduces the effectiveness for an individual. Play it with managers and team members that think working on multiple projects or multiple tasks is a good idea.

Some photos from our day of play

Business Value Game

Marshmallow Challenge and Marketplace

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

It is interesting to watch oneself after some time has passed. I would definitely keep the energy and the passion. For sure I would speak S L O W E R (Man, I was like a gerbil on speed). I would also drop most of the text as you can see in my more recent zen-like presentations. A lot of the message is very good – I reminded myself of a few things. Enjoy.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

The purpose of this post is to share how the event was run for attendees and other Open Space enthusiasts.

Setting up the Space

As a not-for-profit, the City of Toronto provided us with a great space for free.  You can see us setting up below.

Empty Board

Rather than follow the suggested approach of an unstructured bulletin board, we elected to create a grid. Why? We find techies get really frustrated and will sort sessions by time anyway. Note that some of the session slots are marked reserved and only get opened up once there are enough sessions to run all day.

Lawrence Welcomes Everyone

Long-time host of XPToronto/Agile meetings opened the space.

Michael and Gino Pair Facilitate

We pair program, we pair test, we pair coach. We really like working together since it provides variety for listeners and it’s easier to remember everything between the two of us. As you can see, we are walking in a circle to set the tone and explain how open space works.

The Initial Rush

Once the call to action is given, there is a rush of motion and energy as people write session proposals.

The Board at the end of the day

Here’s what the board looked like at the end of the day. You can click on it to see a hi-res version and read the session titles.

Many thanks to all the volunteers: Edwin, Farooq, Tom, Bob, Micrea and others who arrived early and helped out. (If I forgot you, remind me and I’ll add your name)

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Agile Executive Briefing – Situational Assessment and 50,000ft view of Agile

The first part of this presentation is a situational assessment of typical challenges in IT project delivery using the SCRAP (Situation, Complication, Resolution, Action, Proof) model. This is essentially a business case for Agile. So if you are looking for ways to get buy-in for Agile, then this is a good place to start.

The second part of the presentation shows you what Agile is from 50,000 ft. From this high up, we’ll be covering the essential elements from a business and management perspective. We’ll cover what Agile is, what it does, how it works and what it achieves.

Each of the parts can be used independently so you may use the first part to get buy-in or the second part as a high-level introduction.

Slides on Slideshare

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

On a personal note, I met lot’s of new people and had a number of interesting discussions and exchange of ideas. We are definitely going to do something for next year and make this an annual event to grow Agile in the Toronto area.

All the presentations will be appearing at DZone over the next several months.  To cover this gap, we are going to publish whatever slides we can directly on our website.  Mine are here: A Gentle Introduction to Agile and Agile Executive Briefing.

Thanks to everyone who helped make this a big success.

Partner Workshops

On Monday and Wednesday, I had the privilege of training together with Yves Hanoulle to run two Agile workshops: KickStart (XP) and Games Day.  It was a great experience for me and for the participants.  Pairing works.  Even for training and coaching.  Who knew?  Yves, i guess So, now I am actively looking to pair with other trainers/coaches.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Phew! It’s a lot of work.

Anyway, we are making progress and have a web site up: http://www.torontoagilecommunity.org/

We are looking for volunteers, presenters and sponsors.  See the website for details.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.