This is a rambling-about-random-thoughts post. It goes a little out there. Have fun! This post was triggered by the Lean Code talk at #xp2017, by Desmond Rawls (@okokillgo) Using Lean Startup principles to improve code quality. Nick was using the normal code quality metrics for this. That is good, but: not all that actionable, and … Continue reading Random Thoughts: Measuring Technical Debt
The ancient and respected team of Science Ninja is amazing. For centuries (or so it seems) they’ve protected the temple of Llabdum. The temple is old, with many places showing signs of previous attacks, or simply crumbling rock and weapons still in the skeletal hands of fallen enemies. Or maybe, you know, just lego bricks … Continue reading The Blindfolded Ninja Model of Software Development
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
Monday, August 3, I had the opportunity to give a talk at the Agile Alliance's Agile 2015 conference in Washington, D.C. My first conference in the US, and it was absolutely fantastic to be able to meet so many people I'd only interacted with on mailing lists and twitter. It was also a huge conference, … Continue reading Agile 2015 Talk: Don’t Refactor. Rebuild. Kinda.
I haven't written anything on here for quite a while. I haven't been sitting still, though. I've gone independent (yes, I'm for hire!) and been working with a few clients, generally having a lot of fun. I was also lucky enough to be able to function as Chet's assistent (he doesn't need one, which was … Continue reading Outside in, whatever’s at the core
If you want to go fast and have high quality, communication has to be instant, and you need to automate everything. Structure the organisation to make this possible, learn to use the tools to do the automation. There's a lot going on about DevOps and Continuous Delivery. Great buzzwords, and actually great concepts. But not … Continue reading DevOps and Continuous Delivery
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
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?