Comments on: How To Share An Agile Development Team http://www.allaboutagile.com/how-to-share-an-agile-development-team/ Agile Development Made Easy! Sun, 19 May 2013 08:16:47 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Andrew Hedges http://www.allaboutagile.com/how-to-share-an-agile-development-team/#comment-145 Andrew Hedges Mon, 26 Nov 2007 01:44:00 +0000 http://allaboutagile.com/uncategorized/how-to-share-an-agile-development-team/#comment-145 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?

]]> By: Alexey http://www.allaboutagile.com/how-to-share-an-agile-development-team/#comment-80 Alexey Wed, 18 Jul 2007 17:14:00 +0000 http://allaboutagile.com/uncategorized/how-to-share-an-agile-development-team/#comment-80 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.

-Alexey

]]>