Normally I’m very wary of “investigation” or “research” cards in a delivery team. Sometimes there are pieces of development work that are difficult, but I usually find that when a … Continue reading One good approach to development “research”
This week I was listening to a great podcast conversation between Ian Gill and Andy Bold, focusing on Andy’s area of expertise, which is devops. (Disclaimer: I am part of … Continue reading Team optimisations can have wider consequences
Many years ago I worked with a team that seemed to be delivering software only very slowly. There were multiple causes, as is usual in these situations, and part of … Continue reading Simplifying estimation
Every so often someone asks me, “So, have we got the green light for Project Blah?” There is always some project that’s particularly exciting, and anticipated by team members, and … Continue reading You don’t need just one green light for a project
I often talk to people about their “value statement”—a statement of the value of their programme or project. But how do we make our value statement most effective? From my … Continue reading What makes a good value statement?
One of the challenges with speaking to senior stakeholders—and really I mean the stakeholders who sign the cheque that pays for our work—is being able to promise them something that … Continue reading Stakeholder commitments on a sliding scale
I was asked recently about the ideal relationship between the architecture and development functions within an organisation. In some sense the ideal relationship can take many forms, because the shape … Continue reading The development/ architecture feedback loop