A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

How does the Scrum team decrease the difference between Capacity and Velocity (contd..) ?

In the previous post on this topic (geographic distance between the Scrum team members), I talked about some of the problems that are faced by teams that are separate geographically, and how such distances and the issues that are caused by such distances can impact the productivity of the teams. What is needed are steps to ensure that in such situations, the teams are still able to feel connected and the issues due to the distances are minimised.
One approach is to have clearly defined time periods where team members from both teams can interact. This can be in the evening / morning, with some amount of inconvenience, but it is necessary to have such time periods for discussions. One needs to sensitize team members that with such cross-geographical distances, it is necessary that some amount of morning or evening effort would need to be involved. Before the Daily Scrum meeting, or other meetings where issues need to be discussed, team members should have prepared lists of queries and sent those by email prior to the meeting. Further, tools that make for instant communication such as instant messengers, phone messages, chat services (including group chat) should be encouraged since they increase the connectivity between the teams, creating deeper connections, and reducing the surprise element. This goes a long way in reducing any mis-communications between geographically separate teams, and we have seen this working when there have been cases of teams working across geographies.
Another approach is if it is possible to have the teams separated into separate Sprint teams that are co-located, there are a huge amount of advantages. This may require some amount of re-alignment of feature work across the teams – consider the case where team members are slowly added to the project in both geographies, and it is very much possible that feature work may happen across the geographies. In such cases, some amount of re-alignment can ensure that sub-features are done by teams located at the same geography and this will increase the efficiency of the team, leading to an increase of the Velocity of the team.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>