Work Hacks beim Flaneur

[English summary: Bastian Wilkat interviewed me about Work Hacks in his podcast “Der Flaneur”.]Der Flaneur

Falls Du thematisch nicht so festgelegt bist, gibt es einen ziemlich interessanten Denkanstöße-Podcast: “Der Flaneur” von Bastian Wilkat.

Die Themen reichen von “Robo Advisors und Geldanlage” über “Positive Psychologie” zu “Denkwerkzeuge”. Und seit Anfang Dezember auch “Work Hacks” mit Yours truly. Viel Spaß beim Anhören 🙂

How teams form and break up when there are no managers

Self-Selecting Teams” and “Dynamic Reteaming” are a big topic in my timeline thanks to the books by Sandy Mamoli & David Mole and the upcoming book by Heidi Helfand respectively.

This made me relize that I’ve written about the composition of our teams over the course of the years but not about how people join and leave teams. Let’s take a look at this now.

Crude self-selection into initial teams

We made the switch to Scrum and cross-functional teams in 2010. Tim (the CEO) asked two designers and me into a meeting room. There was a board with a table in it. Three empty columns headed Team 1 | Team 2 | Team 3. The teams would start with Scrum one after the other with two weeks (= one sprint) in between and we each should pick a column.

The three of us were the first ones who got to choose a column, so I just picked the first one. I was looking forward to getting started with this whole Scrum thing. I still think that many of the people looking forward to Scrum self-selected into that first team. It was certainly fun to be part of that team. Continue reading

Agile is about usability. So is Clean Code.

Maybe it’s because usability was such a strong focus of mine for such a long time but I feel like most good ideas boil down to usability. It’s kind of my “grand unifying theory of good practices”. To me, Agile Software Development is about providing good usability to the customer (not necessarily the user). Clean Code is about good usability for other developers. They’re both about going the extra mile to make someone else’s life easier.

Agile Software Development is about providing good usability to the customer

Not convinced? Well, I hope it’s easy to see how Clean Code will make code more usable for its future maintainers. That’s why I’ll concentrate on making the case that agile software development is for product development what usability is for product. Continue reading

How to get a very dirty whiteboard sparkly clean

When you let the writing on whiteboards stay on for long enough – say, a couple of month –  dry-erase markers stop being “dry-erase” and start being “leave unwipeable shadowy traces behind”. You’re left with an unsightly board, no matter how often you wipe. Water doesn’t help, at least not against dried up German Edding markers.

Even worse are traces of the slim tape that some teams use to create tables on their boards. Its remains are stickier than candy floss and way uglier.

wepos-kunststoffreiniger Fear not, my colleague Frieda has the miracle cure: Clean your whiteboard with “Wepos Kunstoffreiniger” (= Wepos plastics cleaner) and it will become perfectly clean and smoother than a baby’s butt. Way smoother, actually.

That’s also the catch: After wiping your board with the cleaner you have to wipe it with water. Otherwise no sticky note will stick to the board. Try it, it’s quite fascinating. The sticky notes fall right off of the infinitely smooth surface.

If you don’t have tape traces you can also get rid of the old marker markings with a wet microfibre cloth. Again, kudos to Frieda for finding this trick.

The very last resort, for people without any equipment, is ye olde overwriting trick: Retrace the old writing with a whiteboard marker. The solvents in the marker’s color will also work on the old markings and make them wipeable again. It’s works, it’s just tedious.

Do you have any neat tricks for cleaning dried-in markers?

What can you do if retrospectives repeatedly go sideways?

Not all retrospectives go well. When you support a team as a Scrum master, there are all kinds of strange behaviours or team dynamics that can make retrospectives go sideways, time after time. A facilitator can’t always prevent that. At least I can’t. Not always. Got lots better, though. Over the years I’ve picked up several different angles to get retros back on track (what I think is the “track” anyway). Enjoy:

Choose specific activities

When I started out as a Scrum master I thought my only option was to carefully choose activities to nudge people into the direction I thought they needed to go. And for some situations that works well.

The team acts the victim. Others need to change, there’s nothing they can do? Try Outside In, Circles & Soup, If I were you, …

There is a specific “weak” area they don’t like to look at? Communication Lines for (surprise!) flow of information, Quartering for Tickets, Company Map for Power Dynacmics, …

Talk to individuals

Then I started to address individual behaviour in spontaneous 1:1s whenever I could snatch the person alone. For instance: “I’ve got the impression that you often address me during the retrospective (/standup/…). The information is not for me, it’s important for the others. I would love for you to try to look at the others more.” Continue reading

Improve your Retrospectives with this 1 weird trick: Liftoffs

When health is concerned, preventing issues altogether is often easier than treating them once they’ve manifested. The same can be said for retrospectives:

In retrospectives we often make up for the fact that we didn't have a liftoff

Either Deborah Hartmann Preuss or Steve Holyer said that in a conversation and it rang true. Very few teams get a proper liftoff and they lose weeks and months of productivity to initial friction. In contrast, a proper liftoff sets up a team for success by laying a solid foundation of agreements and shared understandings. Then the team doesn’t have to spend their retrospectives patching up problems that could have been avoided.

