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: technical practices
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
Make BlackOps development the Corporate Standard – Embrace Microservices
Contrary to how they are perceived in the media as lumbering dinosaurs, most large organisations have loads of clever people and good ideas.The trouble is these organisations can’t deliver against the ideas. The answer is not “Blue Sky” R&D departments or “BlackOps” teams. The answer is to make the BlackOps approach standard; create an innovation platform built from microservices with new services deployed swiftly into production.
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
Don’t use the Formal User Story Format for Minor Modifications
Kim Daubney asked what to do when the story isn’t a new requirement but a UI change. Kim wanted to know if the “as a, i want, so that” format is still required? Short answer is “no”.
Continue reading
Seven Things to do When Starting Specification by Example with Cucumber
I was asked “What to do in terms of training and practice when starting to use gherkin to define requirements?” Although I’ve written quite a lot of material on Specification by Example I haven’t written about how to start doing it.
Continue reading
I always work with a Technical Lead. Always
They might be called an Architect or a Tech Lead or just “Bob” but I always work closely with a senior technical person.
Continue reading
Five things to do when people don’t to see the value of automation
Not everybody sees the value of automation, specifically test automation. But I believe effective software development demands test automation. What to do?
Continue reading
Who is Specification by Example for? Everybody!
I was talking to Pedro Santos on the train the other day. Pedro is my technical lead, an expert in his field and a keen advocate of automated testing and software craftsmanship in general. We were talking about Gherkin and Pedro was saying he doesn’t see Gherkin tests adding value because it doesn’t help him as a developer. Of course I disagree. The way I look at it is the Gherkin tests are not for the developers. The Gherkin tests are for the organisation – they are for everybody.
Continue reading
Solution Convergence: Marrying Business, User Experience and Technical Input
My product owner was upset when I told her she couldn’t have the widget that she had agreed with the User Experience (UX) Designer. The problem was the design was not technically feasible. To get a great solution to meet the business requirements three parties – business, user experience and technical – must agree on the approach. That negotiation is what I call “Solution Convergence”.
Continue reading