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

The Service Value System - Continual improvement | ITIL V4 Certification

Continual Improvement Continual improvement takes place in all areas of the organization and at all levels, from strategic to operational. When provisioning a service we should always keep continual improvement in mind, and should always be looking for opportunities to improve. To support continual improvement at all levels, the ITIL® SVS includes: ITIL® Continual Improvement Model provides organizations with a structured approach to implementing improvements Improve Service Value Chain Activity Continual Improvement Practice Continual Improvement Model Continual Improvement Model can be used as a high-level guide to support improvement initiatives.  The model supports an iterative approach to improvement, dividing work into manageable pieces with separate goals that can be achieved incrementally. The scope and details of each step of the model will vary significantly based on the subject and the type of improvement The steps of this model do not need to be carried out in a linear ...
Read more

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...
Post a Comment
Read more

What is ITIL?

The term ITIL means "Information Technology Infrastructure Library". ITIL is the most popular and widely accepted approach to manage IT Service(ITSM). ITIL has been adopted by many organizations as the framework to manage their IT service. There are millions of practitioners worldwide with ITIL skills and capabilities. IT is important to keep in mind that ITIL is a set of best practices and not a standard, so organizations are free to adopt ITIL framework as is applicable or valuable to them. Advantages of adopting ITIL for your organization are immense. Therefore, all scale and size (Small , medium, Large) organizations all over the world use ITIL to help them improve the value of their services. The few important benefits of adopting ITIL are:  ITIL creates stronger alignment between IT and the business Improves service delivery and customer satisfaction Reduces costs with improved use of resources Provides Greater visibility of IT costs and assets A Brief History of ITIL: ...
Read more