What are liftoffs exactly?

You might know them as kickoffs, jump starts, launches or project starts – a meeting at the beginning of a team coming together and / or starting to work on something. I’m going with the name “liftoff” because of the book by the same name written by Diana Larsen and Ainsley Nies. Continue reading

Story Cubes for Retrospectives

Sometimes we have guests over who want to learn more about our Open Friday and see it in action. Lately we’ve been asking for a session in return so that visitors add to our pool of knowledge. These guest sessions are often interesting and sometimes you strike gold: Cynthia Hohlstein and Kevin Plechinger hosted an inspiring session on and with Story Cubes. Because neither of them blogs, I get to share their idea with you: Story Cubes are sets of 9 dice with images on them. The images cover a wide range of motives, such as a speech bubble, a sheep, a star, a hand or a walking stick figure. The idea is that you roll 3 dice and then tell a story that contains the 3 motives you rolled.

3 Story CubesThis can easily be turned into a fun activity for agile retrospectives if players answer a question instead of just telling a story. Cynthia and Kevin already had a couple of ideas:

  • What was last sprint like?
  • How do customers view our product?
  • What’s the state of agility here in our company?
  • What was your carreer path? How did you get here?

We spend the hour-long session answering questions in groups of three. It was very interesting because the cubes prompt you to talk about aspects you wouldn’t normally have touched on – you tell the truth and still have to incorporate the 3 images. Among others, we used the “Customer View” question and it was quite revealing. Story Cubes help with changing perspective and add a fun element.

Thank you Cynthia and Kevin for introducing us to story cubes!

PS: Interested in retrospectives? Sign up to the Retromat newsletter to get related news and tricks!

 

5 more things I learned at Agile on the Beach 2016

From Kat Matfield’s session “User Research in an irrational world”:
1) If at all possible, look at records of what people actually did in the real-world situation, (screen recordings, chat logs, …) instead of putting them into a research situation (in which they will always pay more attention) or asking them to remember (memory is extremely unreliable).

From Gez Smith’s session “Agile Marketing”:
2) Maybe 1 thing goes viral per year. Rest is planted and pushed with fake accounts

From Darci Dutcher’s session “Running killer workshops without killing yourself”:
3) If you use dot-voting and don’t limit the number of votes you get information about the long tail of interests. Not relevant in short retros but maybe for a longer workshop.

4) A retro is a sub-kind of workshop. I never thought of retrospectives in those terms. Nice realization.

From my own session:
5) Putting your cell phone near a mic is a really bad idea (audio feedback)

I also learned about Jeff Patton’s Cups, the sticky note bonus shape and that I’ll try to remind more speakers to repeat the audiences question before answering it.

All in all, a very nice (knowledge) haul 🙂

 

 

Need an idea for your next agile retrospective? Or 127? Retromat eBook!

Wow, this was a looooong time in the making, but it’s finally here: The Retromat eBook! So, if you’ve ever wanted to front-load your brain with each and every activity in Retromat, check out the Retromat eBook!
Cover Retromat eBook

Find the perfect fitting activity for your team and situation! Never run the same retrospective twice. Unless you have to bring one back due to popular demand 🙂

While I was at it, I updated and included a lot of useful information around retrospectives, such as the basics, a default planPhase 0 & increasing follow-through on action items and the interview series about remote retrospectives. I hope the result is useful to you 🙂

PS: If you’re the source or submitter of one of the activities currently in Retromat you get a free copy! Just email me! Check the green box below for contact details.)

PPS: Interested in retrospectives? Sign up to the Retromat newsletter to get related news and tricks!

Of Baby Elephants and MVPs

As you know, I’m a sucker for a good metaphor be they coconuts or hosting. I’ve got a great new one for you: Baby Elephants! Fantastic, right?

Well, yes, it’s promising. Baby elephants – What’s not to like. But what are they a metaphor for, pray tell?

Cute baby elephant courtesy of Beratung Judith Andresen

Cute baby elephant courtesy of Beratung Judith Andresen

Judith Andresen introduced baby elephants as a metaphor for MVPs at Agile on the Beach 2016. One immediate benefit is that it short circuits endless, mostly fruitless discussions along the lines of “What exactly is an Minimum Viable Product?” “We need  an Minimum Marketable Feature instead!” “No a Minimum Loveable Feature is the way to go!” “No, it has to be a …”

Instead of arguing about different concepts, baby elephants give people concrete images to work with:

  • “I think we’re building a teenager elephant here, not a baby anymore.”
  • “We’ve got too many baby elephants in the stable already. Let’s get those out before acquiring a new one.”
  • “What are young mammoth trees (which the elephant is supposed to move) in our context?”

Judith’s fable includes much more, e.g. the context in which a baby elephant is an excellent MVP. Read the whole fable about nature-oriented forest management with baby elephants here.