Search

Key Factors to Succeed at Managing Distributed Agile Teams

 Advanced communication and collaborative technologies have largely been responsible for the onset of globalization, giving organizations a competitive advantage over slow adopters. These technologies have allowed people to work almost anywhere, anytime, and on any device. This has contributed to the age of distributed teams and the virtual employee; professionals who deliver critical business value, but are not constrained by co-location requirements.The majority of Agile teams are distributed in some form or another. From my own personal experience, at least 70% of the Agile projects I worked in the last ten years have involved distributed teams. These include team members on another level of the building, down the road at another site, located in another city or even country.  There are some challenges with distributed teams that do need attention, such as problematic communications technology, language barriers, feelings of isolation, distractions at home, ineffective feedback and a lack of trust by managers. On the issue of trust, Daniel Cable, a professor of organizational psychology, believes that a lack of trust on behalf of managers is the greatest obstacle to successful remote teams.  However, another emerging issue is between the Agile purists who believe that Agile teams should be co-located in order to get the best results and Agile pragmatists who believe that the best self-organizing, cross-functional teams are the ones who create their own team from a global resource pool, regardless of location.Choosing the best one is situational, as there are a number of variables are at play. However, there are some advantages to both schools of thought: Advantages of co-located teamsAd-hoc team meetings are fast and easy to arrange.Facilitates osmotic communication; useful information that is overhead due to a  close proximity.Facilitates tacit knowledge; the stuff we know that isn't necessarily documented or taught.Faster feedback (answers, status, decisions).Low tech, high touch tools such as whiteboards and sticky notes that facilitate  knowledge sharing and create a bond with the team and project through human touch and interaction.Issues with technology can generally be resolved quicker.Faster (but not always smoother) team formation phases.There is a higher level of trust from management. Advantages of Agile distributed teamsIncreases the skill sets of teams by accessing a wider pool of global human resources.Reduces office space and various associated work items.Increased feedback due to the iterative nature of Agile.Reduces travel expenses.Teams can span time-zones, thus access up to 24-hour capacity.Can include members with disabilities and mobility restrictions.Higher levels of well-being.Flexible working arrangements foster an increased commitment to the company.Increased cultural diversity. Helping Agile distributed teams to succeedThere are a number of ways to get the best out of distributed teams. Digital tools such as video conferencing, Agile soft boards and collaboration platforms are just a few of the obvious enablers. Some good applications that I have used in the past include Zoom, Skype, Slack, Jira, and SharePoint. Also, adequate infrastructure such as computers and a reliable fast internet connection is another crucial enabler. I have witnessed several projects fail or underperform simply because internet connectivity and speed were severely limited. Another critical factor that is rarely considered is that of psychological health. If the mind is not in the right place, the greatest tools in the world are not going to make a distributed Agile team successful. Agile teams differ from more traditional project teams in that they are far more useful to being empowered, self-organized, flexible, innovative, collaborative, with a flatter management structure. When an Agile team is distributed, it presents added complexity with regard to the psychological health that can impact these Agile team traits.In my MBA thesis, I investigated the well-being of home-based workers in the BPO industry and discovered that 27% expressed feelings of isolation, less team unity, and missed their work colleagues. Perhaps more disturbing was the lack of organizational support for this phenomenon. While this may not always affect distributed workers, such as ones located in remote serviced offices, the feeling of disconnection is still there. I used to work for Fujitsu out of a serviced office many years ago. The offices were very nice, clean, well serviced, but empty most of the time. The only people I came across were strangers from the company who would drop in to have a meeting or print out something. I distinctly recall the feeling that I was alone with a phone to call prospect clients; more strangers. I was in a distributed team of business development managers and received zero communication from anyone about how I was coping, only about how the sales numbers were going.So here are some of the critical success factors that helped me to reduce the negative psychological effects of Agile distributed teams:The Scrum Master, Product Owner or other Agile lead needs to touch base with the distributed worker or team at least once a day. Videoconferencing is the best method or a phone call at the very least. It only needs to be 5-10 minutes just to touch base and let the team know they have organizational support. This is aside from the daily stand-up, which should also use video conferencing to promote a feeling of togetherness.Now Me  This is my own name for a special weekly get-together derived from a NO Work MEeting. As the name suggests, this meeting is not about work at all. It is an opportunity to get together virtually, via video conferencing, to chat about anything the team wants to chat about.Virtual Coffee CupWhen regular meetings are scheduled in the head office or boardroom with a mix of co-located and distributed team members, I try and buy a custom coffee mug with the name of the distributed team member or members who are connecting remotely to the meeting. I actually fill up the coffee mug with their favorite beverage and place it on the table in view of the camera. This may seem like a simple thing, but you may be surprised just how inclusive people feel when they have been thought of as in that meeting room with everyone else. Remember Agile teams are equal members, so every effort should be made to make everyone feel equally appreciated.Counselling ServicesThis is where HR might need to step in and provide a service for distributed team members that feel isolated, frustrated, or even depressed. These issues can become serious. It is best to provide a service that is independent of the organization, but if that is not possible, HR needs trained and qualified personnel with regard to mental health and confidentiality.  360° Feedback Unfortunately, many performance assessments are only one way. With distributed Agile teams especially, there must be a 360° feedback on team performance, and that includes product owners, scrum masters, release managers etc. Agile distributed teams are becoming the new norm. To label these teams as the lesser counterparts of their co-located cousins would be premature, especially since technology can only get better before the disadvantages start outweighing the advantages. While there is naturally some loss of osmotic communication with distributed teams, it is more than compensated by a healthier, happier, culturally diverse team of members that are backed up by the latest in communication and collaborative technology, and an unlimited global human resource pool. 
Rated 4.5/5 based on 11 customer reviews

Key Factors to Succeed at Managing Distributed Agile Teams

4K
Key Factors to Succeed at Managing Distributed Agile Teams

 Advanced communication and collaborative technologies have largely been responsible for the onset of globalization, giving organizations a competitive advantage over slow adopters. These technologies have allowed people to work almost anywhere, anytime, and on any device. This has contributed to the age of distributed teams and the virtual employee; professionals who deliver critical business value, but are not constrained by co-location requirements.

The majority of Agile teams are distributed in some form or another. From my own personal experience, at least 70% of the Agile projects I worked in the last ten years have involved distributed teams. These include team members on another level of the building, down the road at another site, located in another city or even country.
 

 There are some challenges with distributed teams that do need attention, such as problematic communications technology, language barriers, feelings of isolation, distractions at home, ineffective feedback and a lack of trust by managers. On the issue of trust, Daniel Cable, a professor of organizational psychology, believes that a lack of trust on behalf of managers is the greatest obstacle to successful remote teams. 

 However, another emerging issue is between the Agile purists who believe that Agile teams should be co-located in order to get the best results and Agile pragmatists who believe that the best self-organizing, cross-functional teams are the ones who create their own team from a global resource pool, regardless of location.

Choosing the best one is situational, as there are a number of variables are at play. However, there are some advantages to both schools of thought: 

Advantages of co-located teams

  • Ad-hoc team meetings are fast and easy to arrange.
  • Facilitates osmotic communication; useful information that is overhead due to a  close proximity.
  • Facilitates tacit knowledge; the stuff we know that isn't necessarily documented or taught.
  • Faster feedback (answers, status, decisions).
  • Low tech, high touch tools such as whiteboards and sticky notes that facilitate  knowledge sharing and create a bond with the team and project through human touch and interaction.
  • Issues with technology can generally be resolved quicker.
  • Faster (but not always smoother) team formation phases.
  • There is a higher level of trust from management.

 Advantages of Agile distributed teams

  • Increases the skill sets of teams by accessing a wider pool of global human resources.
  • Reduces office space and various associated work items.
  • Increased feedback due to the iterative nature of Agile.
  • Reduces travel expenses.
  • Teams can span time-zones, thus access up to 24-hour capacity.
  • Can include members with disabilities and mobility restrictions.
  • Higher levels of well-being.
  • Flexible working arrangements foster an increased commitment to the company.
  • Increased cultural diversity.

 Helping Agile distributed teams to succeed

There are a number of ways to get the best out of distributed teams. Digital tools such as video conferencing, Agile soft boards and collaboration platforms are just a few of the obvious enablers. Some good applications that I have used in the past include Zoom, Skype, Slack, Jira, and SharePoint. Also, adequate infrastructure such as computers and a reliable fast internet connection is another crucial enabler. I have witnessed several projects fail or underperform simply because internet connectivity and speed were severely limited.

Agile distributed teams


 Another critical factor that is rarely considered is that of psychological health. If the mind is not in the right place, the greatest tools in the world are not going to make a distributed Agile team successful. Agile teams differ from more traditional project teams in that they are far more useful to being empowered, self-organized, flexible, innovative, collaborative, with a flatter management structure. When an Agile team is distributed, it presents added complexity with regard to the psychological health that can impact these Agile team traits.

In my MBA thesis, I investigated the well-being of home-based workers in the BPO industry and discovered that 27% expressed feelings of isolation, less team unity, and missed their work colleagues. Perhaps more disturbing was the lack of organizational support for this phenomenon. While this may not always affect distributed workers, such as ones located in remote serviced offices, the feeling of disconnection is still there. I used to work for Fujitsu out of a serviced office many years ago. The offices were very nice, clean, well serviced, but empty most of the time. The only people I came across were strangers from the company who would drop in to have a meeting or print out something. I distinctly recall the feeling that I was alone with a phone to call prospect clients; more strangers. I was in a distributed team of business development managers and received zero communication from anyone about how I was coping, only about how the sales numbers were going.

So here are some of the critical success factors that helped me to reduce the negative psychological effects of Agile distributed teams:

5 key success factors for distributed agile teams


The Scrum Master, Product Owner or other Agile lead needs to touch base with the distributed worker or team at least once a day. Videoconferencing is the best method or a phone call at the very least. It only needs to be 5-10 minutes just to touch base and let the team know they have organizational support. This is aside from the daily stand-up, which should also use video conferencing to promote a feeling of togetherness.

Now Me 

 This is my own name for a special weekly get-together derived from a NO Work MEeting. As the name suggests, this meeting is not about work at all. It is an opportunity to get together virtually, via video conferencing, to chat about anything the team wants to chat about.

Virtual Coffee Cup

When regular meetings are scheduled in the head office or boardroom with a mix of co-located and distributed team members, I try and buy a custom coffee mug with the name of the distributed team member or members who are connecting remotely to the meeting. I actually fill up the coffee mug with their favorite beverage and place it on the table in view of the camera. This may seem like a simple thing, but you may be surprised just how inclusive people feel when they have been thought of as in that meeting room with everyone else. Remember Agile teams are equal members, so every effort should be made to make everyone feel equally appreciated.

Counselling Services

This is where HR might need to step in and provide a service for distributed team members that feel isolated, frustrated, or even depressed. These issues can become serious. It is best to provide a service that is independent of the organization, but if that is not possible, HR needs trained and qualified personnel with regard to mental health and confidentiality.  

360° Feedback 

Unfortunately, many performance assessments are only one way. With distributed Agile teams especially, there must be a 360° feedback on team performance, and that includes product owners, scrum masters, release managers etc.

 Agile distributed teams are becoming the new norm. To label these teams as the lesser counterparts of their co-located cousins would be premature, especially since technology can only get better before the disadvantages start outweighing the advantages. While there is naturally some loss of osmotic communication with distributed teams, it is more than compensated by a healthier, happier, culturally diverse team of members that are backed up by the latest in communication and collaborative technology, and an unlimited global human resource pool. 

Sante

Sante Vergini

Blog Author

Sante is a senior management professional with 30 years experience in IT, project management and sales. He holds numerous qualifications in project management and Agile including PMP, PMI-ACP and PSM. He has a Master of Business Administration and a Master of Arts in Management and Strategic Leadership. Currently, he is completing a PhD in project management frameworks within the education system.

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Why Do Scrum Masters Get Paid so Much?

Is Scrum Master the best paying job? Do Scrum Masters are highly paid individuals? Though these two questions look very simple in asking but are very difficult in answering. Let’s dig in and find out the salary range that Scrum Masters are earning.  The survey conducted by ‘Age of Product’ (Stephen Wolpers and Sumit Mehta) in 2017, included Scrum Masters from 13 countries around the world. The salary of a Certified Scrum Master varies from country to country. Collated below are the salary ranges in USD for three important countries:US: 100,001 – 125,000UK: 60,001 - 70,000India: 20,001 – 30,000The monthly income of a Certified Scrum Master can be listed as follows-US: 8333 – 10416UK: 5000 – 5833India: 1667 - 2500The weekly income of a Certified Scrum Master, assuming 52 weeks for a year, the certified scrum master makes the following salary (in USD):US: 1923 – 2403UK: 1154 – 1346India: 384 - 577The hourly salary of Certified Scrum Master (CSM) makes the following(in USD):US: 48 – 60UK: 29 – 34India: 9.6 – 14Note: The figures mentioned here are in USD. Additional compensations for this job The certified scrum master can get additional compensations if he/she can take up a training for the community or get further certified in the line of his/her career. Salaries by company Here are some of the average salaries paid by the top companies to the certified Scrum Masters:TCS: 11,11,500/yearIBM: 16,07,000/yearAmdocs: 14,00,000/yearJP Morgan: 16,52,000/yearPhilips: 19,96,000/yearWhy do scrum masters get paid so much?According to Glassdoor, it is one of the 25 highest paying jobs in America.In an era in which software is constantly being updated and flying out the door, the ability to keep everyone connected and communicating, face to face if possible, is critical. A breakdown in communications leads to a breakdown in software. And a breakdown in software leads to a breakdown of the business.As companies are moving more to Agile, they have realized that scrum master is the core and important role in making the team productive, self -organized and follow the practices of Agile diligently.Job Description for certified scrum masterBelow are the on-job responsibilities of the Certified Scrum Master (CSM):Essential Duties:Guiding the team and organization on how to use Agile/Scrum practices and values to delight customers.Guiding the team on how to get the most of out of self-organization.Guiding the team on self-organizing to fill in the intentional gaps left in the Agile/Scrum frameworks.Assessing the Scrum Maturity of the team and organization and coaching the team to higher levels of maturity, at a pace that is sustainable and comfortable for the team and organization.Removing impediments or guiding the team to remove impediments by finding the right personnel to remove the impediment.Building a trusting and safe environment where problems can be raised without fear of blame, retribution, or being judged, with an emphasis on healing and problem-solving.Facilitating getting the work done without coercion, assigning, or dictating the work.Facilitating discussion, decision making, and conflict resolution.Assisting with internal and external communication, improving transparency, and radiating information.Supporting and educating the Product Owner, especially on grooming and maintaining the product backlog.Providing all support to the team using a servant leadership style whenever possible, and leading by example.Required Skills/Experience:Experience in playing the Scrum Master role for at least one year for a software development team that was diligently applying Scrum principles, practices, and theory.  (Adjust based on your necessity)Good skills and knowledge of servant leadership, facilitation, situational awareness, conflict resolution, continual improvement, empowerment, and increasing transparency.Knowledge of various well-documented patterns and techniques for filling in the intentional gaps left in the Scrum approach(example: numerous Burndown technologies, various Retrospective formats, handling bugs, etc.).Preferred Skills/Experience (Any of these is a plus):Experience is playing the Scrum Master role for at least two years for a software development team that was diligently applying Scrum principles, practices, and theory. (Adjust based on your necessity)Knowledge of other Agile approaches: XP, Kanban, Crystal, FDD, etc.Awareness and experience with widely successful Agile techniques: User Stories, ATDD, TDD, Continuous Integration, Continuous Testing, Pairing, Automated Testing, Agile Games.Applicable knowledge of the technologies used by the team.The experience in applying a wide variety of well-documented patterns and techniques for filling in the intentional gaps left in the Scrum approach (example: various Burndown technologies, many Retrospective formats, handling bugs, etc.).Excellent communication and mentoring skills.Tasks of the Certified Scrum MasterHelping the Development Team to create high-value productsCoaching the Development Team in self-organization and cross-functionalityRemoving impediments to the Development Team’s progressFacilitating Scrum events as requested or neededCoaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understoodEnsuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possibleFinding techniques for effective Product Backlog managementHelping the Scrum Team understand the need for clear and concise Product Backlog itemsUnderstanding product planning in an empirical environmentEnsuring the Product Owner knows how to arrange the Product Backlog to maximize the valueFacilitating Scrum events as requested or neededCompanies that prefer Certified Scrum MasterAccording to the Scrum Guides, “Scrum has been adopted by a vast amount of software development companies around the world.” Scrum has been used in education, manufacturing, marketing, operations, and other fields. If you have the skills in dealing with conflicts and you are an experienced facilitator, then following are the top companies in the world that hire the skilled Scrum Masters like you. According to the latest data on Glassdoor, the top companies preferring Scrum Master are:Answer Financial Inc. – Encino, CAPegasystems – Cambridge, MADonnelley Financial Solutions – Glen Mills, PAIntraEdge – Phoenix, AZWipro Limited, BengaluruZensar Technologies Limited, HyderabadJP Morgan Chase, HyderabadBarclays – PuneOrange, MumbaiFiserv – Pune, and many moreIt is more surprising that the Scrum Master salaries have increased in such a short span of time. Moreover, being a Scrum Master is not an easy role as it requires more of a servant leadership skills. So, the aim of the Scrum Master is always to finish-up the project in time without compromising the quality. Climb-up the ladder of Scrum with Scrum interview questions and answers! Find here.
Rated 4.5/5 based on 1 customer reviews
9669
Why Do Scrum Masters Get Paid so Much?

Is Scrum Master the best paying job? Do Scrum Mast... Read More

SAFe® Agilist Certification Vs PMI-ACP®: Which Certification Should You Choose?

The competition for jobs is getting tough in today’s world. Whether you are a job seeker, corporate employee, or a consultant, you should keep your skills up to date in a fast-paced, online world. Agile has become the standard of project management very fast in today’s world, specifically in the IT and service field. Most of the project management professionals have adopted Agile techniques, tools, and concepts to deliver the projects successfully that has never been seen before.If you want to make a career in Agile or want to make a career shift then Agile certification can be an added advantage. You might be in confusion as to which certification you should do, as there are different types of Agile certifications available. SAFe® Agilist and PMI-ACP® are the two most in-demand IT certifications today that will increase your career growth and salary.  In this post, we will discuss both the certifications and help to choose a career that best suits you.SAFe® AgilistLarger organizations are struggling with Agile, especially the well-established enterprises who are trying to adopt Agile and shift their way of doing things. SAFe® is one such example that provides best practices for adopting Agile at an organizational level and SAFe® certification covers every aspect of Agile from architecture, governance, funding, integration, and roles. Holding a SAFe® certification proves your proficiency and hands-on experience and shows your knowledge and skills in real-time implementations.SAFe® Agilist could be a perfect choice for you if you want to be part of different teams in the adoption of SAFe® and willing to be part of enterprise Agile. Scaled Agile is something different to standard Agile knowledge which is required for Agile change agents, managers, and executives for leading a lean-agile change initiative in large-scale enterprises. This is also essential for those executives who have already implemented Agile principles and practices at small-scale enterprises and now want to take it to the next level.Leaders of Lean-Agile change initiative can learn how to build a Lean-Agile Mindset and implement the SAFe® principles and practices to support Agile Teams, Program Portfolio Management, and Teams from this SAFe® 4 Agilist (SA) course. SAFe® Agilist certification demonstrates your efficiency of leading the Scaled Agile Framework adoption in an enterprise context.PMI-ACPPMI-ACP® certification could be an ideal choice for those who have been applying Agile values and principles in their day-to-day project work and who want to shift to a leadership role. To apply for  the PMI-ACP® certification, applicants must have at least 2,000 hours of working experience on project teams and 1,500 hours of working experience with Agile methodologies or on Agile project teams. Applicants should also complete 21 hours of Agile training and need to pass the exam.The PMI-ACP® is close to the mid-level CSP that is offered by the Scrum Alliance. Enterprises that are shifting to an Agile context and applying different Agile techniques are more interested in recruiting individuals with PMI-ACP® certification.PMI-ACP® could be a right choice if your enterprise is looking forward to adopting Agile framework in order to achieve high-end project goals. It not only covers Scrum framework but also includes XP, Kanban, Lean, and other frameworks. The PMI-ACP® certification exam is more difficult when compared to the basic Scrum Master certifications and individuals must take online or classroom training before going to attempt the exam.Let’s see the key differences between SAFe® Agilist and PMI-ACP®:It is important to look at the career opportunities before selecting the particular course. Think of various factors such as job security, responsibility, stress, income, and other benefits while choosing a profession.Just choosing a certification that is best for you doesn’t lead to the success you deserve. Choosing the best training provider will have a huge impact on the effectiveness of a course. Compare course outlines of different institutes and find the best training provider that will guide you in the right direction of the particular course chosen. You can also visit the institutes and attend some of the demo sessions to understand their approach to training. KnowledgeHut is a Registered Education Provider and offers both SAFe® Agilist and PMI-ACP® training classes across the country by experts who have years of industry experience.
Rated 4.5/5 based on 25 customer reviews
7068
SAFe® Agilist Certification Vs PMI-ACP®: Which C...

The competition for jobs is getting tough in today... Read More

Difference Between Agile and Scrum

Agile describes a set of guiding principles that uses iterative approach for software development, while Scrum is a specific set of rules that are to be followed while practicing the Agile software development. Agile Agile management represents various o software-development methodologies that have been influenced by iterative and incremental development, which includes Extreme Programming (XP), Rational Unified Process (RUP), Scrum, and others. Agile process or methods provide an environment where there is constant evolution in requirements and evolution as a result of collaboration between self-organising cross-functional teams. Agile methodologies foster a disciplined project-management approach that encourages a set of best practices, allowing a rapid delivery of high-quality software and enhancing a business approach, which aligns development with the customer needs. The Agile methodologies stand in contrast to the traditional waterfall methodology, where all the requirements are initially analysed and documented before the development begins. While in Agile approach, requirements are like the actual software-development advances within each iteration. This approach provides flexibility in accommodating changes in the requirements and priorities of the business. The Agile development process aligns with the concepts of Agile Manifesto. Also known as Manifesto for Agile Software Development, the Agile Manifesto is a formal declaration of 4 key values and 12 principles supporting an iterative approach to software development. The Agile development methodology enables assessment of project direction throughout the development lifecycle. This is achieved through regular iterations, and when revaluation is done at every iteration, it greatly reduces the development costs and time. Agile helps the companies to build the right product. Benefits of Agile include as follows: • Benefits the Customers In the traditional waterfall model, the high-value features are developed and delivered in longer cycles compared to the Agile approach, which enables delivery within short cycles. This enables the vendors to be more responsive to the development requests of the customers. • Benefits the Vendors Adopting Agile benefits the vendors by having an improved customer satisfaction and customer retention, leading to more customer contacts through positive references. The Agile allows the vendor’s focus to be on the development effort of high-value features, decrease the overheads, and improve efficiency. • Quality With Agile development, there is a regular inspection of the working product, with testing integrated at every iteration, as it develops throughout the lifecycle. This in turn retains the quality of the product and also allows the product owner to make necessary adjustments whenever a quality issue arises. • Visibility Agile methodology is a collaborative approach that encourages active user participation throughout the product development. This gives an exceptional and clear visibility of the project’s progress and product development to the stakeholders. • Cost Control Agile development process has fixed timescale where the requirements emerge and evolve as the project progresses and the product is developed. This enables a fixed budget. • Risk Management In Agile methodology, small incremental releases are made visible to the product owner throughout the development cycle, which helps identify issues at an early stage, and it makes easier to respond to change, if any. Agile development ensures clear visibility, which allows necessary decisions to be taken at the earliest possible opportunity. Scrum Scrum, on the other hand, is a subset of Agile. A Scrum is a simple and flexible Agile methodology for software development. The Scrum is not a technique or a process but a lightweight and simple framework to address complex problems of a project and deliver a high-value product creatively. The major distinguishing attributes of Scrum are as follows: • Simplicity The development in Scrum is done in sprints, which are 1, 2, and 3 weeks in length. The Scrum team consists of: 1. Product Owner: The major responsibility of the product owner is to maximize the value of the product and work of the development team. Additional duties include managing the product catalogue. 2. Scrum Master: The development team consists of self-organising professionals who turn the product catalogue into product increment at the end of each sprint. 3. Development Team: The Scrum Masters make sure that the Scrum team is abiding by the Scrum theory and its rules. • Flexibility In the traditional waterfall model, when the business and technical requirements are documented and detailed, it results in endless documentation. The Scrum makes use of user stories to describe the functions needed to be developed. A tool called Pivotal Tracker is used to store these user stories in a backlog. If a change needs to be made or a need arises to add to the user stories, in that case the team can adjust as early as the next sprint. This allows the business to change their minds and the development team to be flexible enough to adjust to those changes. The ability to accommodate change is a powerful attribute of the Scrum methodology. • Communication and Collaboration In Scrum methodology, the communication between business users takes place on a daily/weekly basis according to the sprint schedule. This close communication and collaboration is a crucial factor, promoting the success of the Scrum methodology. The Scrum team achieves collaboration in following ways: 1. The Product Owner, the Scrum Master, and the development team work closely on a daily basis. 2. Sprint-planning meetings are conducted, which allows the development team to organise its work based on the knowledge gathered from the business priorities. 3. Conducting daily scrum meetings where the development team can account for the work completed, its future prospects, and deal with issues if any. 4. Conducting sprint reviews allows the team members to evaluate their former work by recommending better practices with every sprint. There are more details on Agile & scum differences
Rated 4.0/5 based on 8 customer reviews
2235
Difference Between Agile and Scrum

Agile describes a set of guiding principles that u... Read More

Useful links