Hi there, it’s been a while since you last heard from me, I know. I have to admit it, I’ve been feeling lost for some time now. Since our company adopted Agile, I haven’t felt at home. People around me started thinking, took initiatives, started to talk about building a “culture”. I felt lost as

Two years ago I created a simple role-play card game called Game of Structure. After trying it out a couple of times it has been sitting idle, and what fun is that? So now I am making it available with this post.

=> Game of Structure – Beta version

The game is Creative Commons Attribution 4.0, so you may use it freely as long as you honor it’s origin. If there is enough interest I may go ahead and create a physical card deck based on this game.

What type of game is this?

The idea is to offer an experience of how a single hierarchy of fixed power roles can generate some common patterns of stuck attention, conversation and challenge that we frequently see in organizations. Often we spend a lot of time managing those conversations without seeing that some of them may emerge just from the power structure itself as a design choice. If we can experience that this may be the case we can talk about it and consider redesigning those structures rather than having to fix these challenges directly.

This game helps you see and experience some of the load of this extra complexity. Have fun!

Disclaimer – The game is fun as it is but I invite you to be a little careful when drawing conclusions from it – there may be some fallacies and traps! If you want to dive down this perhaps sensitive and deeper rabbit hole, read on through the second part of this blog post.Continue reading

I’m blown away of the popularity of the Jimmy Cards I created a few years ago. The massive amount of feedback and appreciative comments inspired me to compile two additional decks. The goal of the original red is to help new teams gel. The new black deck is aimed to challenge mature teams that have worked together for some time. The new blue deck will help the leadership team collaborate more effectively. And now, finally, the labour is done and the physical cards have actually been printed and are available to buy!

Continue reading

Meaningful inclusive retrospectives are possible with distributed teams. Let’s talk about the basics you need to have in place, how you can facilitate a distributed retrospective, and what to look out for. This guide is based on the retrospective format that we used at LRF Media. The retrospective participants included 5 team members at the office in Stockholm, one person working from home, and 2 people working at the Kraków office.

Continue reading

So how do you go about implementing a zero bug policy when you’ve got a long list of real bugs and users and stakeholders who want things fixed? I’ve been getting this question a lot after posting my blog entry Stop Managing Bugs, Start Focusing on Quality and creating the app and cards to help with the

“Fix It Now or Delete It” is a simple method that gives you two options for dealing with a bug: Fix It Now, or Delete It! I wrote a blog entry about this method a few months ago, and now there are lots of resources to help you talk to your team about simplifying the

So you have a LARGE backlog and you have decided that you need to estimate it.

Not on board? Still undecided? Go read my previous post on the tradeoffs between estimating and not estimating large backlogs.

Still reading? Ok, let’s get to it!

You can do larger scale estimation in MANY ways. What I will share with you here is just one way I have found to do it effectively, with enough accuracy at a reasonable cost. It requires some pre-conditions, such as having a team with an established way of working and some way of estimating on the team level, so it may not fit your situation. But if it does it is probably worth your time to check out.

Continue reading

Before there was the concept of frontend and backend developers, there were just developers and I was one of them. We did everything from HTML to SQL and it was not hard. Then something happened, JavaScript became popular. After years of server side rendering and thin clients, the pendulum was swinging back to fat clients again. And I was a backend developer.

Believe me, I have tried to get on the train with JavaScript and its hose of new frameworks. I took courses in JavaScript. I wrote applications using Meteor, tried Angular and React. But what I never managed to do, is liking it. There is simply to many ways of shooting yourself in the foot. And all these frameworks that come and go points to something, perhaps we are trying to fix the wrong problem. I suspect it is the foundation itself, JavaScript.

Continue reading

What I’ve strived for in all my jobs and assignments is to combine the best discovery methods with the best delivery methods, of course in the best possible way. I have tried and tested a lot of popular frameworks and ways of working, and the following list of principles is my conclusion. Continue reading

Recruitment processes for agile team coaches differ greatly from one company to another. Jan Grape and Yassal Sundman share their insights on what makes for a good process based on their work recruiting coaches for their clients.Continue reading

You’re coaching a new team! Woohoo! You have so many ideas! You’re going to help make the team’s world a better place! All the things that you’ll do! Then you get there. The music stops, and the frustration sets in. You’re trying to help but team members come late to the daily scrums, they don’t update the information radiators and they’re zoning out during meetings. You’re not sure what to do anymore. What happened? You feel undermined and unappreciated. Aren’t you the expert? Isn’t that why you got this team to begin with? Why won’t they let you help them?

Let’s look at the journey of joining a team and how you can pave the way for a successful coaching experience!Continue reading

How should you structure your Ansible variables in playbooks calling cloud modules? Ansible has extensive support for variables at different levels (there are 21 different levels!).

