Skip to main content

Distributed Scrum Teams


Today businesses are shifting to emerging economies (such as India) due to reduced business operations cost and an easily available workforce. The businesses certainly are more virtual and distributed, with "distributed" as its key element. Thus the need for better managing such teams, using the right tools and processes, is becoming increasingly critical for any enterprise company.

Here are some reasons for the shift and need for having distributed Agile teams:
·         Globally distributed teams reduce costs.
·         They can reach the market more quickly with a "follow the sun" model.
·         Distributed teams expand access to new markets.
·         Acquisitions as a result of consolidation results in companies working together to integrate their businesses.
·         Expansion can aid innovation and thought leadership.
·         Telecommuting gives options for communicating with teams effectively.
·         Collaboration tools -- improved tools for distributed communications and server-based, multiuser tools for product development -- are removing barriers, and more teams view distributed collaboration as an alternative.
1.1       Handling Distributed Scrum Teams
·         Distributed teams increase the need for clear, timely communication between sites. You might be thinking of increases in complexity due to more time zones, language barriers, and cultural differences getting in the way.
·         Communication is the core issue among the distributed teams. Different time zones, conflicting working hours, cultural and language barriers impact communication and collaboration.
·         Investing ineffective enterprise tools for requirements repositories, Source Control management, build and deployment setup, defect tracking, and project management tools is essential.
·         Practicing Test Driven Development (TDD), Continuous Integration and Automation of Testing are recommended
·         Proper communication setup such as telephones and video conference are essential in a distributed setup.
1.2       Collaboration within a Sprint
·         Scrum Teams should follow continuous integration, test automation, and test-driven development practice to foster distributed collaboration during the sprint and help teams complete user stories within a sprint.

·         Documentation helps to overcome distance: Because of language barriers, distributed teams often need more written documentation than co-located teams.

·         Using the right tools: In a distributed environment, right tools and effective practices can help team members communicate more effectively.

·         Valuing the whole team: The Scrum Master should focus on an "us" versus a "them" attitude in the distributed team, due to more delays in communications and fewer opportunities to work together.

·         Transparency: Distributed Agile teams should use project management tools to identify tasks that are open, in progress, and completed so everyone is aware of the current status.

·         Dealing with defects: Distributed teams may want to consider creating a user story with a certain number of story points in the Sprint to deal with the problems, or they can set a priority for the maintenance tasks as per the customer log, or create a sub-team to focus only on handling these issues during the Sprint, or -- depending on the skill set of the technical support team -- make the necessary code changes.

·         Handling blockers during the sprint: In the large-scale enterprise transitioning to agile, the Scrum Master needs to hear from distributed Scrum team members who are facing blockers and dealing directly with inhibitors will help increase the velocity of the team over time, as well as the velocity of other teams as they transition to Scrum.

·         Responding to questions during the sprint: For enterprise product development, the Product Owner should look for ways to match representative stakeholders with the teams' working hours and to be available during that time as well.

·         Sharing time zone challenges: One approach to help manage such cases is to make sure that distributed teams in different time zones are fully self-sufficient and the team spreads the work to minimize dependencies.

·         Automation and Continuous Integration
o   Continuous integration.
o   Report any build failures to the team
o   Reduce the risk of integrating code.
o   Automated Test Cases.
o   Improve the efficiency of the team.
o   Builds can run at different frequencies.
o   Test automation.
·         Dedicated automation teams.

Test-driven development: Developers write unit tests, the small tests that fail first. Testers work with developers to ensure that any later tests do not repeat the work the developers have already done.

The Certified Scrum Master® is a Certification from Scrum Alliance. The Product Owner is the key member of the Scrum Team. The Scrum Master Certification Mumbai helps you gain a high degree of proficiency in the processes of the Scrum Methodology. It aims at providing you with an understanding of the Scrum framework, including team roles, activities, and artifacts. For More Information Call +91-8291749529 or visit, http://www.worldofagile.com.
Labels:
Location: India

Comments

Post a Comment

Popular posts from this blog

What are Important Roles in Scrum-Agile Teams?

The Primary Team roles in scrum are named as • Product Owner  • Scrum Master • Development Team Scrum Master, Product Owner, and Team are considered as people who are committed to the project while customers and executive management are considered as involved but not committed to the project. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.  Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of “Done” product ensure a potentially useful version of working product is always available. All the roles are based on the concept of “S...
1 comment
Read more

What is Definition of Done?

Done Criteria are a set of rules that are applicable to all User Stories. A clear definition of done is critical because it removes ambiguity from requirements and helps the team adhere to mandatory quality norms. This clear definition is used to create the Done Criteria when a Prioritized Product Backlog is prepared. Definition of done is crucial to a highly functioning Scrum team. The following are characteristics that you should look for in your team’s definition of done. Verifying that your team’s DoD meets these criteria will ensure that you are delivering features that are truly done, not only in terms of functionality but in terms of quality as well. DoD is a checklist of valuable activities required to produce software. Definition of done is a simple list of activities (writing code, coding comments, unit testing, integration testing, release notes, design documents, etc.) that add verifiable/demonstrable value to the product. Focusing on value-added step...
Post a Comment
Read more

Five Phases of Agile Project

There are FIVE phases that an Agile project goes thru. The FIVE phases are ·         Envision ·         Speculate ·         Explore ·         Adapt ·         Close Envision Phase : – This phase is to determine the product vision and project scope, the project community, and how the team will work together. The term ‘envision’ is a clear departure from traditional phase names such as initiate and plan, which while subtle, is also significant. This is because when envisioning you inadvertently accept a level of mishap and are therefore ready to make any necessary adjustments, in contrast to a set plan which has more rigorous connotations. The envision phase covers the ‘Who? What? And how?’ Speculation Phase:  Unlike planning, speculating esta...
Post a Comment
Read more