Related posts:
Scrum Framework in 10 Minutes Lyssa Adkins
The Scrum Framework (Scrum Academy clarifies Agile)|2021 Edi...
Scrum Framework
Locate out the basics of using Scrum. Unders...
What is Scrum?|Scrum under 3 mins
What is Scrum? In this vid...
Scrum 101 | Scrum for Dummies | Sprint | Product Backlog | Scrum Framework
The Scrum Technique - The Advantages and the Obstacles
Scrum Framework in 5 Minutes
YDS: What are the Principles of the Scrum Framework?
The Scrum Framework
Active instructors need to be able to in...
[Upgraded] Scrum Framework - How Scrum Works Today
#scrumfra...
The Scrum Framework : eLearning course - The big picture (lesson 1/19)
Agile Management - Start with Better Management
Felipe Luz
Awesome video! Short but packed with valuable information in a digestible way! Perfect to share with the team!
Szentkiralyi Pal KMCSSZ
Excellent overview!
Panagiotis Chatzipanos
Jeff, this is an awesome introduction…!!!
Highping1
Thanks for telling us about Scrum without bragging about how great it is and putting down Waterfall.😁
T G
when the timeframe is flexible, it is trully better than waterfall though
Highping1
@T G You ruined it!!! That’s just what I was talking about.
BTW scrum is only better in certain situations. It is worthless for manufacturing.
T G
@Highping1 I agree!
Mohamed Selim
Great video ♥️
Néstor Duarte
porque no traducen al español???
Scrum Inc.
https://www.linkedin.com/showcase/agile-education-by-scrum-inc.-espa%C3%B1ol/
Света вокруг света
thank you for video
Scrum Inc.
You are welcome
US R
What is backlog refinement
Scrum Inc.
See more here: https://www.scruminc.com/product-backlog-refinement/
Madhu Anandan
Can I use you content and give you credits in my presentation?
Scrum Inc.
Yes, kindly link to the source video, thanks!
Modupe Oladejo
This is simple, understandable and straight forward. Thank you!
Scrum Inc.
Glad you found it helpful:)
Linard Perez
THIS HELPED ME ON MY INTERVIEW!! THANK YOU SO MUCH!!
Scrum Inc.
Glad it helped!
Ree W
Great video! Simple and easy to understand! Thanks for posting!
Scrum Inc.
You’re welcome!
Na'il Salahu-Din
An Easy way to remember the key elements of SCRUM is 353..
The first 3 represents the 3 roles:
– Scrum Master
– Product Owner
– Team
There are 5 meetings which are called events and 3 artifacts that are produced in or help guide the events.
Product Owner owns the what or what the team is going to make. They create a product backlog which is a focused to do list on how the team will produce the product.
The team then examines the product backlog during Sprint planning, which is the very 1st event in SCRUM.
The team only pulls what they can finish in a set period of time from the backlog. The Sprint backlog is the shorter to do list from the original backlog.
Sprints are the “heartbeat” of SCRUM. Sprints last from 1-4 weeks, checking off the task on the Sprint backlog that the team pulled from the original backlog. Sprints are just long enough to produce a meaningful part of the product that could be released to the customers. Sprints should be short enough that the team can change course, if need be, based on feedback from the consumers or stakeholders.
Throughout the sprint the SCRUM Master coaches the team and product owners on SCRUM and facilitate all the events. The product owner and team join with the SCRUM Master daily for no longer than 15mins to check in on what daily task they executed for the previous day and what they will do on that day towards the Sprint goal. They also name any challenges that may be hindering them from completing the goal.
The next event is the Sprint Review in which the Product Owner ensures the right people (customers & stakeholders) are present to see the final product from the Sprint or the potentially shippable increment demonstrated.
The final event is the Sprint Retrospective. This event entails reflections on the process from the entire team naming what went well and what could have gone better. Leaving with an agreement to try something new that may boost production or make the process smoother.
Paul Wijntjes
A brilliant video, BUT with one major mistake. The Daily Scrum is for Developers. Most of the time SM and PO are not needed and should not be there. It is an opportunity for the Developers to organise themselves. When the SM and PO attend the Daily every day the sit in the way of this basic principle of self organisation. If you don’t agree: Read the Scrum Guide. When you fix this mistake I will recommend and use this video everywhere. For the rest: Great Work!