The inventory group_vars and host_vars offer enough flexibility for many use cases. However, when you are setting up cloud infrastructure, you don’t really have any hosts yet. Maybe you are setting up load balancers, instances, security groups and such things. Perhaps you want to setup the same things in several different environments (like “staging” and “production”). You want to re-use the same playbook, but adapt what it does by using different variable values in different environments.

In this post, I will demonstrate a way to structure Ansible variables in a playbook which pretends to setup a AWS AutoScalingGroup. I will show how you can separate the configuration for different environments by using a inventory directory. As a bonus, I will give you a neat trick to automatically load a extra variable file for each environment. We will use this to load a separate secrets file which is encrypted with git-crypt.

Continue reading

I had the opportunity to make an interview with Dave Snowden as he visited Crisp for his latest Master Class end of November, titled “What´s next for agile”. We explored the topic of What´s next for agile, new updates to the Cynefin model, now called Cynefin liminal. Check out the video below to of my interview with Dave (14 min).

Agile is increasingly becoming commodified and what are the opportunity for smaller Agile companies and anyone believing in the original Agile movement? (0:20).  h “The key now is to produce new high energy efficient, radical, high value, innovations around the core of what Agile has become”

Continue reading

Do you have a long list of bugs? You definitely want to have a zero bug policy, but now you have all sorts of minors, majors, and criticals. You’re not really sure how to get to zero bugs (were you ever there to begin with?). You have spikes where you fix the bugs and your graphs show a steep downward drop, only for them to turn upwards again and reach new heights. Just maintaining the list of bugs is a full time job! To add insult to injury, when a team member finally gets around to looking at a bug, they usually find that it’s outdated, not reproducible or part of some long forgotten removed functionality.

There has to be a better way! How can you shift the focus from managing bugs to ensuring quality? Here’s a system that’s easy to start using, and rewarding when you follow it.Continue reading

One of the most exciting aspects of working as an Agile Coach is applying what we know to other industries. Especially when what we do serves the greater good. We’re both always actively looking for opportunities to work with integration initiatives, and in this case we supported an initiative to improve integration of newcomers. Here’s how we facilitated the 2018 kick off meeting for Järfälla municipality’s Interfaith Council.Continue reading

When you use Ansible to provision hosts, running a task on a set of hosts in parallel is not a problem. You simply use the `serial` keyword in a playbook. See: http://docs.ansible.com/ansible/latest/playbooks_delegation.html#rolling-update-batch-size What about when you want to run a task several times in parallel, either on each host, or on a single host? A

Have you worked with teams that don’t communicate well? Or teams that don’t collaborate? What about teams that deliver late or with poor quality? Or maybe teams that are in constant negative conflict?

How do you tackle these issues? It might feel like you can fix everything by changing some of the people on the team. Before you do that, consider how you’ve set the stage for your team. Will removing and adding some people really solve all your problems? Or will the new members find themselves in the middle of a dysfunctional team, and end up unhappy and not delivering to their full potential?

Here are some of the things you can think about when you work with teams to create an environment where they can succeed.

Continue reading

For the past four years I’ve consulted for King as an agile team coach. It’s been a whirlwind of personal growth, learning about mobile games and meeting awesome people. I wrote about my biggest takeaways in an article on Crisp’s website. I am grateful for all the connections and insights that I’ve gained. I’m also

Yuval is coming to Stockholm to teach a Scaled Agile class (Implementing SAFe) in January. I know Yuval from the Kanban community from a number of years back. We invited him because we know he shares the same pragmatic view on things as we do in Crisp.  We made the interview in order for our audience to got to know him

The role of software development is to produce software to solve a problem. The role of Agile software development is to learn as much about the solution as possible while developing, Agile does that mainly through ruthlessly begging for feedback, both on the product (e.g. sprint reviews, test-driven development and continuous delivery) and on the process (e.g. Scrum/Kanban boards, sprint retrospectives and standup). In between all these feedback sessions, you do ”normal” software development.

The role of user experience design (UX) is to produce a design to solve a problem (through user research and interaction design, of course). So, software development and user experience design go hand in hand, completing each other. Design and build.

The common misconception is that Lean UX also shall produce a design solution to a problem.

This is not the case. The role of Lean UX (and its progenitor Lean Startup) is to learn, but learn as much about the problem as possible. Lean UX does that through ruthlessly validating assumptions about the problem, the customer, their needs, the proposed solutions and the success metrics. Lean UX and Agile go hand in hand as well, learning about the problem and the solution, before, during and after development. In between all these validation sessions, you do ”normal” UX.

Continue reading

Through the years we have at Crisp repeatedly been confronted with the question “How can I become Agile?”. We have checked with coaches outside Crisp and they give us the same picture. People want to become agile and they want it now. It has become obvious to us that there is a need for a quick fix. Hence the Agile Pill.

Continue reading

OK here’s an offer to any conference organizer in the lean/agile/tech/climate space. I get a lot of requests to do conference keynotes, which I’m grateful for, but unfortunately I have to turn down the vast majority. I limit long-distance travel for family reasons, and also for climate reasons (although I confess I’m in Thailand right now as I write this…. hard to be 100% consistent…).

