230/5000 I learned a lot about Scrum from this video with these 2 brilliant founders of Scrum Framework. With their work they have made an enormous contribution to the IT industry. Thank you very much from the Netherlands! Chander Khoenkhoen
Highlighting that the framework can be applied beyond software is a nice addition. The additional information and rewording for the Scrum Master role will be helpful to some. Daily Scrum changes are a great step in a positive direction. Promoting a conversation over the three question format (3QF) or walking the board has been a challenging sell even to PSTs. The need to further reiterate the definition of a time-box highlights one of many symptoms exemplifying that Scrum, for many, is not "Simple to understand" as advertised. :-) The requirement to have "at least one high priority process improvement identified in the previous Retrospective meeting" on the Sprint Backlog creates some issues as it does not align with the definition of the Sprint Backlog. It is not a Product Backlog Item (PBI). It is not a part of the plan for delivering the Increment and realizing the Sprint Goal. It is not a forecast of functionality. The Sprint Backlog belongs solely to the Development Team therefore so would this process improvement item. Changes are inspected and adapted during the Daily Scrum (for Development Team only). Development Team works through the plan. Only the Development Team can change its Sprint Backlog during a Sprint. It is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint. I also find the change from "The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum." to "The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting." problematic as it interferes with self-organization. It was already difficult enough to keep many organizations from using it as a traditional status update meeting. Transparency is a pillar but the information discussed during the Daily Scrum should generally have no impact on anybody else. If it does, then it is the Development Team's responsibility to raise the concerns and issues.
I have noticed that "agile marketing movement" often refers to Scrum as to a methodology or technique and many people are just copying it without even checking the real source.
Fantastic session, Great words from these two gentlemen. My only concern is why is this video that was posted in Nov 2017 with these two wonderful founders of Scrum having so less views and so under-liked. Makes me very curious, 15 M people are using Scrum where are they and what are they doing with Scrum?
Thank you Robert. We don't have any specific ones scheduled, but there are a lot of additional resources, documents, papers, blog article and forum posts at www.scrum.org.
Spotify doesn't use scrum. According to James Coplien, the vast majority of teams don't do scrum correctly. I have been on many teams at several different companies and scrum has always failed.
Spotify did Scrum, but when their company grew they made certain Scrum practices optional: labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/.
How can I be the first one to comment on this video? What is going on in the Scrum Community? My top change is making it clear that the improvements from the Retro are going to the Sprint Backlog.
Great improvements, self-organization, integrity, transparency and cross-functionality, but most importantly respect people in your team. Have a vision & quickly determine if it's usable.
Scrum actually sucks. It ruins projects. If your team is lacking teamwork skills then you have failed as a manager to lead, and you have failed as a boss when hiring
Agile is about micro managing people and takes a lot more effort than traditional waterfall techniques but without the documentation to be able to do a similar project in the future.
I do not agree. There is plenty of documentation and planning on agile. It just means you don’t plan a year at a time and be inflexible about change. Agile means you learn and adapt as you go forward. Documentation is key to communication. Additionally, it is about self-organization and trust, not micro managing. The team is trusted to do what it needs, etc. You should check out a few things: 1. The Scrum Values - www.scrum.org/resources/scrum-values-poster 2. Evidence Based Management - www.scrum.org/resources/evidence-based-management 3. Product Backlog Management which contains the documentation that you claim doesn't exist
@Wayne, could you elaborate on how you developed your perception? Scrum takes quite a while, sometimes years, for many organizations to truly implement. They (hopefully) move steadily along the maturity spectrum. During that journey, mindsets have to change. Often, there are struggles to shift and they'll focus in on certain practices that do seem like micro managing. They're not ready yet to give up that predictive, command & control style of working. I know that my own organization is moving along the spectrum. As a Scrum Master, I see some of those struggles. But it excites me, because it opens pathways to talk about how to introduce better Scrum maturity. From your comment, I'm wondering if you were at such an organization and it might have left you with disappointment in the methodology. If so, I hope your future experiences are better.
![Official Scrum Guide Update 2020 - Changes & Impact LIVE Event [Recording]](http://i.ytimg.com/vi/Dfxo3PZwDI8/mqdefault.jpg)
230/5000
I learned a lot about Scrum from this video with these 2 brilliant founders of Scrum Framework.
With their work they have made an enormous contribution to the IT industry.
Thank you very much from the Netherlands!
Chander Khoenkhoen
This vlog is severely underliked...A definitive video..by the founders
Highlighting that the framework can be applied beyond software is a nice addition.
The additional information and rewording for the Scrum Master role will be helpful to some.
Daily Scrum changes are a great step in a positive direction. Promoting a conversation over the three question format (3QF) or walking the board has been a challenging sell even to PSTs.
The need to further reiterate the definition of a time-box highlights one of many symptoms exemplifying that Scrum, for many, is not "Simple to understand" as advertised. :-)
The requirement to have "at least one high priority process improvement identified in the previous Retrospective meeting" on the Sprint Backlog creates some issues as it does not align with the definition of the Sprint Backlog.
It is not a Product Backlog Item (PBI).
It is not a part of the plan for delivering the Increment and realizing the Sprint Goal.
It is not a forecast of functionality.
The Sprint Backlog belongs solely to the Development Team therefore so would this process improvement item.
Changes are inspected and adapted during the Daily Scrum (for Development Team only).
Development Team works through the plan.
Only the Development Team can change its Sprint Backlog during a Sprint.
It is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint.
I also find the change from "The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum." to "The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting." problematic as it interferes with self-organization. It was already difficult enough to keep many organizations from using it as a traditional status update meeting. Transparency is a pillar but the information discussed during the Daily Scrum should generally have no impact on anybody else. If it does, then it is the Development Team's responsibility to raise the concerns and issues.
I have noticed that "agile marketing movement" often refers to Scrum as to a methodology or technique and many people are just copying it without even checking the real source.
I am just loving the whole framework. This is fabulous, challenging and real.
Great interview! Please buy some Microphones next time before the meeting with these icons, precciate it, hastag no blame.
Fantastic session, Great words from these two gentlemen.
My only concern is why is this video that was posted in Nov 2017 with these two wonderful founders of Scrum having so less views and so under-liked. Makes me very curious, 15 M people are using Scrum where are they and what are they doing with Scrum?
I stumbled on SCRUM talking to a family member who mentioned it offhandedly and I went went and Googled it, bammm! I'm in a different world.
Great interview 👍..
Lost audio from about 50:01
Really loved the interactions, thanks for helping over come the mis conceptions...!!!!!
Great interview and info!! Is there a follow-up mtg/interview?
Thank you Robert. We don't have any specific ones scheduled, but there are a lot of additional resources, documents, papers, blog article and forum posts at www.scrum.org.
It's an honor for me to watch this interview!
Spotify doesn't use scrum. According to James Coplien, the vast majority of teams don't do scrum correctly. I have been on many teams at several different companies and scrum has always failed.
Spotify did Scrum, but when their company grew they made certain Scrum practices optional: labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/.
I love framework
This was a great video on the scrum framework
54:40 "because the world needs " (not understandable for non native English speaker...)
"because the world needs them" referring to what Jeff said about implementing Scrum just prior.
How can I be the first one to comment on this video? What is going on in the Scrum Community?
My top change is making it clear that the improvements from the Retro are going to the Sprint Backlog.
Great improvements, self-organization, integrity, transparency and cross-functionality, but most importantly respect people in your team. Have a vision & quickly determine if it's usable.
Scrum actually sucks. It ruins projects. If your team is lacking teamwork skills then you have failed as a manager to lead, and you have failed as a boss when hiring
It's a money making religious scam. Just play the game and make some money out of it.
I smell some offended line manager here. 😅
@@BorisGligorijevic 😂
dang. Whether i dont get the terminology and the way how scrum is explained or, in this case, they saved on the microphone. :(
i like waterfalls.
Agile is about micro managing people and takes a lot more effort than traditional waterfall techniques but without the documentation to be able to do a similar project in the future.
I do not agree. There is plenty of documentation and planning on agile. It just means you don’t plan a year at a time and be inflexible about change. Agile means you learn and adapt as you go forward. Documentation is key to communication.
Additionally, it is about self-organization and trust, not micro managing. The team is trusted to do what it needs, etc. You should check out a few things:
1. The Scrum Values - www.scrum.org/resources/scrum-values-poster
2. Evidence Based Management - www.scrum.org/resources/evidence-based-management
3. Product Backlog Management which contains the documentation that you claim doesn't exist
@Wayne, could you elaborate on how you developed your perception? Scrum takes quite a while, sometimes years, for many organizations to truly implement. They (hopefully) move steadily along the maturity spectrum. During that journey, mindsets have to change. Often, there are struggles to shift and they'll focus in on certain practices that do seem like micro managing. They're not ready yet to give up that predictive, command & control style of working. I know that my own organization is moving along the spectrum. As a Scrum Master, I see some of those struggles. But it excites me, because it opens pathways to talk about how to introduce better Scrum maturity. From your comment, I'm wondering if you were at such an organization and it might have left you with disappointment in the methodology. If so, I hope your future experiences are better.