The Scrum Process Post 2020

AdaptDev “Agility Hour” · Beginner ·📰 AI News & Updates ·4y ago

Key Takeaways

Describes the Scrum process post 2020 update

Full Transcript

in this session we will consider the 11 elements that make up the process of scrum as described in the scrum framework first let's identify the roles in a scrum team the scrum master is the coach for the team and the organization in implementing scrum so that all the benefits of scrum may be gained through effective implementation the scrum master is a management role that manages the effective implementation and understanding of the scrum framework within the organization they also need to be considered a senior enough organizational role so that they are confident to discuss impediments at any level within the organization the product owner should own the product in an entrepreneurial manner providing the vision to the scrum team of the value the product should deliver through this vision the product owner maximizes the value of the work delivered by the developers through actively owning the product backlog as a living artifact they maximize the amount of work not done therefore you can consider the product owner as the value optimizer the developers is the term for those who carry out the work in a scrum team they are a collection of professionals who work to deliver a potentially releasable increment of done products at the end of each sprint next let's consider the three artifacts in scrum the product backlog is a living artifact describing the vision of the product through the product owner adding items to the backlog that will deliver the value expected from the product and the developers refining the backlog items so that they can technically be delivered in a sprint where items can be removed is no longer needed not likely to deliver the expected value or that this value can be delivered in another manner then the product owner should do so in order to maximize the value of the work not done the sprint backlog forms the plan of the items that the developers expect to deliver through the sprint this may be broken down and described as tasks they intend to complete in order to deliver each product backlog item or as tests that describe the work that must be completed so that each backlog item can be considered done the done increment is the accumulated increments of all sprints completed so far in order to deliver the product if you're at the end of sprint one then the done increment will be the output from only that sprint however if you're at sprint 11 then the down increment is the accumulated work of all proceeding sprints as well as the output from the newly completed sprint 11 which comprises the potentially shippable product every time the product owner releases the done increment to their customers this provides a feedback loop to the vision and therefore the product backlog based on the customer's reaction to the release now let's identify the events in scrum that connect the roles to the artifacts and build the feedback loops the first event that occurs within a sprint is the sprint planning this allows the scrum team to plan the work that will be undertaken during the current sprint in sprint planning a sprint goal will be identified and the developers along with the product owner will select items from the product backlog and place them in the sprint backlog in order to deliver the sprint goal the event in which the developers participate to synchronize their work is called the daily scrum this gives the developers an opportunity to inspect the work of the last 24 hours and adapt their plan for the next 24 hours the sprint review is an opportunity for the scrum team and its stakeholders to participate in the inspection of the work that has been produced to meet the sprint goal and how this progresses the development of the overall solution the outcome from the sprint review provides a feedback loop to both the product backlog and the choices made during sprint planning one thing you can be assured to have as an outcome from your sprint review is an updated product backlog even if it is agreed that the current order is correct the retrospective is the opportunity at the end of the sprint in which the scrum team can inspect its implementation of scrum as a process framework the interactions of the people within the team as well as any required skills in order to deliver the solution while reviewing these to consider opportunities for continuous improvement is also discussed this provides an improvement feedback loop for the scrum team which should take at least one continuous improvement goal into each sprint as a target to achieve the last event that we will list is a special event called the container event this is the actual sprint itself which has been termed as a container event because all activities of scrum occur within a sprint in the scrum framework there is no activities events or other actions that will be carried out outside of the actual sprint therefore the length of the sprint should be such that allows you to carry out all the work to deliver a done and complete increment of the product within this time box and that's been the 11 elements of scrum thank you very much for watching i hope you've enjoyed this video please remember to like share and subscribe and please check us out on facebook linkedin and twitter you

Original Description

The 11 basic elements of scrum described post the 2020 update to the Scrum Guide.
Watch on YouTube ↗ (saves to browser)
Sign in to unlock AI tutor explanation · ⚡30

Playlist

Uploads from AdaptDev “Agility Hour” · AdaptDev “Agility Hour” · 18 of 24

