Programmes can use more than one method: Kanban, Scrum, XP, BDD, etc

I have my preferences – Kanban and BDD – but don’t enforce these on my teams. That means I’ve got a couple of Scrum (ish) teams and teams that don’t use BDD. And I also have a bunch of people working in isolation – I just leave them to it.
Continue reading

35 person-years worth of prototype is a fantastic spec

I once invested 35 person-years worth of effort on prototyping. From my perspective this was time and money well invested. By the end of that time we knew, really knew, what problems our customers were facing and how to solve them.
Continue reading

Scope Creep v Flexible Scope – Undisciplined v Agile

Bart asked “What do I do when agile is abused as an excuse for scope creep?” with the sub-text “You’re agile so you’re flexible, no?”. I say point out the difference between scope creep and flexible scope. Agile makes changing scope a zero sum game – that gives flexibility without the creepiness.
Continue reading

TPM – Project Manager who is technical or technical person who manages?

I squirm when I see a job description for a “Technical Project Manager (TPM)”. My experience is that an organisation advertising for a TPM is often confused about what they are looking for. Do they mean a project manager who is technical or a technical person who provides some coordination? Often you’ll find both types in the same “project management” team.
Continue reading

Little’s Law – the basis of Lean and Kanban

Sometimes I think it helps to go back to basics. And when using Lean Software Development, including Kanban, that means a man called Little and his Law. “Little’s Law” is a fundamental of queue theory and defines the relationship between Work in Progress (WIP), Throughput and Lead Time. It is the reason why Kanban teams try to limit WIP.
Continue reading