Tag Archives: kanban

Let the User Story Flow

Posted on by

One of my biggest surprises when I first met the squads I where going to work with at Spotify was that none of them were using User Stories. At first I observed to see their alternative. Unfortunately there was none. Instead most of the work got done as big chunks of work (what I would tend to call Epics) that was sliced into a todo-list of tasks (named that way by the developers) and also divided according different platforms.

Squad focus on technical tasks

A typical board contained one or more business cases and lanes for each developer/platform with tasks that were executed upon. These big “busses” where on the board blocking other works for weeks, which of course meant there needed to exist one or more emergency lanes for all expedite work (in the long run, most work).

This is a setup that does not foster collaboration, focus on value and art-of-the-possible. From an agile fluence point of view I would say it is a way of working that does not even reach fluence level 1 (Christian and I will describe agile fluence in more depth in a follow up blog post). From my experience focusing on User Stories is a great way of fostering the above values, and reach fluence level 1.

read more »

Why I prefer ToDo over Trello for agile teams

Posted on by

The Gist

  • ToDo has a flow. It knows about cycle times and about being DONE. Trello does not.
  • ToDo has Planning Poker Estimates. Trello does not have any estimates.
  • ToDo has automatic burn up charts. Trello does not.
  • ToDo has swim lanes which groups cards by your dimensions. Trello does not.
  • ToDo has Work-In-Progress limits. Trello does not.
  • ToDo has upgrade possibilities to the full tool set of Projectplace. Trello has a bunch of plugins from different vendors of various quality.
Swimlanes on a ToDo board

Swimlanes on a ToDo board

Already convinced? Sign up for ToDo by Projectplace! Want to know more? Read on.

read more »

Det är inte bara din ScrumMaster som behöver förstå vad “agile” är!

Posted on by

Återigen har ni diskussionen om “working software over comprehensive documentation” verkligen betyder att man inte behöver dokumentera någonting alls. Eller diskussionen om det är ok att förlänga sprinten med några dagar för att hinna klart den sista fixen på den där storyn. Eller diskussionen om vad det egentligen innebär att vara “lean”. Känner du igen dig? Kan det vara så att alla har nytta av att ha samma grundförståelse av centrala begrepp i och runt “agile”? Läs vidare för ett enkelt sätt att skaffa den kunskapen! read more »

Nytt matigt kapitel till Riv pyramiderna igen

Posted on by

På ett bräde blev boken Riv pyramiderna igen dubbelt så tjock (222 sidor) med det nya kapitlet “En organisation utan huvud – en agil odyssé“. I den gör vi en historisk, praktiskt och teoretisk resa från apache-indianerna, över Ford, Toyota, Lean, Scrum, Agile, flödeseffektivitet, Hegel, Kant, hur det påverkade oss och mycket mer. Slutstation:en massiv förfyttning av makt till den agila organismen – teamen. Här är underrubrikerna:

  • När Sloan slängde ut Drucker och barnen med badvattnet
  • Kunden i centrum – från Österike till Japan
  • En agil kunskapsteori
  • Scrum – Toyota för programmerare
  • Kontinuerlig förbättring – kunskapen finns på golvet
  • Kult av kvalitet – människan i maskinen
  • Stoppa bandet – och bygg in kvaliteten
  • Vid behov – skapa drag
  • Ibland är det bättre att gå hem – eller vad är flödeseffektivitet?
  • Jobba i lag – ta bort alla köer
  • Motivation – Purpose, Autonomy, Mastery och så lite umgänge
  • Scrum och flödeseffektivitet
  • Kanban i mjukvaruutveckling – utveckla din egen process
  • Rätt sak, på rätt, sätt regelbundet – en agil formel
  • Gro en smidig kultur – med fraser
  • Lägg till lite kaos för innovation
  • Hypertextorganisationen – centralt skelett, distribuerad hjärna

Köp den nu, den blir aldrig billigare

Good and Bad Technical Debt (and how TDD helps)

Posted on by

Technical Debt is usually referred to as something Bad. One of my other articles The Solution to Technical Debt certainly implies that, and most other articles and books on the topic are all about how to get rid of technical debt.

But is debt always bad? When can debt be good? How can we use technical debt as tool, and distinguish between Good and Bad debt?

read more »

MIKE – The Daily Meeting Microphone

Posted on by

This is MIKE, The Daily Meeting Microphone.
MIKE is a concept. An idea.  Captured on a poster.

If you like it; Click the image below (or click here to download the powerpoint). Print it on A3 format. Put it on the wall next to your team wall or in the office corridor. Done :-)

If you would build it, I’d buy 50 pieces of it :-)

Slides from Dare – “Visualization, what’s my brain got to do with it?”

Posted on by

Just got back from DARE conference in Belgium.  I don’t know how Maarten makes it happen, but I always leave with more ideas than I had when I came.

I ran a session on visualization – highlighting our brains limited capacity capture and record knowledge (and what to think of when using visualization).
An amazingly interesting subject. I also introduce five lenses to visual work which (you as coach) can choose to apply in the order the organization is capable of  learning from it Room was packed which always warms a presenters hart.

Enough talking, here are the slides!