I don’t know if it was Alistair Cockburn’s inspiration but I’ve noticed a striking similarity between Cockburn’s HeartOfAgile and the plan-do-check-act (PDCA) cycle of TQM.
Continue reading
Tag Archives: agile
Going back to basics with Agile, what would we find? The Heart of Agile
In a world with non-software Agile and Agile at scale, what is Agile? I think Alistair Cockburn has hit the nail right on the head with his recent HeartOfAgile.
Continue reading
Quality is a choice: the case of the Next Generation Apps
Over the last year I’ve had the privilege of overseeing the development of the next generation of mobile apps (iOS and Android) for the major commercial radio brands in the UK. The most amazing thing about this experience was the priorities – UX&D was #1 priority – something I’ve never had before.
Continue reading
What is the optimal number of manual testers in a development team? Zero?
To have manual testers, or not to have manual testers, that is the question. Typically I have one per team: Less than many teams but more than some organisations get away with.
Continue reading
Delivery Manager – A new role for an Agile world
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
Disruptive Innovation is an Illusion Hiding Efficiency
The way I see it disruptive innovation is an illusion to observers who have not had the same focus. From my experience that apparent disruptive innovation actually comes from companies who have invested and honed very tight, very frugal or cost effective product iterations on what is ultimately a predictable destination. In other words, to be truly innovative in a digital landscape you just need to be very efficient.
Continue reading
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