I’ve just answered “Scrum” because that’s what I used last but I’m being slowly convinced that I’ve taken a first step towards Lean. I recently blogged links to a set of posts by hackerchick.com that explain why, brilliantly
There is no Agile process, only ‘agile thinking’ but it’s amazing how many people think there is. The guys who wrote the Agile Manifesto all came from different companies with their own processes and wrote down what they all agreed on.
‘The Agile family’ encompasses lots of optional stuff that you make your own process from. Scrum is a starting point as it gives a framework to build a process in. It’s a good way to migrate an organisation from Big-Everything-Up-Front to small batches without damaging the minds of managers who can think only in project terms. Some people really struggle to understand Scrum and many think they are ‘doing it’ when they’ve just built a façade on their old ways of working. If you believe Project Management works for software then you are probably going to struggle, as you have to throw away your religion.
p.s. more potential for confusion:
The word ‘project’ has a very specific meaning in traditional PM. Life is easier if you call Agile and Lean a ‘product development’. If you use the word ‘project’, it cannot mean what it used to, so don’t, because there may still be times where you have to talk about projects with the original meaning.
Kanban is both the idea of a board on the wall and a work scheduling process that replaces Scrum and uses the board. You can have a board but be ‘doing’ something that is not the Kanban Lean process, including Scrum. I’ve only just worked this out.