Skip to main content

Scrum Framework - 3 Roles In Agile Scrum - By Ankur Mistry

Today, we will learn Scrum Roles in Agile Scrum Framework.
There are three main roles in Agile Scrum Framework.
  1. Product Owner
  2. Scrum Master
  3. Development Team
Roles in Agile Scrum Framework
(Figure: Roles and responsibilities of a Scrum Team from The Professional ScrumMaster's Handbook by Stacia Viscardi)
Product Owner is the one who has product vision. He or she is the voice of the customer/stakeholders.
Responsibilities
  • Owns Product Backlog
  • Ensures product backlog is transparent, visible, and clear.
  • Closely works with Development Team and Scrum Master.
  • Available to the team to answer any issues or queries and provide feedback.
  • Has authority to cancel a sprint.
  • Accept/Reject development team's work.
  • Participates in Scrum events as needed.
Scrum Master is the person who is responsible for the Process and facilitates Scrum events as needed in the project.
Responsibilities - Service to Development Team
  • Teaches development team to be self-organized and collaborative.
  • Ensures that team will understand and follow the Scrum practice and rules.
  • Helps development team to reflect and improve as a team.
  • Resolves conflicts; acts as a mentor to the development team.
Service to Product Owner
  • Teaches Scrum process and theory to the Product Owner so that the owner can understand the rules.
  • Helps to create a product backlog.
  • Removes impedimentations or dependencies.
  • Helps to order/prioritize the product backlog to maximize the value.
  • Helps Product Owner to write clear user stories for Product Backlog.
Service to the Organization
  • Coaches organization on Scrum
  • Working with other Scrum Masters to increase the performance.
  • Creates a culture where teams can work on the incremental/empirical product development.
Development Team
Development Team is a team of professionals (Size 7 + or – 2) who is responsible for the working product or potentially shippable product at the end of each sprint.
Responsibilities
  • They are self-organized and know what the sprint goal is and what to do for achieving the same.
  • Cross-functional teamwork and collaboration
  • Owns Sprint backlog and responsible for the design and quality of the product.
  • Participates in Scrum Events.
  • Estimate items in the backlog.
  • Update Sprint Burndown chart.
  • Help in product backlog refinement.
Hope you like this article. Please let me know your feedback in the comment section. In the next articles, we will discuss three Scrum Artifacts and five Scrum Events.
Reference
  • https://www.scrumalliance.org/
  • http://staragile.com

Comments

Post a Comment

Popular posts from this blog

Agile Story Point Estimation Techniques - T-Shirt Sizing by - Ankur Mistry

In my previous articles, we have discussed  Agile Story Point Estimation  and  Agile Story Point Estimation Techniques - Planning Poker . In this article, we will learn Story Point Estimation using T-Shirt Size Technique. What is T-shirt sizing? T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. It's a relative Estimation Technique. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. The term originates from the way T-shirt sizes are indicated in the US. Rather than having T-shirts in sizes 4, 5, 6 etc, there are just a few sizes: Small (S), Medium (M), Large (L) and Extra Large (XL) and so on. With T-shirt measuring, the development team is made a request to evaluate whether they think a story is extra-small, small, medium, large, extra-large, or double extra-large. By expelling the numerical score, the development team is allow...
Post a Comment
Read more

User Story In Agile Scrum - By Ankur Mistry

In this article, we will learn what User Story is and how to write one. User Story plays a major role here. It is the part of the Agile process where instead of writing comprehensive requirements, we write a short description of a feature. As the  Agile Manifesto  says 'Working Software' Over 'Comprehensive Documents'. What is User Story? User Story is a short and simple description of the feature or requirements of the project. Generally, user stories are written on sticky notes or index cards as a user or role-based perspective. User Story Template As a < type of user or role >, I want < some goal > so that < some reason >. The template identifies 3 questions - "Who", "What", and "Why". If the team doesn't know these three answers, it means they don't understand the story, and if they don't understand the story, then it's difficult to split it well.   Reference:https://mazoea.wordpres...
Post a Comment
Read more

Visual Studio Team Services - Agile - Scrum Project Management Tools

Before starting this article let's understand what is Agile and Scrum.  What is Agile Agile is a  Method  of project management that is characterized by dividing module in to tasks and t asks into short phases of work and frequent reassessment and adaptation of plans. In other words, Agile is a Time Boxed incremental software development method.  What is Scrum Scrum is an incremental agile software development framework  (Agile Framework).   Agile Scrum Process in Short. Product Backlog:  A product owner creates a customer’s wish list and prioritized it and create backlog, called Product Backlog. Sprint Planning:  In this meeting team select small part or module from the Top Priority Wish List of Product Backlog and prepare a small task list. Setting Capacity and Sprint:  Team has to deliver the tasks in 2 weeks or 4 weeks sprint, here Scrum Master bind tasks with Time and User. Scrum Master’s role:  Is to make sure te...
Post a Comment
Read more