Rich Lewis is the best I’ve worked with. When I met him he was a Business Analyst who, on the sly, was Scrum Master of a small team. He was good at this but capable of much more. I invited him to be the Delivery Manager on the programme I was running at the time.
Continue reading
Tag Archives: flow
Continuous Delivery by Default; Timeboxes by Exception
Once I used timeboxes by default. Now I relegate Sprints and such like to exception situations.
Continue reading
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
Product Owner – leader, facilitator or unnecessary overhead?
Daniel Markham thinks the Product Owner is “the perfect scam in the Agile community” and recommends getting rid of the role. This might work for highly functioning teams working in highly functioning organisations, but for not normal teams. For normal teams in normal organisations the Product Owner performs a valuable role as a facilitator and, if you are lucky, a leader.
Continue reading
Test driven architecture – use your tests to inform architecture
As test-loving development teams, we are all painfully aware of the complexity of getting an application into the zen state of development – quick, test-driven red/green feedback for developers, software designs that are functionally on-the-money from a test-led, “outside-in” approach (from BDD), and a nigh on seamless continuous delivery process as a result. Very few teams achieve this, and those that do are frequently gifted a green-field project in which to engender them.
As test-savvy teams, when tests start to hamper the release process, we often assume our approach to testing needs an overhaul, but that might not be the case. Here we look at the role of architecture in test-driven applications, and examine whether we should listen to our tests to examine our macro design.
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
Deming wasn’t a fan of Management by Walking Around
W. Edwards Deming, credited with launching the Total Quality Management movement, wasn’t a fan of Management by Walking Around.
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
How to get Agile experience as a project manager? Just start
Tim felt in a Catch-22 situation. He wanted to break into Agile, however, without experience he had little chance of landing a job running an Agile project. He felt stuck and wanted help to find a way forward. My advice – just start.
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