Distributed Teams & its Impact in Scrum Project

Distributed Teams & its Impact in Scrum Project

Agile principle states, “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”This is why Scrum recommends co-located teams. But with the changing business realities and globalization, co-located teams are becoming more and more difficult and are slowly being replaced with distributed teams.

You might ask, what do distributed teams bring to the organization? Global reach and distributed costs, more culturally inclusive team leads to understanding the market better, global acquisitions of other small businesses to assist the main organization etc. The possibilities are endless.

With this global reach and inflow of efficient resources, working with distributed teams has become an important part of a Scrum Master role. Of course, working with distributed teams has its own challenges, primary being communication. A culturally different team needs a different approach to communicate among each other. If everyone in the team understands one langague, it solves a lot of trouble otherwise language becomes a big impediment. Then there are different time zones, working hours, scheduling deliveries etc. These all can be managed with proper communication to the team that all of them are working towards a common goal.

Sprint planning meeting requires proper communication among team to arrive at a consensus as to how to proceed with the client’s requirements. Daily Scrum meetings need to happen at respective locations, the Scrum Master has to consolidate the data of different teams and find how the efficiency can be competitively maintained. If the communication is perfect and teams are working efficiently, the end sprint reviews helps consolidate and set things for retrospectives. Retrospectives help in analysing the sprint, what was good? What could have been done better? All of these help to make the team more efficient and fluid. Better coexistence among the teams leads to faster delivery of end product.

Training plays an important role in setting individual teams into Scrum teams. Collaboration among teams is the prime criterion that needs to be met for the teams to start delivering on the project. Self-organized teams are better in delivering products than teams trying to outshine each other. All these points lead to a better distributed team for global reach and faster end delivery while adhering to Scrum framework.

For more such interesting articles/blogs visit: https://www.dhirubhai.net/groups/6718717/

To know more interesting facts about Scrum and Agile, please join our free webinar on Scrum Fundamentals here: https://www.scrumstudy.com/classes/scrum-fundamentals-certification-training


要查看或添加评论,请登录

Sam Mishra的更多文章

  • Lean Six Sigma Methodology in Cyber Security Operations

    Lean Six Sigma Methodology in Cyber Security Operations

    In the swiftly changing digital environment, organizations face a constant worry – the looming threat of cyber security…

  • The Impact of Lean Six Sigma in Public Sector

    The Impact of Lean Six Sigma in Public Sector

    The adoption of Lean Six Sigma in the public sector has brought about significant improvements in performance…

  • Integration of Lean and Six Sigma

    Integration of Lean and Six Sigma

    Lean Manufacturing and Six Sigma methodologies are now commonly implemented in tandem, resulting in a fusion of their…

  • A brief Overview of The Initiate Phase in Scrum

    A brief Overview of The Initiate Phase in Scrum

    Initiate phase, as defined in A Guide to the Scrum Body of Knowledge (SBOK? Guide), is applicable to the following:…

  • Scrum in Programs and Portfolios

    Scrum in Programs and Portfolios

    When applying Scrum to manage projects within the context of a program or portfolio, it is strongly recommended that…

  • User Story Prioritization Methods in Scrum

    User Story Prioritization Methods in Scrum

    The key techniques used to prioritize the User Stories or requirements in the Prioritized Product Backlog, on the basis…

  • Business Justification and the Project Lifecycle

    Business Justification and the Project Lifecycle

    Business justification demonstrates the reasons for undertaking a project. It answers the question “Why is this project…

  • Sprint Retrospective Meeting

    Sprint Retrospective Meeting

    Retrospect Sprint In this process, the Scrum Master and Scrum Team meet to discuss the lessons learned throughout the…

  • How do we handle change requests in Scrum?

    How do we handle change requests in Scrum?

    Any change that arises in either the programs or portfolios may have a cascading effect on all dependent projects and…

  • Agile Myth: “Agile Means No Planning and No Documentation”

    Agile Myth: “Agile Means No Planning and No Documentation”

    It is widely known in the software development industry that Agile values “working software” over “extensive…

社区洞察

其他会员也浏览了