1 Why Scrum?
Why Scrum?
AdaptDev “Agility Hour”
2 Stacey Complexity Model Explained - Alasdair Macleod
Stacey Complexity Model Explained - Alasdair Macleod
AdaptDev “Agility Hour”
3 Get Scrum - The Scrum Process Explained
Get Scrum - The Scrum Process Explained
AdaptDev “Agility Hour”
4 The House of Scrum
The House of Scrum
AdaptDev “Agility Hour”
5 3 amigos - Complementary Practice in Agile
3 amigos - Complementary Practice in Agile
AdaptDev “Agility Hour”
6 Module 1 - Agile vs Waterfall
Module 1 - Agile vs Waterfall
AdaptDev “Agility Hour”
7 Emergence
Emergence
AdaptDev “Agility Hour”
8 Introduction to Scrum Mastery Online Course
Introduction to Scrum Mastery Online Course
AdaptDev “Agility Hour”
9 Acceptance Criteria vs Definition of Done | Thinking Agile
Acceptance Criteria vs Definition of Done | Thinking Agile
AdaptDev “Agility Hour”
10 Identifying and reducing bugs | Thinking Agile
Identifying and reducing bugs | Thinking Agile
AdaptDev “Agility Hour”
11 A Day in the life of a Scrum Master | Thinking Agile
A Day in the life of a Scrum Master | Thinking Agile
AdaptDev “Agility Hour”
12 Online tools for Story Mapping | Thinking Agile
Online tools for Story Mapping | Thinking Agile
AdaptDev “Agility Hour”
13 Cutting the User Story Cake | Thinking Agile
Cutting the User Story Cake | Thinking Agile
AdaptDev “Agility Hour”
14 Thinking Agile | Using Jira & Process Management tools
Thinking Agile | Using Jira & Process Management tools
AdaptDev “Agility Hour”
15 How to determine an items complexity | Thinking Agile
How to determine an items complexity | Thinking Agile
AdaptDev “Agility Hour”
16 How does a Scrum Team decide which items to work on? | Thinking Agile
How does a Scrum Team decide which items to work on? | Thinking Agile
AdaptDev “Agility Hour”
17 Remote Working for Scrum Masters & Can they continue post Covid-19? | Thinking Agile
Remote Working for Scrum Masters & Can they continue post Covid-19? | Thinking Agile
AdaptDev “Agility Hour”
The Scrum Process Post 2020
The Scrum Process Post 2020
AdaptDev “Agility Hour”
19 An Introduction to our PST Alasdair Macleod
An Introduction to our PST Alasdair Macleod
AdaptDev “Agility Hour”
20 Module 5   Success as a Scrum Master
Module 5 Success as a Scrum Master
AdaptDev “Agility Hour”
21 Module 5   Stances of the Scrum Master
Module 5 Stances of the Scrum Master
AdaptDev “Agility Hour”
22 Module 4   Reporting Progress
Module 4 Reporting Progress
AdaptDev “Agility Hour”
23 Module 1 - Agile Manifesto
Module 1 - Agile Manifesto
AdaptDev “Agility Hour”
24 Applying Professional Scrum
Applying Professional Scrum
AdaptDev “Agility Hour”

Related AI Lessons

You Are Not Behind. The World Is.
You're not behind, the world is still adapting to AI, and it's okay to take your time to learn and grow
Medium · AI
Career choice with the advent of AI - pure Computer Science or learn software with a background of core engineering area
Learn how to choose between a Computer Science and Engineering career path or combining programming with a core engineering background in the age of AI
Dev.to AI
The AI Hype Cycle: Calm Before the Next Breakthrough?
Understand the AI hype cycle to anticipate the next breakthrough and make informed decisions
Medium · Programming
AI won’t replace scientists. It will make the current model of science obsolete
AI is not replacing scientists, but rather making the current model of science obsolete, enabling new forms of discovery and collaboration
Medium · Data Science
Up next
Motorist saved by human chain | 9 News Australia
9 News Australia
Watch →