I learn and refreshed by concepts with this video. At timing 6:13; "by the end of sprint planning Spring backlog items are decomposed into tasks of day or less duration", slight change here as per 2017 Scrum guide, task for the first day of the sprint only. And dev teams measure their progress towards the goal during daily scrum and plan the days work.
Good day Per, Great job. I would recommend to continue and add new training and visions. 1. Tools and Scrum; 2. Old/New roles ( BA, PM, QC, QA) in Scrum; 3. Big projects/products and Scrum; 4. How to plan first product/project/sprint in Scrum; 5. Assessment approaches and techniques in Scrum; and so on... I appreciate your approach. Thanks
Best Scrum video ever! Someone who is coming from waterfall environment (in Sales, Construction and engineering) I was having trouble to make sense of Scrum guide. After watching your video and reading the Scrum guide everything clicked and started making sense :) It is a must watch video before and after reading the Scrum guide... Thanks a lot !
Hi Thanks for the kind words. I'm happy you enjoyed it. The video was initially made with the purpose of giving an introduction to Scrum and the Scrum Guide. Happy that it still works within that context.
This is a great summary of the scrum guide. I do, however, have a small correction. There are five events and the backlog grooming is not one of them. It is rather an ongoing activity. The events are 1) sprint planning 2) daily scrum 3) sprint review 4) sprint retrospective and 5) the sprint ( time box fir the aforementioned events). Thank you for sharing this!!
Hi Adam, You are totally right! The Product Backlog Refinement as well as the Sprint cancellation are Best Practices and NOT Scrum Events as I'm stating in the video. Thank you for pointing this out, and taking your time to post your comment.
Per, What can I say? A fantastic summary of the concepts; succicnt, interesting, beautifully illustrated....I can go on. This video has kindled my interest in scrum - I am going through the URLs cited. Thanks very much for sharing it so nicely!!!
This is one of the best scrum definition videos in my books 😎 . My understanding of scrum was a bit cloudy before i watched this video, now the skies are clear 🙌🏽 . Absolutely love it and appreciate it THANK YOU! PS. if you could please include the URLs at the end of the video in the description also to be accessible just by a click
Excellent Video. Because of the animation now i would remember everything more easily . I am preparing for the PSM exam and found 2 deviations in your video from the scrum guide. 1. There are 5 events ( sprint, sprint planning, daily scrum, sprint review and sprint retrospective) out of which except sprint all 4 are inspecting and adapting events. You mentions product backlog refinement as a scrum event which ideally it is not ! 2. 3 questions are no longer part of daily scrum. Please correct me if i have misunderstood.
Hi Malcolm, Thanks! It's based on the Scrum Guide 2013 version. And Since I've made it - 4 years ago I've noticed a few errors: The PBL Refinement and The Sprint Cancellations are Best Practices and not Events. But beside that - I agree: The first 12 min. gives a good overview of Scrum (quick intro for everyone new to SCrum and Agile). And the remaining are a good listing of a lot of the facts for the CSM Certification and also for the Scrum.org PSM I Assessment. Thanks for you taking the time to comment! Brgds Per
sorry, but I need sock puppets and cowbell....more cowbell.....all kidding aside, thanks that is great, I am about to attend a CSM course in the coming weeks.
This entire video is excellent. Your explanation was really didactic as well. I just had trouble downloading the sketchnote picture - the website doesn't seem to be working. Anyway, thanks a lot for your efforts!
Great Video! Thank you so much for this! I like Agile but I feel Scrum is lacking. I wonder if anyone has used waterfall iteratively in a way that is agile? To me that would make the most sense in software development.
Nice and useful presentation, I think it would be a good idea to put the two links as a description of your presentation. Could you please also share with me which material did you use to create the video ? thx.
the quality of the tutorial had some issues while viewing in the auto mode. ( may be some network problems ) . Other wise its the best in class of the CSM practical understanding in the implementation. Good job.
I've been told it's used by some CSM and PSM Trainers as an introduction for their students for Scrum.org PSM I Professional Scrum Master Assessment and the CSM Scrum Master Certification. I also use it myself for prepping the students of my Scrum Master Classes for the Scrum.org PSM I Assessment.
Comment after resuming the video @ 14:12 minute: Estimate is done by the Dev only?! I know it's a joint process where the entire TEAM (PO, DEV and Testers) voice and vote for estimation.
It's the development team that is accountable for the estimates. They are definitely allowed to consult the Product Owner on details. As mentioned there is no tester role in Scrum by the book.
Well, I agree with the concept of 'self organization' and some organizations perhaps authorize developers for estimation. I'm new to JIRA and have been following Agile (Scrum) as opposed to Agile (Kanban) for the last last 30+ months and in many projects. In our organization, estimation is a democratic process (highest votes for each estimation gets approved) to decide either Story Point or Hours for each Sprint. I'm still not sure how Scrum process works without tester! As far as I know from my 6+ years experiences in software testing, Developers DO NOT test except Unit testing, let alone being known as Testers.
I have been in contact with many teams, where the tester title is not existing. Its typically due to really high maturity - both in regards to the Agile mindset and the Teams Maturity (teams are definitely in the Performing state - with reference to Tuckmans model). In Jira - you are totally correct - there are 2 templates that can be used for working agile: The Scrum setup/Template and the Scrum setup/Template. The video is a visualisation of whats included in the Scrum Guide. So it's not a "Scrum as implemented in Jira" or "Scrum as implemented in my company". Important is probably also to state that Scrum is a framework - not a process. When you implement all the elements of scrum - and decide how you and your team will adhere to the elements - then you have a process. I hope that clarifies even more.
Well presented. One question I have is that at 13:44 you say all team members are "developers." I have a difficult time finding that in the Scrum Guide and in fact this seems at odds with the Scrum Guide: "Scrum recognizes no titles for Development Team members." Could you maybe furnish the source for what you say? Thank you.
Comment @ 18 minute: I'm stopping watching this presentation any further. What's your role in the Scrum process? Scrum Master? Product Owner? Developer? If you're any of those, where is YOUR tester? You mentioned impediments. Who finds impediments? It's true that many organization have their own way of implementation the process and defining roles, but as a tester, I know every organization has a place for testers in every steps throughout the project. JIRA Scrum is a collaborative software process, remember? Forgive me for being little sarcastic, but without testers, none of those position I mentioned are non-functional.
Thanks for watching that much. The video is as mentioned with set off in Scrum by the book. So no Tester role. The impediments are raised by the development team. If not when they are encountered, then at the latest at the daily scrum. You can find all the details in the Scrum Guide - by Kenneth Schwaber and Jeff Sutherland: scrumguides.org/scrum-guide.html Jira is (as you probably already know) a software tool - and the process in there can be customized any way you want. So It's not necessarily following Scrum by the book. And in real life a lot of organisations have a specific role for the Quality Assurance part of systems/product development. In my experience - with the teams with the highest level of Agile and Team Maturity: moving away from specific titles makes work a lot better flowing. It's not easy to get there. And sometimes personal agendas needs to be broken down and some I highly recommend the book "Joy .Inc" by Richard Sheridan (menloinnovations.com/joyinc/) for some great ideas on how working in pairs could help moving teams and companies into that direction. It's OK that your being a little sarcastic. I'm sure that in your world a tester is needed. And don't misunderstand me: Testing or quality Assurance is important - also in Scrum. But no specific role is titled for that. In the Same way there is no title for Architects, Usability Experts, User Interface designers, Business Analysts, Test Managers etc. etc. Thanks for your comments! I hope I was able to give a bit more details to why there is no tester in Scrum by the book. /Per
Please do not get me wrong. I'm not a rolecentric person. Your concept and presentation in premise of SDLC under Agile framework is much more resourceful than many others' on RUclips. Except that in your Scrum, no role or contribution of testers is acknowledged!
The way you did it is very confusing and not good at all. Having a very bad hand writing plus slow sketch-note drawing totally took me out of the way. I am not complaining about the content of your video and I am sure you are a great teacher but pls use a different way to do the video. If you really have to use the Sketch-note then use a totally different software which has a better hand writing. I started to watch but it really made me stop and write thins not to you. Pls change the hand writing and re do the Video and I am sure your video will be watched and enjoyed by many more people. Thanks for your video.
Hi, Sorry that you didn't like my video. We all learn differently. The great thing about the internet is that you can always find something else that will fit your preferences. /Per
I paused the video @ 14 minutes to make a timely comment: During this entire time, you didn't mention a): The importance of writing or defining 'Acceptance Criteria' {when it is written and who writes it} and b): NO mention of any role or importance of TESTER! Perhaps you have discussed those in the remaining time, for for a sequential development of the concept, it would have been beneficial if you had incorporated testers moving forward, in my opinion. Let's move on for the remaining presentation....
Hi Mokter Ahmed, Thanks for your comment. The video is related to Scrum with emphasis on "by the book". And Neither Acceptance criteria nor Tester role is part of Scrum. Scrum specifically states that all people in the Development Team have titles of developers - no matter what kind of work they are performing. This supports the selforganizing element of the development team - and fuels the cross-functionality.
I learn and refreshed by concepts with this video. At timing 6:13; "by the end of sprint planning Spring backlog items are decomposed into tasks of day or less duration", slight change here as per 2017 Scrum guide, task for the first day of the sprint only. And dev teams measure their progress towards the goal during daily scrum and plan the days work.
Very useful, in a simple language and very close to the Scrum Guide. Thank you!
Good day Per,
Great job.
I would recommend to continue and add new training and visions.
1. Tools and Scrum;
2. Old/New roles ( BA, PM, QC, QA) in Scrum;
3. Big projects/products and Scrum;
4. How to plan first product/project/sprint in Scrum;
5. Assessment approaches and techniques in Scrum;
and so on...
I appreciate your approach.
Thanks
Best Scrum video ever! Someone who is coming from waterfall environment (in Sales, Construction and engineering) I was having trouble to make sense of Scrum guide. After watching your video and reading the Scrum guide everything clicked and started making sense :) It is a must watch video before and after reading the Scrum guide...
Thanks a lot !
Hi Thanks for the kind words. I'm happy you enjoyed it. The video was initially made with the purpose of giving an introduction to Scrum and the Scrum Guide. Happy that it still works within that context.
Excellent overview and visuals. Thank You!
Excellent Scrum presentation - It looks like a Scrum Guide in a Box! Nicely summarized - Good Job!!
Thanks for the kind comment.
Great and detailed overview. The best I've gone though so far. Exactly for visual learners like me. Many, many thanks, Per! :)
yES I AGREE WITH YOU
One word .... FANTABULOUS
I fucking love scrum
Excellent and easy to understand. It wasn't too fast so i was able to take notes. I appreciate it!
Great that you liked it.
This is a great summary of the scrum guide. I do, however, have a small correction. There are five events and the backlog grooming is not one of them. It is rather an ongoing activity. The events are 1) sprint planning 2) daily scrum 3) sprint review 4) sprint retrospective and 5) the sprint ( time box fir the aforementioned events). Thank you for sharing this!!
Hi Adam, You are totally right!
The Product Backlog Refinement as well as the Sprint cancellation are Best Practices and NOT Scrum Events as I'm stating in the video.
Thank you for pointing this out, and taking your time to post your comment.
Per,
What can I say? A fantastic summary of the concepts; succicnt, interesting, beautifully illustrated....I can go on. This video has kindled my interest in scrum - I am going through the URLs cited. Thanks very much for sharing it so nicely!!!
Hi Partha,
Thanks so much for the kind word!
I do hope you will have great experiences in your continued Scrum journey.
/Per
Great!!!! Thank you!
This is one of the best scrum definition videos in my books 😎 . My understanding of scrum was a bit cloudy before i watched this video, now the skies are clear 🙌🏽 . Absolutely love it and appreciate it THANK YOU!
PS. if you could please include the URLs at the end of the video in the description also to be accessible just by a click
Great Job Beining...enjoyed your video as it was fun.
Great video! Was bored when reading the Scrum Handbook, this video made it more interesting. Thanks :)
Thank you so much Sir. Regards
thank you Per - still serves me today :-) michael
This is awesome 😎
The presentation style and pace is excellent, kudos!
Thanks for the kind words. Happy that you enjoyed it.
Excellent Video. Because of the animation now i would remember everything more easily . I am preparing for the PSM exam and found 2 deviations in your video from the scrum guide.
1. There are 5 events ( sprint, sprint planning, daily scrum, sprint review and sprint retrospective) out of which except sprint all 4 are inspecting and adapting events. You mentions product backlog refinement as a scrum event which ideally it is not !
2. 3 questions are no longer part of daily scrum.
Please correct me if i have misunderstood.
Very nice voice,explanation and visuals ! Thanks
Thanks a lot!
Brilliant overview and hopefully a good prep for the CSM course and exam
Hi Malcolm, Thanks!
It's based on the Scrum Guide 2013 version.
And Since I've made it - 4 years ago I've noticed a few errors: The PBL Refinement and The Sprint Cancellations are Best Practices and not Events.
But beside that - I agree: The first 12 min. gives a good overview of Scrum (quick intro for everyone new to SCrum and Agile).
And the remaining are a good listing of a lot of the facts for the CSM Certification and also for the Scrum.org PSM I Assessment.
Thanks for you taking the time to comment!
Brgds
Per
scrumguides.org/scrum-guide.html
agilemanifesto.org/
Hi,
Thanks for adding the reference to the actual book: The Scrum Guide: scrumguides.org/scrum-guide.html
excellent illustration.
sorry, but I need sock puppets and cowbell....more cowbell.....all kidding aside, thanks that is great, I am about to attend a CSM course in the coming weeks.
41 years old. Never heard of this word.
Thanks its a very brief and clear guide for scrum methodology. But I could not reach the link of presantation Can one one help me to get it ? Thanks
This entire video is excellent. Your explanation was really didactic as well. I just had trouble downloading the sketchnote picture - the website doesn't seem to be working. Anyway, thanks a lot for your efforts!
Great Video! Thank you so much for this! I like Agile but I feel Scrum is lacking. I wonder if anyone has used waterfall iteratively in a way that is agile? To me that would make the most sense in software development.
Nice and useful presentation, I think it would be a good idea to put the two links as a description of your presentation.
Could you please also share with me which material did you use to create the video ? thx.
Great job on this. I'd love to download the picture but I get an error when clicking on your URL. Is there another way to get it?
the quality of the tutorial had some issues while viewing in the auto mode. ( may be some network problems ) . Other wise its the best in class of the CSM practical understanding in the implementation. Good job.
Thanks a lot!
I've been told it's used by some CSM and PSM Trainers as an introduction for their students for Scrum.org PSM I Professional Scrum Master Assessment and the CSM Scrum Master Certification.
I also use it myself for prepping the students of my Scrum Master Classes for the Scrum.org PSM I Assessment.
A+ Thank You.
Thank you so much. The tutorial is perfect.
PS. Can you fix the pdf of the sketchnote because the image is trimmed at the edges.
scrumguides.org/scrum-guide.html
agilemanifesto.org/
thank you so
very helpfull tuto
Gmh918283731 Ach675848 I
Comment after resuming the video @ 14:12 minute: Estimate is done by the Dev only?! I know it's a joint process where the entire TEAM (PO, DEV and Testers) voice and vote for estimation.
It's the development team that is accountable for the estimates.
They are definitely allowed to consult the Product Owner on details.
As mentioned there is no tester role in Scrum by the book.
Well, I agree with the concept of 'self organization' and some organizations perhaps authorize developers for estimation. I'm new to JIRA and have been following Agile (Scrum) as opposed to Agile (Kanban) for the last last 30+ months and in many projects.
In our organization, estimation is a democratic process (highest votes for each estimation gets approved) to decide either Story Point or Hours for each Sprint.
I'm still not sure how Scrum process works without tester!
As far as I know from my 6+ years experiences in software testing, Developers DO NOT test except Unit testing, let alone being known as Testers.
I have been in contact with many teams, where the tester title is not existing. Its typically due to really high maturity - both in regards to the Agile mindset and the Teams Maturity (teams are definitely in the Performing state - with reference to Tuckmans model).
In Jira - you are totally correct - there are 2 templates that can be used for working agile: The Scrum setup/Template and the Scrum setup/Template.
The video is a visualisation of whats included in the Scrum Guide. So it's not a "Scrum as implemented in Jira" or "Scrum as implemented in my company". Important is probably also to state that Scrum is a framework - not a process. When you implement all the elements of scrum - and decide how you and your team will adhere to the elements - then you have a process.
I hope that clarifies even more.
Well presented. One question I have is that at 13:44 you say all team members are "developers." I have a difficult time finding that in the Scrum Guide and in fact this seems at odds with the Scrum Guide: "Scrum recognizes no titles for Development Team members." Could you maybe furnish the source for what you say? Thank you.
Lekker kort dit
Comment @ 18 minute: I'm stopping watching this presentation any further.
What's your role in the Scrum process?
Scrum Master?
Product Owner?
Developer?
If you're any of those, where is YOUR tester?
You mentioned impediments.
Who finds impediments?
It's true that many organization have their own way of implementation the process and defining roles, but as a tester, I know every organization has a place for testers in every steps throughout the project.
JIRA Scrum is a collaborative software process, remember?
Forgive me for being little sarcastic, but without testers, none of those position I mentioned are non-functional.
Thanks for watching that much.
The video is as mentioned with set off in Scrum by the book. So no Tester role.
The impediments are raised by the development team. If not when they are encountered, then at the latest at the daily scrum.
You can find all the details in the Scrum Guide - by Kenneth Schwaber and Jeff Sutherland: scrumguides.org/scrum-guide.html
Jira is (as you probably already know) a software tool - and the process in there can be customized any way you want. So It's not necessarily following Scrum by the book.
And in real life a lot of organisations have a specific role for the Quality Assurance part of systems/product development. In my experience - with the teams with the highest level of Agile and Team Maturity: moving away from specific titles makes work a lot better flowing. It's not easy to get there. And sometimes personal agendas needs to be broken down and some
I highly recommend the book "Joy .Inc" by Richard Sheridan (menloinnovations.com/joyinc/) for some great ideas on how working in pairs could help moving teams and companies into that direction.
It's OK that your being a little sarcastic. I'm sure that in your world a tester is needed. And don't misunderstand me: Testing or quality Assurance is important - also in Scrum. But no specific role is titled for that. In the Same way there is no title for Architects, Usability Experts, User Interface designers, Business Analysts, Test Managers etc. etc.
Thanks for your comments! I hope I was able to give a bit more details to why there is no tester in Scrum by the book.
/Per
Please do not get me wrong. I'm not a rolecentric person.
Your concept and presentation in premise of SDLC under Agile framework is much more resourceful than many others' on RUclips.
Except that in your Scrum, no role or contribution of testers is acknowledged!
Hi,
Thanks for this clarification, with a clear link to the content of the Scrum Guide.
/Per
The way you did it is very confusing and not good at all. Having a very bad hand writing plus slow sketch-note drawing totally took me out of the way. I am not complaining about the content of your video and I am sure you are a great teacher but pls use a different way to do the video. If you really have to use the Sketch-note then use a totally different software which has a better hand writing. I started to watch but it really made me stop and write thins not to you.
Pls change the hand writing and re do the Video and I am sure your video will be watched and enjoyed by many more people.
Thanks for your video.
Hi,
Sorry that you didn't like my video. We all learn differently. The great thing about the internet is that you can always find something else that will fit your preferences.
/Per
I paused the video @ 14 minutes to make a timely comment: During this entire time, you didn't mention a): The importance of writing or defining 'Acceptance Criteria' {when it is written and who writes it} and b): NO mention of any role or importance of TESTER! Perhaps you have discussed those in the remaining time, for for a sequential development of the concept, it would have been beneficial if you had incorporated testers moving forward, in my opinion. Let's move on for the remaining presentation....
Hi Mokter Ahmed,
Thanks for your comment.
The video is related to Scrum with emphasis on "by the book". And Neither Acceptance criteria nor Tester role is part of Scrum.
Scrum specifically states that all people in the Development Team have titles of developers - no matter what kind of work they are performing.
This supports the selforganizing element of the development team - and fuels the cross-functionality.