Scaling Agile with Set-Based Design

I wrote a while back about set-based design, and just recently about a way to frame scaling Agile as a mostly technical consideration. In this post I want to continue with those themes, combining them in a model for scaled agile for production and research. Scale In the previous post, we found that we can … Continue reading Scaling Agile with Set-Based Design

The ‘Just Do It’ Approach To Change Management

Last Friday I gave a talk at the Dare 2013 conference in Antwerp. The talk was about the experiences I and my colleague Ciarán ÓNeíll have had in a recent project, in which we found that sometimes a very directive, Just Do It approach will actually be the best way to get people in an … Continue reading The ‘Just Do It’ Approach To Change Management

Scaling Agile?

There's a lot of discussion in the Agile community on the matter of scaling agile. Should we all adopt Dean Leffingwell's Scaled Agile Framework? Do the Spotify tribe/squad thing? Or just roll our own? Or is Ron Jeffries' intuition right, and do the terms scaling and agile simply not mix? Ron's stance seems to be … Continue reading Scaling Agile?

Spikes, they’re sharp

One of the concepts that came from XP is the Spike. Especially in teams new to agile, there can be confusion on what a Spike is, and how to deal with them. The best definition of a Spike I've found is this one: "Spike" is an Extreme Programming term meaning "experiment". We use the word … Continue reading Spikes, they’re sharp

Not Estimating At Scale

Estimation is a sensitive subject in Agile. Should we estimate? Do we avoid estimation in days or other time-based units? If we use relative estimation like story points, do we standardize across teams? What do we use estimation for? Are we explicit enough in emphasizing the distinction between estimations and commitments? How do we prevent … Continue reading Not Estimating At Scale

Set-based design in software

Last year at the Lean and Kanban Benelux conference I attended a session by Michael Kennedy: Set-Based Decision Making: Taming System Complexity. Watch that video, where he explains the way that Toyota uses set-based design to be innovative without risk to the schedules of their new product development projects. I thought that was a very interesting … Continue reading Set-based design in software

On Discipline: Fooling yourself is an important skill!

Discipline is an interesting subject. One that I find myself regularly talking about. Or discussing about. In the last year I lost about 20kg of body weight through a combination of diet change and exercise. This apparently give some people the impression that I am very disciplined. I'm not. I do know, however, how to … Continue reading On Discipline: Fooling yourself is an important skill!

On Effect Mapping and Pirate Metrics

During the Specification by Example training I talked about recently, Gojko Adzic introduced me to Effect Mapping. He's writing a more extensive booklet on the subject, of which he's released a beta here. I think this is an excellent tool for exploring goals, opportunities and possible features. It can be used as a tool to … Continue reading On Effect Mapping and Pirate Metrics

Management Innovation, ca. 1972

Yesterday, after my brother's 47th birthday, I was talking with my father. My father is 79, and he has had an interesting professional life. He started out as a catholic priest but, as you could guess from the fact of my existence, at some point figured out that this was not a sustainable career path … Continue reading Management Innovation, ca. 1972

Turning it up to 11

It's odd how I've been unable to be very consistent in my subject-matter for this blog. I tend to hop around, going from very technical subject to very organisational ones. Some might see this as lacking focus. Maybe that's true. I've never been able to separate execution from organisation and vision very well. To me … Continue reading Turning it up to 11