This was my first video(year 2013) to get to know about scrum before interview, When interviewer asked my question about scrum I explain same what you did here in video. Wow! no further question asked and I got job. Thanks you very much.
Going to be 11 years old video.. all the pointers said here are still relevant and effective in the way we work! Thanks for putting this video and still available for all Scrum masters or Agile Coachers!
Hey ! Great work Lyssa...I was trying to relate all that I have learned so far and watching your video made my life so much easier to understand the Scrum Framework...Thanks for this one :)
This is one of the clearest and best explanations of SCRUM I've ever come across...the business you work in is blessed to have someone as concise and coherent as you. Can scrum work when you're trying to intergrate a 3rd party package into your 'product' when the 3rd party package is actually orchestrating parts of your processes and they want requirements up front to build their modules? Can you run multiple sprints in parallel if you have enough people to form multiple teams?
Yes you can run multiple teams building components of the products in parallel. Then you will need to have what is called the scrum of scrums to harmonize the work. Scrum can work when you are working with third parties even though it can be a little more challenging. As you know scrum is a philosophy, a culture and if your supplier does not buy into that culture it may be difficult for them to work within it's parameters.
Hi Lyssa! Great presentation and great book. One thing you omitted here is the critical step of Product Backlog Refinement (what we used to call grooming). Thanks!
A mi siempre me salen las mismas dudas. Qué pasa si al final del sprint hay tareas que no se han terminado? Qué pasa si a mitad de sprint se han terminado todas? Y si alguien se pone malo? Y si hay imprevistos? Y si hay q hacer otras cosas como dar soporte, arreglar bugs del sprint anterior que surgen en mitad de otro sprint?
Fernando F. Gallego Scrum deja muchas cosas abiertas, pero a mí también me gustaría oír consejos de _expertos_ sobre ese tipo de casos. Supongo que pasará más o menos como cuando te equivocas en la planificación con otra metodología: la cagaste, empieza a echar horas extra xD Lo que no cuenta en el vídeo es que diariamente se actualiza el gráfico de Burndown, en el que se compara el trabajo realizado con el trabajo que queda por hacer. Así se va viendo si se van a quedar cortos o se pasan de la planificación, y pueden ajustar la carga de trabajo. Pero vamos, supongo que cada equipo se adaptará a los imprevistos como pueda.
You are correct but I think describing a Scrum Master as an Agile Coach is a good thing because a lot of people seem to think that the SM is a Project Manager. The term agile coach helps to uderscore the coaching element of the SM role.
Hi Lyssa, I think it's important to clarify (and change in the video) your usage of the term Commitment. A few times throughout the video you state thing like: "the team commits to getting these things done in the Sprint"; or each team member in the Daily Scrum "makes a commitment to each other about what they're going to get done" in the day. The use of 'Commitment' in the most recent version of the Scrum Guide is (I believe) quite different -- specifically, "people personally commit to achieving the goals of the Scrum Team". That usage may appear compatible with your usage; however, "achieving the goals of the Scrum Team" is a broad statement which goes well beyond and may not relate to specific PBIs or Sprint Backlog tasks. For example, the Scrum Team's goal may not have one-to-one relationship to the Sprint Goal; and may not relate in a direct way to the Product Vision. The Scrum Team may set itself a goal like 'zero defects' or 'learning a new technology' or 'better communication' or 'hiring another developer'. A participant in my Scrum Master class put it nicely: "we commit to each other, we earn our place in the team every day". Due to the relative popularity of your video, I worry its usage of that term may reinforce the (wrong) notion that "estimates == commitments".
I appreciate this comment was written prior to Scrum Guide 2020. Nowadays the word 'commitment' is used extensively throughout the Scrum Guide. An example extract is: "Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: For the Product Backlog it is the Product Goal. For the Sprint Backlog it is the Sprint Goal. For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism and the Scrum values for the Scrum Team and their stakeholders."
I am interested to learn why you picked Agile Coach as a more generic term for Scrum Master rather than something like Agile Master. Because a Scrum mastery is not only about coaching and not only about Agile.
Great job! QQ - How to handle the scenario appropriately when during the sprint something changes which change the whole dynamics? The work in progress is needed to stop and ... your thoughts?
This scenario is exactly what scrum is designed for- ability to respond the change. The shorter the sprint the better because it means the work can be stopped.
I wonder what Steve Jobs would say about this concept? There is basic tenet coined by Einstein which states that: "Anyone can make that which is complex..more complex....it takes a breath of genius to take that which is complex and make it simple!"....I wonder what he would say about SCRUM...brilliant or ......
Scrum Framework doesn't have an Agile Coach role. Scrum Guide is clear about it. Scrum doesn't have a Team Member role, it's Developer. PBL is ordered not prioritized. Daily Standup is called Scrum - would be nice do mention that since it influences the framework's name. Definition of Done is also important part in Scrum. The exercise is a great idea. I need to give it a try myself.
between 10 and 15 seconds you state "every coach should be able to train the framework of their choice in 10 minutes or less". Really? Train an entire framework in 10 minutes? Do your training classes only last 10 minutes? Get rid of that and it's a decent, quick overview of scrum.
Read the description and you might understand why :) It doesn't mean that if you know how to explain it under 10 minutes, from that moment on, you can ONLY teach it in 10 minutes, even if it's a training class. Being able to explain it under 10 minutes is simply one more tool in your agile coach toolbox, ready to be used over and over again, whenever needed :)
This was my first video(year 2013) to get to know about scrum before interview, When interviewer asked my question about scrum I explain same what you did here in video. Wow! no further question asked and I got job. Thanks you very much.
Going to be 11 years old video.. all the pointers said here are still relevant and effective in the way we work! Thanks for putting this video and still available for all Scrum masters or Agile Coachers!
Thank you, Lyssa, for scrum framework explained in a nutshell.
Thanks, Lisa for simplifying the scrum framework!
Very concise and useful. This is what we call mastering the field.
Hey ! Great work Lyssa...I was trying to relate all that I have learned so far and watching your video made my life so much easier to understand the Scrum Framework...Thanks for this one :)
Excellent recap for the Scrum Framework - Thanks Lyssa!
Your teaching of scrum agile framework was very informative. Keep it up!!!
Awesome！ this is the best SCRUM demo video I have ever seen
Excellent Scrum Framework overview in 10 minutes.
Very precise and clear illustration.
Very nice! All I've read make more sense now! Thank you!
Just wanted to say that your book is great and I have been using it in my coaching for quite a while! Thanks for all the hard work!
Very useful picture and comments, thanx
Very good video. Succinct and informative. Will use this info to explain Scrum quickly!
Explain it quickly? Is this because you or "them" don't have time?
This is one of the clearest and best explanations of SCRUM I've ever come across...the business you work in is blessed to have someone as concise and coherent as you.
Can scrum work when you're trying to intergrate a 3rd party package into your 'product' when the 3rd party package is actually orchestrating parts of your processes and they want requirements up front to build their modules?
Can you run multiple sprints in parallel if you have enough people to form multiple teams?
Yes you can run multiple teams building components of the products in parallel. Then you will need to have what is called the scrum of scrums to harmonize the work. Scrum can work when you are working with third parties even though it can be a little more challenging. As you know scrum is a philosophy, a culture and if your supplier does not buy into that culture it may be difficult for them to work within it's parameters.
Best explanation on SCRUM thus far.. thank you
thumbs up. precise and accurate with the right keywords. awesome
very good presentation and you have explained the scrum framework nicely
Spot on, very helpful and clear
Hi Lyssa! Great presentation and great book. One thing you omitted here is the critical step of Product Backlog Refinement (what we used to call grooming). Thanks!
Thank you for the video, the best explanation I've found
Excellent and very clear presentation. > Congratulations!!!
i realize it's kinda off topic but does anybody know a good place to stream newly released series online?
@Karsyn Mathew i watch on flixzone. You can find it on google =)
@Jesus Mateo yea, I've been using flixzone for since april myself =)
@Jesus Mateo thank you, signed up and it seems like a nice service :) I really appreciate it!!
@Karsyn Mathew happy to help =)
Thank you for sharing your simple and nice presentation. Very helpful.
very well explained, everyone should watch
Great video, thanks Lyssa. Agreed that losing the pen sound would be good - maybe record voice separately?
Muy buena explicación rápida de Scrum en 10 minutos. Nos va a ser de mucha ayuda para nuestro proyecto.
A mi siempre me salen las mismas dudas. Qué pasa si al final del sprint hay tareas que no se han terminado? Qué pasa si a mitad de sprint se han terminado todas? Y si alguien se pone malo? Y si hay imprevistos? Y si hay q hacer otras cosas como dar soporte, arreglar bugs del sprint anterior que surgen en mitad de otro sprint?
Fernando F. Gallego Scrum deja muchas cosas abiertas, pero a mí también me gustaría oír consejos de _expertos_ sobre ese tipo de casos. Supongo que pasará más o menos como cuando te equivocas en la planificación con otra metodología: la cagaste, empieza a echar horas extra xD
Lo que no cuenta en el vídeo es que diariamente se actualiza el gráfico de Burndown, en el que se compara el trabajo realizado con el trabajo que queda por hacer. Así se va viendo si se van a quedar cortos o se pasan de la planificación, y pueden ajustar la carga de trabajo.
Pero vamos, supongo que cada equipo se adaptará a los imprevistos como pueda.
Great video, thanks Lyssa. Made my basics clear
You are correct but I think describing a Scrum Master as an Agile Coach is a good thing because a lot of people seem to think that the SM is a Project Manager. The term agile coach helps to uderscore the coaching element of the SM role.
Great! thanks a lot! I would like to work with people like you!
this is amazing, thanks! :)
thanks
Great!!!
Hi Lyssa,
I think it's important to clarify (and change in the video) your usage of the term Commitment. A few times throughout the video you state thing like: "the team commits to getting these things done in the Sprint"; or each team member in the Daily Scrum "makes a commitment to each other about what they're going to get done" in the day. The use of 'Commitment' in the most recent version of the Scrum Guide is (I believe) quite different -- specifically, "people personally commit to achieving the goals of the Scrum Team". That usage may appear compatible with your usage; however, "achieving the goals of the Scrum Team" is a broad statement which goes well beyond and may not relate to specific PBIs or Sprint Backlog tasks. For example, the Scrum Team's goal may not have one-to-one relationship to the Sprint Goal; and may not relate in a direct way to the Product Vision. The Scrum Team may set itself a goal like 'zero defects' or 'learning a new technology' or 'better communication' or 'hiring another developer'. A participant in my Scrum Master class put it nicely: "we commit to each other, we earn our place in the team every day". Due to the relative popularity of your video, I worry its usage of that term may reinforce the (wrong) notion that "estimates == commitments".
I appreciate this comment was written prior to Scrum Guide 2020.
Nowadays the word 'commitment' is used extensively throughout the Scrum Guide. An example extract is:
"Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured:
For the Product Backlog it is the Product Goal.
For the Sprint Backlog it is the Sprint Goal.
For the Increment it is the Definition of Done.
These commitments exist to reinforce empiricism and the Scrum values for the Scrum Team and their stakeholders."
Great video, but the sound can be improved by using noise cancelling mic. Thanks!
I LOVE U, U SAVED MY LIFE :)
I am interested to learn why you picked Agile Coach as a more generic term for Scrum Master rather than something like Agile Master. Because a Scrum mastery is not only about coaching and not only about Agile.
The feature would need to be further decomposed during the Product Backlog grooming process by the development team. There is no exception!
Great job! QQ - How to handle the scenario appropriately when during the sprint something changes which change the whole dynamics? The work in progress is needed to stop and ... your thoughts?
This scenario is exactly what scrum is designed for- ability to respond the change. The shorter the sprint the better because it means the work can be stopped.
I wonder what Steve Jobs would say about this concept?
There is basic tenet coined by Einstein which states that: "Anyone can make that which is complex..more complex....it takes a breath of genius to take that which is complex and make it simple!"....I wonder what he would say about SCRUM...brilliant or ......
very clear but what if no meaningful feature can fit in 4 weeks
Scrum Framework doesn't have an Agile Coach role. Scrum Guide is clear about it. Scrum doesn't have a Team Member role, it's Developer. PBL is ordered not prioritized. Daily Standup is called Scrum - would be nice do mention that since it influences the framework's name. Definition of Done is also important part in Scrum.
The exercise is a great idea. I need to give it a try myself.
Fair !! :)
Agile Coach is optimized for organizational dysfunctions whereas, Scrum master is optimized for team related dysfunctions.
Scrum Master is not an Agile Coach!!! two have very different roles....
between 10 and 15 seconds you state "every coach should be able to train the framework of their choice in 10 minutes or less". Really? Train an entire framework in 10 minutes? Do your training classes only last 10 minutes? Get rid of that and it's a decent, quick overview of scrum.
Read the description and you might understand why :)
It doesn't mean that if you know how to explain it under 10 minutes, from that moment on, you can ONLY teach it in 10 minutes, even if it's a training class.
Being able to explain it under 10 minutes is simply one more tool in your agile coach toolbox, ready to be used over and over again, whenever
needed :)
Jouais c’est pas