Scrum in 5 minutes from Professional Scrum Trainer | Scrum.org | Agile
ฝัง
- เผยแพร่เมื่อ 27 มิ.ย. 2024
- UPDATE: The burn-down charts are mentioned in the Scrum Guide as an example of a practice that can be used.
A visual professional overview of the Scrum framework from a Scrum.org trainer walking you through every step of the Sprint.
In this video I talked about:
✅ How Agile and Scrum are related
✅ What is included in Scrum
✅ How to run a Sprint
✅ What is NOT part of Scrum
◾◾◾◾◾
Resources mentioned:
📕 Scrum Master Startup Guide: store.scrummastered.com/produ...
🎥 That's NOT how you measure velocity - Velocity is a made-up number: • That's NOT how you mea...
🎥 Best way to run the Daily Scrum: • Best way to run the Da...
🎥 Useful graphs metrics for Scrum Teams | Jira Reports: • Useful graphs metrics ...
◾◾◾◾◾
MORE Resources:
🎥 Backlog Refinement - How and Why: • Backlog Refinement - H...
🎥 The Definition of Ready is not something you must have. It’s not similar to the Definition of Done that is actually mandatory to have. The Definition of Ready can be a good practice to use, but it is not a required one, and in fact if used incorrectly can be extremely damaging.
◾ ◾ ◾ ◾ ◾
📩 Subscribe to my newsletter to get updates on new stuff and special offers: scrummastered.com/free-downlo...
📚 BUY the essential Scrum Master tools: shop.scrummastered.com/
◾ ◾ ◾ ◾ ◾
✨ MY FAVORITE TOOLS ✨
Use my referral links to get some sweet bonuses
⚪ My digital notepad --- Get $40 off remarkable.com/referral/X55X-...
⚪ Try Figma for free 👉 --- bit.ly/smedfigma
⚪ My electric standing desk --- Get $30 off : share.flexispot.com/x/Vqw7rR
⚪ My office chair --- secretlabcanada.refr.cc/daryab
⚪ My business pen --- bastionboltactionpen.com/?rfs...
⚪ Loom --- loom.grsm.io/uy4artv49x2l
◾ ◾ ◾ ◾ ◾
☕ Support me - buy me a coffee: www.buymeacoffee.com/scrummas...
👋 Follow me and ScrumMastered on social media:
LinkedIn: / dariabagina
LinkedIn Company: / scrummastered
Instagram: / scrummastered
Facebook: / scrummastered
Twitter: / bescrummastered
📖 Check out MORE COOL THINGS at scrummastered.com/
✅ SUBSCRIBE to this TH-cam channel: / scrummastered
❗ DISCLAIMER
If you are using my affiliate links I will make a small commission on the sales made. This has no additional cost to you.
Chapters
0:00 Introduction
0:22 Scrum and Agile definition
0:49 What is included in Scrum?
1:28 Visual Scrum overview
1:53 Product Backlog
2:22 Sprint Planning
3:16 What Developers do
4:02 Sprint Review
4:41 Sprint Retrospective
4:59 What does Scrum Master do
5:59 Practices that are NOT Scrum
6:16 Story points
6:26 3 questions in the Daily Scrum
6:42 Burndown charts, Scrum & Kanban Boards
7:02 Backlog Refinement meeting
7:24 Definition of Ready
8:10 Conclusion
📖 If you are looking for guidance on how to implement Scrum in your team, check out my guides, especially, the Scrum Master Startup Guide (store.scrummastered.com/products/scrum-master-startup-guide) and the New Product Owner Guide (store.scrummastered.com/products/new-product-owner-guide) as they cover the key parts of Scrum implementation.
📩 Subscribe to my newsletter to get updates on new stuff and special offers:
scrummastered.com/free-downloads/
By far, one of the best breakdown of the framework.!.
Well done.!.
Thank you for watching!
Well done, Daria. Thank you for a refresher 👍🏾
My pleasure 😊
SO clear👏 ! Thanks for this content 🔝!
Glad you liked it!
The best video about Scrum so far!
@rostislavpodgorniy3974, thank you, I'm glad it was helpful :)
No nonsense content..Really cool explanation.Thanks😃
Glad it was helpful!
Hello Daria, I LOVED this refresher video! Very much appreciated! And, I LOVED your drawing abilities: you are very good at it!
BTW, I agree with you that Scrum (and other (meta)frameworks) are under the agile umbrella. In my opinion, for what it values, even if the agile manifesto is born after the Scrum framework, nothing forbids that the Scrum (and Kanban and...) can be taken under it. Simply, before the agile manifesto there wasn't an umbrella (everyone stays under the rain :D), after that we had a safe house where common characteristics to all the (metaframeworks) are grouped, made transparent and available.
Thanks again for this great content!
Cheers, Alessandro
Thank you for watching!
I wish I was able to create those amazing visual charts some people can make while attending a talk at a conference. Those are some real skills!
Love the rain metaphor :)
Thank you ❤. We will form new teams at my company soon. And I want to try to focus on scrum first and then implement complementary practices piece by piece. Scrum doesn‘t have the highest reputation among the Devs 😢, probably due to the overload of the complementary practices 🙈.
So it is great that you mentioned the difference between scrum and complementary practices ❤. Lets see what my boss says, when I tell her I might not use story points, for the first couple of sprints 😅. But what is the point without reference stories and velocity will be impacted by teambuilding and much more.
Yes, the "hate for Scrum" is usually associated with one of the two things: 1 - incorrect implementation of Scrum focused on irrelevant practices; or 2 - toxic people.
Great explanation... So planning is on day 1. When would you recommend the refinement call... A week after planning?
It usually makes sense to have the Backlog refinement a few days after the start and a few days before the end. That allows you to prepare for the upcoming sprint, but also doesn't interrupt regular sprint meetings.
🥰🥰🥰🥰🥰🥰🥰
Thank you!
I am newly certified SM coming from medical field. I am working with a team who is new to Scrum but I am so lost. I realized the course I took didn't really help me understand my actual role. :(
Hello, your feeling it's perfectly normal. The course(s) give you the understanding of the theory, the practice will allow you to use it, to experiment with it, to grow with it. As with almost everything else, you have to make your hands dirty to start to really know a topic and to really apply techniques, theories and so on.
I warn you: it will be hard, sometimes painful, sometimes very satisfing... the usual :D
It's 5 years that I try to be a decent scrum master: sometimes I'm good, sometimes I'm bad, often I struggle, sometimes I ask myself if it is the right work for me, sometimes I'm very pleased what we (as a team) do... it's a neverending journey.
My suggestions (based on my experience) are:
1) never stop to learn: read official material, follow trainers like Daria and look at their content! But don't become overwhelmed: there is so much info out there that it's very easy to feel crushed by the sheer amount of it. Start with what you need to learn in a specific moment, then expand. Be careful: use only proven and official materials. There is a lot of "low quality" material that can point you into wrong direction
2) Point out that agility is a MINDSET and that without that, only going through the moves of scrum, is not agility! So, the question is: do you want to play seriously and change the mindset? Do you (all) will be willing to play this game? BE AWARE: this thing can be a very long process, for sure is not achieved snapping the fingers
3) Be transparent with your team: you are going to learn together! Tell them that this is your first experience, tell them that you (all) will do good things, lots of errors but you'll learn from them and that you'll grow together
4) Tell the team that you'll become a team, with time. At the beginning you'll be just a group of person that work together
5) Work on "team building". There are games for doing that, if you are colocated, have fun together past working time and so on
6) Teach them about agility and scrum: if they don't know about it, they cannot understand the WHYs behind every concept, event, practice
7) The team lead: you are a facilitator, a teacher a coach. You should find ways to help them to understand which are the good things and the things that can be improved. You don't solve them, unless they are not able to do it themselves (eg they cannot reach the right people for solving an issue).
This is the most difficult thing to do: DON'T do things yourself for solving issues that they can solve and helping them to understand how they can improve and help themselves. This is about taking ownership of what everyone has to do
8) stay in touch with other scrum masters (there are communinties and channels for doing that). Obviously it would be better to have a mentor, but it's so rare (at least in my experience)... in my case, never had one
9) as said before: it's a NEVER ending journey! Take it a step at time, you'll learn, you'll improve, you'll be better. It requires a lot of time and it's like being above a rollercoaster. Even after many teams, two certifications, different customers, I often find myself doubting on my abilities as a scrum master. The I try to focus more on what I'm able to do and what I've learned than what I've still have to learn (that it's a LOT more of what I already know, so it's scaring). That usually gives me a bit of confidence!
10) Don't seek for perfection: not for you, not for the team, not for the environment! You'll NEVER be perfect, the team will NEVER be perfect, the environment will NEVER be perfect. You can only be as you are and improve from there.
These suggestions are in a sparse order! I hope that Daria is not going to find something terribly wrong in them.
Good luck with your team, I'm sure that you'll be great!
Alessandro
PS: watch this, it's a nice summarization of our role ;)
th-cam.com/video/S5zrZMyKm9s/w-d-xo.html
Awesome suggestions, Alessandro!
I am first today
The featured comment for this video :)