How To Share An Agile Development Team

How To Share An Agile Development TeamScrum, and other agile development methodologies, provide a framework for managing software development projects.

But all too often, methodologies focus on a project environment, where the team is focused predominantly on a shared goal. Where the team is largely dedicated to the project.

In reality, this is often not the case.

In reality, development teams are frequently required to develop and support multiple products. Multiple products with multiple product owners. And particularly in ‘business as usual’ ongoing development.

So how do you share an agile development team?

Operating as a resource pool is often not ideal. Everyone throws their requests over the wall. Those that shout loudest get the team’s attention. Or maybe the bigger products get the team’s attention, at the expense of smaller products that never get to the top of the list, and never will.

Splitting the team by product sounds great. But sometimes the team’s too small for this approach to be practical. Or it leaves too many individal developers, causing problems with cover and you can’t exactly collaborate with one developer per product!

So what can you do?

We have a similar situation in lots of our teams. Broadly speaking we are solving it like this:

  • There is one Product Owner per product. The Product Owner maintains a separate Product Backlog for each product.
  • The development team acts as one team.
  • The Sprint Budget (number of man-hours available for a Sprint/iteration) is allocated to each product based on our recharges, e.g. 60%-20%-20%. If you don’t recharge, you could agree this at a more senior level as a general rule of thumb. Each product has a known % of the budget for each Sprint.
  • Use Cases/User Stories/features are broken down into Tasks and estimated by the development team during Sprint Planning.
  • Each Product Owner can only include Tasks from their Product Backlog up to their allocated % of the Sprint Budget.

This approach means the development team can act as one team. There is knowledge sharing and cover when someone is off, because in this case the overall Sprint Budget is reduced but everyone still gets their usual % share of the available hours.

It also means team members don’t have to juggle their time between products on a 0.x FTE basis, which is awkward at best and just plain impossible when the fractions are too small or odd numbers.

Instead the Tasks allocated in the Sprint are already appropriate to the Sprint Budget per product, meaning team members can focus on delivering the Tasks in the Sprint, not worrying about how to split their time.


See also:
10 Key Principles of Agile Software Development
10 Good Reasons to do Agile Development
Top 10 Agile Development web sites

3 Responses to “How To Share An Agile Development Team”

  1. Alexey says:

    Hi Kelly,

    Could not help to leave the comment as the topic is quite familiar to me. We tried to address the challenge of accurate iteration planning, when the same team members sharing their time between multiple products, in our Yoxel SW agile product management solution. Although in a slightly different manner.

    In our case for each developer the tool allows you to set % of time he will be spending (or usually spends) on tasks from each product. This time sharing could look like 50% on ProductA, 30% on ProductB, and 20% on Other. Quite similar to what you’re saying, right?

    Now when you start a planning session for your next iteration for ProductA the 50% factor is used to adjust perfect time estimates (entered by the developer) for his tasks. This way you actually get realistic estimate in the context of this particular product/iteration and time sharing scheme.

    The same thing happens for ProductB, with 30% time spent on this product the realistic estimate will be that much longer than the perfect one. (9hr will become ~27hr)

    ‘Other’ means time spent on critical or unplanned requests. You can think of it as 1-[person’s individual velocity] :)

    Nice post, I am surprised I do not see this topic discussed anywhere else. From my experience this is a quite common situation when developers participate in multiple projects for different products.


  2. Andrew Hedges says:

    The way you describe in your post is roughly how we go about things, too. The problem we’ve run into is how to determine the order that we work on the various stories. In our domain, we have stories against a legacy system that tends to blow out our time estimates from time to time. That means we occasionally have to drop less important stories off the bottom of our board. You don’t mention an absolute ranking across backlogs, but would that be a solution to this issue in your eyes? If not, how would you handle this?

  3. Marten says:

    Good to hear a story about other teams that deal with the same challenge of sharing an agile team between multiple product owners.

    The way we deal with it is quite similar, and it seems like a workable process, but not ideal. An agile team by definition adapts to change. That is what we do right? Every standup we replan our work. So whenever priorities change, we deal with it. But what about conflicting priorities between two backlogs? What if changing priorities on one backlog effects the other? The way of working described here doesn’t really solve that. It becomes the team’s problem to decide what to work on next, not the product owner’s problem.

    A way to solve this is to find a product owner that can represent multiple backlogs. This is not as easy as it sounds. Product owner is a difficult role already for only one backlog, let alone multiple backlogs. It will be very hard, not to say impossible, to find this ‘product owner to rule them all’.

    So for now we stick to our current process, which like I said is quite similar to what has been described by Kelly. But I won’t rest to keep looking for better alternatives.

Leave a Reply

What is 8 + 8 ?
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.”