It’s funny, isn’t it? Everybody is still talking about ‘scaling agile’. A whole industry has been created on the premise that large companies need process structures to help them manage pushing very large projects through huge sets of development teams. Luckily, the DevOps movement (and the continuous delivery movement, I’m not sure they’re really separate) … Continue reading Scaling: Local vs Full Vertical scaling
Everyone seems to want to get on the Continuous Delivery train. Rightfully so, I think. For most, though, it's not an easy ride. From my work with client and conversations with other coaches there's a few common barriers to adoption. In the end, the goal should be to be able to react faster to the … Continue reading The three failures of Continuous Delivery
I recently had the chance to speak at the wonderful Lean Agile Scotland conference. The conference had a very wide range of subjects being discussed on an amazingly high level: complexity theory, lean thinking, agile methods, and even technical practices! I followed a great presentation by Steve Smith on how the popularity of feature branching … Continue reading Don’t Refactor. Rebuild. Kinda.
In his post "The Goal in Scrum", Ron Jeffries makes the case for having a proper, higher-level-than-stories, Sprint Goal. As he says: This is better, because it allows the wisdom and knowledge of the team to be fully exercised, and because it keeps focus on “what” is needed more than on just how it is to … Continue reading Extending the Goal in Scrum
Situation Normal There's a clear pattern for software development. A pattern of lost opportunity. In most, if not all, places where I'm called in the base question deals with the inability to deliver. Management sees that the plans they have are simply not going to be realised. Business opportunities are lost waiting. Waiting for the … Continue reading From Here to Continuous Delivery
On occasion, I like to listen to podcasts. Some of the most interesting can be those that are from outside of the software industry. This week I was listening to Robb Wolf's podcast, where he hosted guest David Werner. Robb talks mostly about diet, metabolism and exercise, and this episode was focused on that last … Continue reading Everybody need somebody
I wrote a while back about set-based design, and just recently about a way to frame scaling Agile as a mostly technical consideration. In this post I want to continue with those themes, combining them in a model for scaled agile for production and research. Scale In the previous post, we found that we can … Continue reading Scaling Agile with Set-Based Design
Last Friday I gave a talk at the Dare 2013 conference in Antwerp. The talk was about the experiences I and my colleague Ciarán ÓNeíll have had in a recent project, in which we found that sometimes a very directive, Just Do It approach will actually be the best way to get people in an … Continue reading The ‘Just Do It’ Approach To Change Management
organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations. -- Melvin Conway We often run into examples of Conway's Law in organizations where silo-ed departments prompt architectural choices that are not supportive of good software design. The multi-functional nature of Agile teams is one way to … Continue reading Conway’s Organizational Structure Heuristic
There's a lot of discussion in the Agile community on the matter of scaling agile. Should we all adopt Dean Leffingwell's Scaled Agile Framework? Do the Spotify tribe/squad thing? Or just roll our own? Or is Ron Jeffries' intuition right, and do the terms scaling and agile simply not mix? Ron's stance seems to be … Continue reading Scaling Agile?