Building the Agile delivery organization, Incrementally
Ramki Sitaraman
Engineering Partner at Thoughtworks | Healthcare, Energy Portfolio, Growth Enablement
I have designed it kind of a Provaction-Response format for incrementally developing a agile delivery organization. The article skims across the stages and is not an exhaustive material. For a proper advisory model, refer to the fluency model.
We have sprints
Running sprints is a small part of agile organization. It ensures that as a team, one is able to split the work in iterations, and that's a good start. At a minimum, one needs to have a prioritized backlog with some concrete prioritization framework.
We have sprints with prioritized backlog
Great ! You have a prioritized backlog now and think about how often does your customer use the application and provide feedback? Is your business throwing the backlog at you? Do you work as one team ?
We have sprints, with customer using them, Business works with us
Very nice- its great to know that your customer uses them, gets the value out of the product that you develop and business works frequently to see how the product is developed and shape that. Its a great feeling and how often do you go live and do you have an infrastructure to go live soon?
We go live every week, have CI, CD
We are getting better, it is great that you have tests, automation and an delivery infrastructure to get there often. I'm sure Business is happy that you can go live anytime and decisions are made collaboratively. Now, its time to examine if you have validated your product incrementally.
We go live every week, incrementally add value, get feedback
Terrific, you go live every week and add some value to the client. Examine if your pattern is to develop a Big MVP followed by weekly releases and then a big release again. While you might get feedback for what you deliver, examine if what you deliver is truly thin slice which is hypothesis driven.
All done !
yes, we are getting close. The final step is to check if your entire backlog is driven by hypothesis, you measure metrics and budget in portfolio driven by outcomes - and you truly become an amazingly responsive organization !
This is only a delivery organisation and doesn't have any equivalent journey in Technical or People capabilities. I will try to address the people journey in my next article.
Independent Consultant | Business & Technology Transformation, Program & Change Management
4 年Good one. I liked the provocation-response style. Will be a very good 2-min video material. Why don’t you try it, with some good graphics thrown in?
Large Deals Solution | Digital Transformation | Business Development
4 年Very well Articulated!!! It's vital to have key metrics in place and measure them at regular intervals to be informed about the level of maturity!