Tag Archives: teambuilding

Help your team improve by visualizing their way working with the fluent@agile game. With the game you can help a team find out where it is on its agile journey and help it find new ways of both fine tuning and make leaps in their daily agile practices.

A teams fluent@agile board.

Me and Christian Vikström made the game together at Spotify during the spring 2014 when we were coaching and helping team to improve their agile skill sets and processes.

At Spotify the teams owns their own way of working. A team is basically only accountable to itself. We therefore needed an coaching tool that could help team take ownership of their self image and improvement strategy.

We also wanted the tool to be opinionated. It should be normative, tell what’s good and not, what kind of practices and behaviour that’s expected and not. But at the same time it should be open to new ideas, new practices and the teams local conditions.

Sometimes it’s hard for a team to know if they get tighter and better as a team over time. This is a tool that allows a team to learn just that.

Team barometer (self-evaluation tool) in a nutshell

The barometer is executed as a survey in a workshop. The survey consists of 16 team characteristics, packaged as a deck of cards. Team members vote green, yellow or red for each card in the meeting (or before the meeting as an anonymous survey). Once all cards have been run through, the team reflects and discusses the results. You can, if you want to, run through the exercise in thirty minutes, but I recommend to set aside an hour.

Christoper Avery, a leading authority on applying personal and shared responsibility for agility and performance, returns to Crisp in Stockholm April 29-30, 2013 to teach his public workshop Creating Results-Based Teams. Space is limited. Register now.

This classic blog post was originally posted on Christopher Avery’s popular Leadership Gift blog on February 9, 2011 — you can find it here.

Why is it so hard to build a well-functioning team?

Often it is because we’re looking in the wrong place for answers.

The most important game may be the one you aren’t even seeing.

I’ll share a critical secret for success. The primary problem lies in what you are (or are not) paying attention to. When it comes to working with smart people in shared-responsibility situations, all too often I catch myself getting caught up in the wrong game — a pointless game. I bet you do, too.

When I start paying attention to the truly important game, my ability skyrockets. And yes, you can solve this problem for yourself as well.

Christoper Avery, a leading authority on applying personal and shared responsibility for agility and performance returns to Crisp in Stockholm April 29-30, 2013 to teach his public workshop Creating Results-Based Teams. Space is limited. Register now.

This classic blog post was originally posted on Christopher Avery’s popular blog on January 20, 2011 — you can find it here.

There is a big difference between being an accountable leader and being a responsible leader. I have been working with business leaders for the last 20+ years as a consultant and speaker, and I am committed to showing real leaders the powerful difference.

The following may sound a bit harsh or pedantic at first, but stay with it and you will be rewarded with important distinctions:

An accountable leader focuses on being able to account for his or her actions and results. As a communication scholar years ago I researched “account-giving.” That is simply the narratives (i.e., stories) we make up to explain what is going on — we give accounts.

The concept of retrospectives is well established in the agile community as the way to incrementally improve your processes and the way the team members collaborate during their work. The idea is that by regularly looking back at the past period you may find improvement that will increase the productivity and delivered value.

This concept can also be used in other contexts, for example during a project kick-off at the start of a new project and team. To get the team on track and up to speed quickly it is important that the forming process starts out nicely and that the team learns how to collaborate and get focus on their work. Iterative processes with short iteration lengths helps out here in that the team needs to get focused in order to have a successful delivery after the first iteration. But you can also help out by establishing a common goal and vision for the team immediately at the start of the project. This common goal could help the team establish better collaboration and communication patterns as well as good process and engineering practices from start that will kick-start the project. And to establish that goal you could run a retrospective from the future, a future-spective.