I am a little wary that “agile” appears to have become a morally loaded term. Despite some unhelpful dogma, the gradual shift towards developing software by iterative collaboration has been a universal “good thing”.
8 January 2021
Estimates are difficult, usually wrong, and frequently misused, especially at the “epic” level. An “appetite” can be a more meaningful measure that defines the amount of time the business is prepared to invest in the solution.
24 August 2020
There can be a tension between the lean, experimental nature of agile development and the more deliberate, planned demands of a large organisation. It does not have to be like this.
11 March 2020
The discipline of architecture is an important part of any efficient engineering organisation. It just needs to adapt its game from the process-orientated “Enterprise Architecture” of old to something more collaborative and relevant.
19 February 2020
Code coverage can be a useful technique for discovering untested parts of your code base, but it makes for a useless target.
9 September 2019
There’s more to adopting trunk-based development than deciding to shun long-lived branches. You need a confident development team, a loosely coupled code base and efficient build automation to make it stick.
12 August 2019
Agile process tends not to generate the kind of metrics that management teams feed on. Should this be a problem?
8 June 2019
Maturity models are a popular way of looking at development challenges. The problem is that they are an arbitrary and inflexible tool and they tend to encourage the wrong mindset.
23 March 2019
The problem with SAFe is that you can implement it without writing a single unit test or automating a single build…scaled agile may be an oxymoron.
24 February 2019
Standardisation does have a place, but it should be reserved for infrastructure and collaboration rather than languages and tools.
30 August 2018
There is a growing sense of unease around how larger organisations have implemented agile. In particular, there is a tendency towards centralised control that can be at odds with the agile preference for individuals over process.
29 July 2018
It’s easy to get caught up in unrealistic notions that you can re-write a legacy system or gradually decompose it. There are other, more pragmatic approaches that can help to modernise architectures and enable new development.
16 February 2018
Agile teams still need to make architecture decisions, but in supporting them architects should seek “just enough” architecture over “big design up front” and practical solutions over large-scale abstract thinking.
27 January 2018
On the face of it, TOGAF describes a very different world to the agile preference for working software over documentation. That doesn’t mean that TOGAF is incompatible with agile, so long as you’re prepared to adapt its numerous building blocks.
18 November 2017
Technical debt may be a useful metaphor for describing how bad code design undermines productivity to non-technical audiences, but it does not help in understanding the longer term problems that affect code bases.
12 October 2017
The Scaled Agile Framework talks about an “architectural runway” as the main deliverable for agile architecture, yet it’s vague on the detail of what this looks like.