Now I’m thinking: Why should something as mundane as physical transport get in the way of participating in a great conference? And, in this world of catastrophic climate change, shouldn’t most business trips be replaced with remote participation?

My hypothesis is that it’s possible to remote-participate effectively in a conference –  to do a keynote or talk, participate in workshops, even hang out with people in the hallway. I’ve tried this a few times using video conference and telepresence robots. In fact, 4 years ago I was sitting on this same beach in Thailand, remote-participating in a Spotify event in Stockholm using a Double (see “What it feels like being an ipad on a stick on wheels“). That was fun and a bit clunky, but it was 4 years ago so I bet the telepresence robots have come a long way since then!

So here’s my offer:Continue reading

Here are the slides from my keynote “Agile – where are we at?” at Agile Tour Bangkok i November. Here’s the abstract:

Everyone is talking about Agile. I stumbled into this 15 years ago and have been living and breathing Agile since then, seeing it grow from a small movement within software, into an industry-wide revolution and then gradually become mainstream. More and more companies around the world, even big traditional companies, are turning themselves inside out trying to be Agile. Now it’s time to take a step back and reflect. What is going on? What is this all about? And where is it headed?

The CO2 emissions from this trip were offset using Trine and GoClimateNeutral.

Sample slides:

Continue reading

Last time I wrote a book (Visualization Examples) I decided to do it publicly online. That was a fantastic experience, which I also wrote a blog post about. It was great fun and I got tons of valuable feedback.

Now I’ve started to write a new book and I’ve decided to have the same approach. It’s currently titled “Toolbox for the workshop facilitator – Facilitaion Tricks and Techniques (How to reach strong workshop outcome)“.

The book is far from finished and it might take me another year to finish it. But I still want to invite you to read it now and to help me make the book even better.

Continue reading

– Having rules for communication is stupid!
– What was your intention with calling the rules stupid?
– Well, I’m sorry, I didn’t mean anything negative towards you, of course. I just don’t find such rules necessary at all. We have been communicating with each other since we were small.
– Okay, I understand what you are saying. But, hear me out…

Continue reading

Just got back from Athens and Devops Greece where I talked about “Using Kanban in the field, and how we got management buy in to do so” Two key takaways are: Shift leadership behaviours, in order to shift your culture. The good news is: You can all exericise them, they are not personality traits. The invisible

In this series of blogs, I am writing of my experience of practical applications of Sociocracy 3.0 (S3) patterns in teams and organizations. In the first blog, I wrote about My journey of finding and applying Sociocracy 3.0 (S3). There are many cool patterns in S3 that I have been using with great success as an Agile organizational coach so far. In this article I will cover the pattern of Consent Decision Making:

In contrast to consensus which focuses on reaching an agreement, consent focuses on intentionally checking for reasons not to do something a certain way. An objection is an argument that reveals why doing (or continuing to do) something, impedes or misses an opportunity to improve flowing value somewhere in the organization. Reaching consensus is often very time consuming and has the risk that one single person can block the whole process when unanimity is sought. Continue reading

The Future of Work is already here, it is just only unevenly distributed.

There is a crisis in the world of work. The pace of change in our environment is faster than the internal change in most organizations. Many organizations are struggling to keep up and are risking becoming obsolete. Gallup’s report on engagement crisis with only 32% of US workforce and 13% of the worldwide workforce engaged. Companies in the S&P 500 Index in 1958 stayed in the index an average of 61 years but has fallen to 18 years in 2012. Why is this?

When it comes to our work-life most of our organizations are still designed based on principles from the industrial age. Separation of thinking, planning, and management from the work. Organizations are designed to be top-down hierarchical and inside out rather than outside-in, customer-centric, and decentralized. There is mechanistic view rather than an organic, natural and Agile view of organizations.

This new complex world will put completely new demands on leadership, organizing and just everyday living. We are living in truly exciting times. How can we create organizations that are fit for the future and more human? How can we re-invent organizations so that we will free up people’s potential for doing good? Many of these organizations are also based on triple bottom line principle: “Profit, People, and Planet”. This is my passion and I am super excited about it right now. Continue reading

Codekvast is a tool for detecting Truly Dead Code in your Java application. Truly Dead Code is code that is in production, but has not been used for a significant time. Codekvast has been lurking in the spare-time realm for too long. Now the project has eventually been granted some full-time development effort, with the initial

Large group retrospectives are long, large, unwieldy facilitations. So much so that they’re typically done only at the end of a project. Holding a 1-2 day retro every few weeks for a large project is neither practical nor responsible, but continually improving the project is also important.  So, how do you hold light-weight retrospectives for large groups, while making sure that you:

• Have a common understanding
• Identify issues and strengths
• Reach a group agreement on action points
• Ensure that the group feels that they received a high return on time invested

This retrospective combines different techniques and technologies to achieve these results.Continue reading