Tired of the same old boring and ineffective daily meetings with your team? Try this new Awesome Team Focus daily routine! It will help your team use a swarming technique to laser-focus on the stuff that really matters and get it done. As a bonus it will help you start limiting Work In Process withoutContinue reading
Yep! The collection of Kanban boards now is now available in french. Big thanks to Nicolas Mereaux who made it happen! Here’s the link to “10 tableaux kanban et leur contexte” (fr). (the english 1.5v is available here )Continue reading
The Kanban and Scrum minibook is now available with Polish translation. Great thanks to Zbigniew Zemla for the translation! Pobierz tutaj (aka polish for “get it here” ): http://www.infoq.com/minibooks/kanban-scrum-minibook Cheers MattiasContinue reading
Just back from Lean Kanban France where I gave a presentation on “Learnings across Kanban case studies, and what happened next” and introduced Skarin’s law: ”The number of improvement initiatives in a kanban system is proportional to the trust members have in that systems purpose” (.. it’s never too late to introduce your own law 🙂Continue reading
Are you thinking about electronic Kanban tools? Do you need transparency to end-to-end flow? Do you work across multiple sites? Tired of managing work states in Jira? Here’s a short video demonstrating visualisation, analytics and key features in Swift-Kanban & Leankit. Both combine “simple and flexible” with “enterprise ready”. I also mention an interesting runner up – Obeya. Some things IContinue reading
For this year’s Stop Starting conference, we asked ourselves three questions: How do you develop awesome products? How do you bootstrap a successful mega project using Agile contracts? How do you use Agile and Lean thinking to turn a stagnant company around? We then picked the brains of people from real companies who have beenContinue reading
Update: The book has since the publication of this blog been
made available for purchase at LeanPub.
A couple of weeks ago I published my new book ”Toolbox for the Agile Coach – Visualization Examples (How great teams visualize their work)” even though it’s still very much a work in progress.
I’ve made it public, thanks to persuasion from my colleague Hans Brattberg. I decided to try out Google Slides to make it easily accessible and to provide a simple way to give feedback. That turned out to be a great decision. The response has been overwhelming. There are at any given point 5-15 people reading the book, many of which provide great feedback, point out spelling correction and provides generous suggestion for more examples.
It’s always nice to look at real data and these two studies are worth their read.
- “Impact of Agile” from Rally compares the effect of WIP and estimation techniques on productivity and quality.
- “The State of Developer Productivity” by Rebel labs examines the effect of XP style techniques on quality and predictability.
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.
- 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.
Already convinced? Sign up for ToDo by Projectplace! Want to know more? Read on.
Å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!Continue reading
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 massivContinue reading
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?
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 🙂 IfContinue reading
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 amazinglyContinue reading
Added a visualization combining architecture with progress follow up for more complex product development scenarios. You’ll find the complete collection of boards here! Cheers MattiasContinue reading
Agile India 2013 in Bangalore. Wow, what an awesome conference! I was amazed by the energy level of the participants, spent hours talking to people about all kinds of really interesting challenges. Based on the fully packed rooms and incredible feedback, it seems like my talks were exactly the kind of information people were lookingContinue reading
I gave a talk to a group of mechatronics students at KTH (Royal Institute of Technology) today. The topic was agile software development with an emphasis on Scrum, and some information about Kanban and Lean Startup. Here are the slides: KTH-2013 Get in touch via my homepage if you have questions or comments!Continue reading
(UPDATE: see Spotify Engineering Culture, two short animated videos showing how we work)
Dealing with multiple teams in a product development organization is always a challenge!
One of the most impressive examples I’ve seen so far is Spotify. I’ve had the pleasure of working with Spotify on and off ever since the company was founded, and it’s one of the few companies I’ve seen with a truly agile culture. Spotify has grown a lot lately and now has hundreds of developers divided into 30 agile teams spread over 4 cities in 3 timezones. So how is this managed?
Check out the article: Scaling Agile @ Spotify with Tribes, Squads, Chapters and Guilds. I wrote it together with Anders Ivarsson, one of the agile coaches that I’m working with (Spotify has a truly awesome group of coaches!).
Here are the slides for my talk “Lean from the Trenches” at Øredev, Malmö. And here is the book/ebook, in case you want more details. There may also be some copies left at the conference bookstore. Thanks for attending!Continue reading
This is basically a 1 day product ownership course compressed into a 15 minute animated presentation.
Over a million views! Some call it “The best 15 minutes on the Internet” 🙂
There’s obviously more to product ownership than this, so see this is a high level summary.
- Here’s the complete drawing (.png format)
- Here’s a downloadable version of the video, in case you don’t want to stream (.mov format, 90 Mb)
Special thanks to Alistair Cockburn, Tom & Mary Poppendieck, Jeff Patton, Ron Jeffries, Jeff Sutherland, and Michael Dubakov for providing many of the models, metaphors, and ideas that I use in this presentation.
Translations: (see also the translation guide by Cédric Chevalerias)
- Chinese – simplified (subtitles)
- Chinese – traditional (subtitles)
- French (voice)
- German (subtitles)
- Italian (voice)
- Japanese (subtitles)
- Polish (voice)
- Portuguese – Portugal (voice)
- Portuguese – Brazil (voice)
- Russian (voice)
- Spanish (subtitles)
Below is a full transcript in english. But I recommend watching the video instead of reading the transcript. The video is 100% visual, the transcript is 0% visual…
Hi! Just back from a great conference – LKCE 2012 – and a great town – Vienna. A really cool thing was the illustrator who worked around the clock to visualize how he interpreted the difference presentations. He did a great job (see below). What would you do – learning from charts I challenge theContinue reading
For the past couple of years I’ve had to work with Jira. Really, it’s mostly been dreading working with Jira. At both projects I’ve had Greenhopper available, and that hasn’t really made things better. My frustrations have had to do with the complexity of setting up the right fields, to creating a new sprint to creating a new project, down to mundane things like problems with ranking. I don’t particularly enjoy spending hours just tidying up my data. I want to quickly organize so I have time to actually work. I also want to easily see how much work we’ve done, and how much we have to do. Cards and a physical board are great for this, but I end up with stacks of cards everywhere, and after several sprints I don’t know what to do with them anymore. Enter Trello!Continue reading
Here are the slides for my talk “Lean from the Trenches” at Agile2012. And here is the book/ebook, in case you want more details (unfortunately sold out in the conference bookstore). Thanks for attending!Continue reading
Last month market the launch of the Kanban Accreditation scheme. Let’s give our view including why we have chosen to engage ourselves as members of the advisory board.
Why the Kanban accreditation scheme?
Kanban is a word that needs meaning. So what meaning do we want people to connect with the word? This matters (to us..) . Stumbling upon about kanban classes declaring it will help you “resource optimize” it makes me think there is a need. (To any unfamiliar reader.. kanban helps you improve flow, quite a different thing..)
Any accredited class will contain some core messages that we care to share. The best way we could think of to make sure that messages is good was to engage ourselves in the process 🙂