Re: [scrumdevelopment] Sprint Planning Resource Allocation
- In our distributed environment, similar to yours, we couldn't make sense
of things until we realised that what we had was 3 colocated teams
rather than 1 distributed team. Once we accepted that reality things
fell into place a bit easier. Might not apply in your situation though.
Michael Hedgpeth wrote:
> Point taken. Pair programming could work in our situation, however
> the third team is in another country and has little experience with
> the software. I'm coming away from this conversation with this idea:
> In a normal agile project, where everyone is collocated, people will
> balance their skill levels out through pair programming and regular
> daily interaction. This would make sprint planning easier because
> there will be fewer specialists on the team.
> In the absence of this environment, one has to accept more of an
> individualistic approach and will experience less of the benefits
> being agile. The costs will most likely outweigh the benefits, so one
> does so to his team's detriment.
> On Wed, Aug 6, 2008 at 5:58 AM, Ron Jeffries <ronjeffries@...
> <mailto:ronjeffries@...>> wrote:
> Hello, Michael. On Wednesday, August 6, 2008, at 6:48:02 AM, you
> > That's certainly something I would like to try, but our team is
> split up in
> > three locations (4 developers, 2 developers, 4 developers), so I
> can't see
> > how it would work.**
- Michael Hedgpeth wrote:
> Pair programming could work in our situation, however theI have never been in that situation, but if I were, I would seriously
> third team is in another country and has little experience with the
think about distributed pair programming.