Human DevOps

Saturday 3rd June - Individuals and Interactions over Processes and Tools

Published about 1 year ago • 2 min read

This is Rule #1 of the Agile Manifesto. In 2023, do we really value individuals and interactions over processes and tools? I think for the most part, we still don't, however we still should try. Why? Read on...

This statement says that we should still value processes and tools - but not as highly as individuals and interactions. However, interactions are hard - especially if we're remote. Interactions are costly. Interactions are difficult and human. Interactions can cause us to have to change what we think or do. Interactions are something that we want to avoid, perhaps?

So we fall back to tools. We fall back to processes. We have a Definition of Done (which we ignore). We have a Definition of Ready (which we ignore). We write terrible stories (but they are good enough). We don't write enough tests (because we don't have time). We drift.

How can we stop drifting? By committing to something we all agree on.

Last week I was over at the first-ever Fast Flow conference in London for a day of presentations and activities with those who would probably describe themselves as Team Topologies aligned practitioners or those who have benefitted from these approaches. Many of the people I spoke with would also probably describe themselves as having an inherently human-first approach to delivering software. These people understand and accept that teams and their arrangement are fundamental to the success or failure of software projects.

One of the underpinning principles of Team Topologies itself is that Conway’s Law is real and that, to a certain extent, you can reverse-Conway your architecture by wilfully designing your organisation. Martin Fowler writing as recently as last year, has also been vocal in his support of this key principle in software engineering. Conway’s Law is, therefore, pretty much an inescapable fact. Acknowledging this and designing your organisation thoughtfully around it should now start to become common practice.

Team Topologies works at a team level, but before you can start to consider the team, you need to consider the individual.

By challenging individuals to consider and question all of their default interactions, I believe you can form a team with the necessary attributes to make a solid stream-aligned team for delivering a faster flow of customer value. Check out the full article for more details and I'll be presenting some more thoughts about how you can achieve this practically at the We Are Developers Conference in Berlin at the end of July.

Enjoy your weekend!

-- Richard

How To Identify a Killer Product Organisation

Published on May 23, 2023

Software is innately abstract. Visualisation and description are sometimes useful to communicate individual pieces, but as a whole, the interactions are often too complex and dynamic to be represented by anything static like words or pictures. Software systems are nondeterministic to the point that it sometimes seems be more craft than engineering, more art than… Read More »How To Identify a Killer Product Organisation


Human DevOps

by Richard Bown

DevOps at is the heart of modern software systems. In my regular newsletter, I dive into the human factors that make successful engineering organizations where teams and platforms thrive at the heart of your socio-technical systems. From leadership to team setup, maximizing performance, tools and techniques.

Read more from Human DevOps

It's good to recognise our changing preferences as we move through the world of software engineering and use those moments to choose the right tool for the job. Sometimes we want to create, sometimes we want to retrench - perhaps refactor something, improve something, add more tests, change our architecture either subtly or fundamentally. In the world of SaaS and open source, we have more than just language, cloud or platform choices. We have tool choices which can mean that we do less...

7 days ago • 1 min read

I have an emotional reaction to peanut butter that is so strong, it’s actually physical. I feel physically sick getting it on me, cleaning it off a surface, or even contemplating eating it. Why? A story. When I was seven, my parents sent me to a preparatory school. During the weekdays, I would board—I would stay over—in a dormitory with other kids around my age. I would come home on Friday night and then leave again for school on Sunday afternoon. I dreaded it. At least, to begin with, I...

14 days ago • 1 min read

I'm sitting on the sidelines watching another big digital transformation roll into town. Those who have tried this before before know that big digital transformations don't work, so we're better not calling them that. Instead, these days we talk about cultural change. Realistically though this means the same thing. How can you recognise one happening in your firm? Well, suddenly there are a lot of meetings, and workshops looking backwards and training looking forwards. Some people might call...

21 days ago • 1 min read
Share this post