Fractals, the solution to all of your scaling problems. Including Scaling Agile

It is no secret that I love planning. I’m not coming out of the closet now, that’s been true forever! And at some point in my life I was even “cool” with that. Additionally, I want you to know (although you will not yet understand why) that I still love planning. That’s me 🙂 Now …

The simple recipe for disciplined organizations

One question puzzles non-Agilists more than any other question. It is the question that uncovers why Agile does not fit their view of the world. A question that makes non-Agilists feel insecure and reject Agile completely or mostly. This question is: how can less structure, and less planning deliver software more reliably, and with higher …

Which do we need the most, Project Managers or Line Managers?

Should we organize around the delivery of products or along the structure of our organization? Which organizational paradigm is the most effective or efficient? This is a question that most managers struggle with regularly. At least when they are asked to “re-organize” their respective organizations. In Europe (and I suspect elsewhere) this has led to …

Dude! Where’s my manager? or Why you should attend LESS2011

Many teams start their agile transition from the “developer-side”. This is quite normal, developers (coders and testers) feel the pain more than others because they need to actually get the product/system finished. But by focusing on developers, aren’t we missing something? Aren’t we forgetting that many of the consequences we so detest come from un-informed …

SWAT Team, a Pattern for Overloaded, Multi-project Organizations

We all have seen it in our projects. Some teams are overloaded and can’t deliver what we need while others are not so busy and could even tackle more work if there was a need for that. This type of partial overloading is easily understood if we picture the work flow as a network of …

The “it’s not my bug” anti-pattern

Talking to a friend we were discussing the organization of feature teams in a local company. They were previously organized in component teams, which led to a lot of inefficiencies and disconnected work. This happened because one team would only work on one component, and when one feature required work in many components, that feature …