"We are looking for a location where we can all be, regardless of where we all are."
After 48 weeks of doing SCRUM, with the number of teams growing from 1 to 6 and trying out different implementations, we now face a new, interesting challenge. Our 5th and 6th SCRUM teams have started in... Chine and India.
So, here it is: "One of the biggest mantras for Agile teams is that you have to be co-located. If you are not co-located, you are not going to be highly performant." (Julie LeMoine, the Fidelity Center for Applied Technology) That's the thing. Everybody, at least in our situation, beleives that one of the biggest benefits is that all team members and teams are at walking distance. Most of them even at pebble throwing distance. And they also agree that most of the problems we face are communication problems with people who are further away then the earlier mentioned.
So how are we going to handle two teams in another part of the world, are we going to share the backlog? Do we instate another product owner? Are they actually working on another product? How do we do shared meetings when we are in different time zones, e.g. for our daily stand up?
Of course there are theories and people who have thought about issues like these, but like always, one also needs to regard the issues of the specific company. And what the possibilities we have to change things. So I'll be probably reading the books below, but also start a discussion, maybe just a theoretic one, with some people and see how we get all advantages there are out of it.
I would be very interested in your opinion and experiences on this, and maybe communicate with the collegues in China and India on a more regular basis, to see what happens from your perspective.
These might be interesting to read:
Monday, 5 September 2011
Subscribe to:
Posts (Atom)
Labels
- Agile (10)
- SCRUM (10)
- management considerations (6)
- methodology (6)
- usability (5)
- Business Value (4)
- ria (4)
- flex (3)
- marketing (3)
- user centered design (3)
- Transition (2)
- application design (2)
- distributed SCRUM (2)
- maturity (2)
- microsoft (2)
- offline desktop applications (2)
- AIR (1)
- CSS3 (1)
- Firefox (1)
- HTML (1)
- HTML5 (1)
- International teams (1)
- PET design (1)
- Twitter (1)
- adobe (1)
- advertising (1)
- browsing (1)
- copy (1)
- customer experience (1)
- demo (1)
- design guidelines (1)
- filesystem (1)
- generations (1)
- incremental (1)
- iteration (1)
- maths (1)
- online applications (1)
- optimization (1)
- people (1)
- popularity (1)
- progress (1)
- projects (1)
- raking (1)
- ria projects (1)
- rounding (1)
- silverlight (1)
- social media (1)
- teams (1)
- time boxing (1)
- usability testing (1)
- web 2.0 (1)
- website design (1)
- website development (1)