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 a series of articles, I am writing about issues that can cause the Scrum team to not reach their full potential, where the Velocity of the team is not meeting the capacity of the team (previous article). For the past couple of posts, I have been covering the case when the teams are located at different geographies, and this causes a reduction in the efficiency of these teams; in many cases, the teams know that they are not doing their best, and feel helpless about the communication issues and loss of efficiency that happens when teams are located at different geographies, and with different cultures and processes. For example, it could be as simple as the amount of openness that happens within a team varies across geographies and these cultural differences can trip up the overall amount of work that is possible.
In this article, I will talk about the cultural differences that are apparent in teams that are spread across geographies and these can problems. For example, a team based in the United States has a concept of openness that can cause huge issues in teams based in India, China, or the United States. For example, when somebody presents an estimate, or when the Product Owner presents a User Story that can be complex, it would be very easy for team members in the US to ask their queries, or challenge the estimates of others, even when the other team member is somebody that is senior to them. This can be a significant problem for teams in Eastern civilizations, where the concept of challenging somebody who is in a superior position (such as a Product Owner, or a developer who is much senior to the other team member).
The impact of this can lead to a loss of efficiency; consider the case where the team has not asked all the questions from the Product Owner about the details of the User Story, or more likely, when the team member has already asked a question, it gets more difficult to ask another question. But, the concept is that team members should be able to challenge estimates, or ask all the questions about User Stories, until they are clear. Else, the estimates will not be accurate, which can cause a severe impact on the productivity of the team.
What can we do about this situation ?
Well, that is something that I will try to answer with some detail in the next article of this series.

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>