For What It’s Worth

This content is syndicated from VersionOne by VersionOne. To view the original post in full, click here.

agile - stop, look, listenI've used this theme before but I need to once again give my nods to Buffalo Springfield.  It is absolutely time we "Stop Children, what's that sound, everyone look whats going down..."

I get involved in a heck of a lot of discussions about agile development and the methodologies that have grown from agile.  In my travels around the world as an agile coach, I've met a lot of people that have interesting takes on what agile is.  What seems to be missing in most of these discussions is the theme of *programming*.  We talk about how to convince the executives it's worthwhile.  We talk about how important a rhythm is.  We have lots of discussions about what user stories are and how big or small they should be.  But we don't talk about the code!

Now it is time for me to interrupt this rant with a couple of caveats and disclaimers.  I believe very stongly that agile methods require discussions about project management.  I believe strongly that we need to understand what stories are and how to create them.  And I believe with every fiber of my being that one thing that differentiates agile software development from all other forms is that the value of all members of an agile team is recognized, not just one particular role.
agile inspect
The fact that agile has "elevated" the other roles to the same level as programmers is a good thing.  But have we gone too far?  Have we now gone to the extent that we are, in essence, focusing on everything except programming?  I believe that we have.

Let's go back and consider what it is that makes agile special.  We believe that change, even late in a project, is something to embrace, as it will add value to our customer's final product.  We encourage customers and stakeholders to constantly review the priority of their stories and re-sort them.  We state that we will only sign up for stories that are sized in a way that they can be complete in a single iteration.  These are all good things, but they are predicated on one basic fact:  The code has to uphold these changes.

Back in the early days of Extreme Programming, many of us were getting very excited because we had finally found a process that got the programmers in touch with the customers.  We found that we can embrace change, because we are producing high quality software in small increments.  This software is covered by automated unit tests so that if we want to change something, we can feel comfortable that the tests will catch any egregious errors.  It is the very presence of these programming activities that make agile development work.

agile programmingAnd yet, as I visit with clients and join in discussion groups, I am surprised by the absolute dearth of discussions about programming.  I see teams that are 100% on the mark with all of the project management techniques in agile, and yet do none of the programming techniques.  And guess what?  They aren't seeing a huge increase in benefit.

So let's renew our commitment to great software.  Let's keep doing the agile project practices that we hold near and dear to our hearts, but let's also focus on how can we write the best, cleanest code possible.  How can we make this code so cohesive yet loosely coupled that it can be changed at the drop of a hat?  How can we write code that will be so easily readable that *anyone* on the team can pick up any story and implement it, without having to rely on an expert or the original author?  And for heaven's sake, let's make sure that the code we write does what the customer wants.  After all, the customer really doesn't care what processes we used, they just want software that does what they need.

Leave a Reply

Your email address will not be published. Required fields are marked *

7 + nineteen =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch