{"id":2673,"date":"2021-09-13T11:20:27","date_gmt":"2021-09-13T08:20:27","guid":{"rendered":"https:\/\/besoftwares.com\/en\/?p=2673"},"modified":"2024-01-24T18:07:15","modified_gmt":"2024-01-24T15:07:15","slug":"understanding-agile-methodology-and-scrum-team-roles","status":"publish","type":"post","link":"https:\/\/besoftwares.com\/en\/understanding-agile-methodology-and-scrum-team-roles\/","title":{"rendered":"Understanding Agile Methodology and Scrum Team Roles"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"2673\" class=\"elementor elementor-2673\" data-elementor-post-type=\"post\">\n\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-0ad0c2c elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"0ad0c2c\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-82104a9\" data-id=\"82104a9\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-b88bb66 elementor-widget elementor-widget-wp-widget-text\" data-id=\"b88bb66\" data-element_type=\"widget\" data-widget_type=\"wp-widget-text.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t<div class=\"textwidget\"><h1><strong>Understanding Agile Methodology and Scrum Team Roles<\/strong><\/h1>\n<p>To better understand what Agile methodology is based on, we&#8217;ll start with a definition that we hope will be understandable to everyone.<\/p>\n<p>Agile methodology is a way of managing a project by breaking it down into multiple stages. It involves constant collaboration with stakeholders and continuous improvement at each stage. Once work begins, teams go through a process of planning, execution, and evaluation.<\/p>\n<p>Agile development is an approach to product (software) development in which requirements and solutions evolve through the collaborative effort of self-organizing teams and stakeholders.<\/p>\n<h1><strong>Roles in Scrum Team<\/strong><\/h1>\n<h2><strong>A. Product Owner, a Key Element<\/strong><\/h2>\n<p>Often, the product owner represents the stakeholders of the respective product and the voice of the end-user.<\/p>\n<p>A Scrum team should have a single product owner, who should not be confused with the Scrum master. The product owner focuses on the product&#8217;s development, closely liaising with stakeholders and the development team. They should not dictate how the team reaches a technical solution but seek consensus among team members.<\/p>\n<p>This role is crucial and often requires a deep understanding of both business and developers in the Scrum team. Therefore, a good product owner needs to communicate what is needed, ask why it is needed, and convey the message to all stakeholders, including the delivery team, using necessary technical language.<\/p>\n<p>Here are some communication tasks of the product owner to stakeholders:<\/p>\n<ul>\n<li>Organize additional meetings to present the solution to stakeholders who were not present at the sprint review;<\/li>\n<li>Define and announce releases;<\/li>\n<li>Share progress during meetings;<\/li>\n<li>Share RAID (risks, assumptions, issues, and dependencies) with stakeholders;<\/li>\n<li>Negotiate priorities, goals, funding, and schedule.<\/li>\n<\/ul>\n<h2><strong>B. Development Team<\/strong><\/h2>\n<p>The development team is responsible for delivering a potentially shippable product at the end of each sprint. The sprint goal represents a brief description of what the team needs to deliver, and it is important for both the team itself and stakeholders.<\/p>\n<p>A development team is self-organizing, and any interaction from outside the team is managed by the Scrum master (who protects and manages the team) or the product owner (who has regular interactions with all stakeholders).<\/p>\n<h2><strong>C. Scrum Master<\/strong><\/h2>\n<p>The Scrum Master is a facilitator and is responsible for removing impediments in the team&#8217;s way to achieve product goals. The Scrum Master is not a traditional team leader or project manager but acts as a buffer between the team and any negative influence that could distract them.<\/p>\n<p>The Scrum Master ensures adherence to the Scrum framework and ensures that the team follows the agreed-upon processes within Scrum, often facilitating key sections and encouraging the team to improve.<\/p>\n<p>Responsibilities of a Scrum Master include the following actions:<\/p>\n<ul>\n<li>Help the team determine the definition of the done product with the contribution of stakeholders;<\/li>\n<li>Train the team in Scrum principles to deliver high-quality features for the product;<\/li>\n<li>Promote self-organization within the team;<\/li>\n<li>Help the team remove obstacles to progress, whether they are internal or external;<\/li>\n<li>Educate stakeholders about Agile or Scrum.<\/li>\n<\/ul>\n<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-f3e265a elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"f3e265a\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-fdc3ba6\" data-id=\"fdc3ba6\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-ec7237c elementor-widget elementor-widget-image\" data-id=\"ec7237c\" data-element_type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.20.0 - 26-03-2024 *\/\n.elementor-widget-image{text-align:center}.elementor-widget-image a{display:inline-block}.elementor-widget-image a img[src$=\".svg\"]{width:48px}.elementor-widget-image img{vertical-align:middle;display:inline-block}<\/style>\t\t\t\t\t\t\t\t\t\t<img fetchpriority=\"high\" decoding=\"async\" width=\"2305\" height=\"2560\" src=\"https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-scaled.jpg\" class=\"attachment-full size-full wp-image-2688\" alt=\"\" srcset=\"https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-scaled.jpg 2305w, https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-270x300.jpg 270w, https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-922x1024.jpg 922w, https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-768x853.jpg 768w, https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-1383x1536.jpg 1383w, https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-1844x2048.jpg 1844w, https:\/\/besoftwares.com\/en\/wp-content\/uploads\/2021\/09\/Echipa-Scrum-Agile-662x735.jpg 662w\" sizes=\"(max-width: 2305px) 100vw, 2305px\" \/>\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":2387,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[24,38,44,43,25],"class_list":["post-2673","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-agile-methodology","tag-mobile-development","tag-scrum-team","tag-software","tag-web-dev"],"_links":{"self":[{"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/posts\/2673","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/comments?post=2673"}],"version-history":[{"count":21,"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/posts\/2673\/revisions"}],"predecessor-version":[{"id":4309,"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/posts\/2673\/revisions\/4309"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/media\/2387"}],"wp:attachment":[{"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/media?parent=2673"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/categories?post=2673"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/besoftwares.com\/en\/wp-json\/wp\/v2\/tags?post=2673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}