Building trust through right-sized initiatives

This content is syndicated from Agile Development Blog: Scaling Software Agility by Parker. To view the original post in full, click here.

Is a one-month initiative a good idea? Is a year too long?

We’ve gone back and forth on how big our initiatives should be. A couple of years ago, we brought Don Reinertsen in to teach a course about his book, “The Principles of Product Development Flow”. We certainly internalized a sensitivity to batch size. Minimizing feature batch size has been one of our great tools for accelerating flow. (We use a hierarchy of initiatives broken down into features broken down into stories).

It’s easy to jump ahead and assume that you should be striving to minimize batch size at all levels of your portfolio, and we have tried this. For a while, product owners tried to keep their initiatives small - one to two months in size. This had some benefits:

  • Each initiative was less expensive, so less money was at risk
  • Cards moved across our initiative kanban board regularly - progress was obvious
  • It wasn’t practical to approve all of the cards at the portfolio level, so we gave product owners more discretion in deciding how to manage work in their area.

But there were downsides - largely the converse of the benefits:

  • Because each initiative was small it was harder to understand exactly how much we were spending on each one.
  • Cards moved fast, so whenever stakeholders and executives looked at the board the work was unfamiliar
  • Because the product owners had the ability to create and launch new initiatives, stakeholders were not clear on how to evaluate the results.

Reinertsen goes into some detail about how to optimize batch sizes, and I really do recommend you read his section B11 on this. But in a nutshell, we want to balance transaction cost against holding cost.

If you are shipping features as they are done, the holding cost for initiatives is very very low. You can start a large initiative and be realizing value continuously. We are not holding items in a batch, the way we do with the user stories in a feature. The holding cost for initiatives only becomes higher if one of them is not shipping features regularly, or if the features it’s shipping are of lower value than a different initiative’s features would be. For the former, we have a different cadence to ensure features don’t get stick. Since value is hypothetical, you need to be sure you’re testing your value hypotheses to be sure on the latter.

So we’ve transitioned to a model where we actually are increasing the transaction cost of initiatives. We are requiring a portfolio-level conversation about the value hypothesis, the assumptions, and the success criteria. We’re setting a planned end date as a lightweight budget. Mind you, the template is designed to be filled out in 5 minutes and be about 100 words.

The target size of initiatives is 3-6 months. Our reasoning is that even the most senior product owners with the most discretion should still be checking back in with the portfolio council twice a year. The same with long-term investments - even if we intend to make them year after year, we still need to check in on whether their value hypothesis still holds.

Each initiative defines the parameters of trust for particular product owner. We’re saying,

  1. We trust you to work with these teams for this period of time to achieve these success criteria.
  2. You get to choose what features you ship to meet those goals.
  3. If you’re successful, you’ve built trust and we might trust you with more.
  4. If your hypothesis or assumptions are invalidated but you come back early you’ve built trust.
  5. If your hypothesis or assumptions are invalidated and you don’t come back to let us know but instead blindly continue with a now-impossible plan, you’ve weakened trust, but we’ll have a pre-arranged checkpoint where we can evaluate together what to do.
  6. If you’ve weakened trust, we can start rebuilding it with a new, smaller initiative with smaller goals.

How well is your portfolio process working at building trust between your stakeholders and your product owners?

Leave a Reply

What is 6 + 5 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

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

What People Say

“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.”


“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.”


“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 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!”


“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 was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“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. ”


“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.”


“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 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.”