Scrum in under 5 minutes

We explain how Scrum works and why it is so useful.

Scrum is an approach for managing projects with more speed, flexibility and energy. Instead of relying on plans, documentation and meetings, you work with a dedicated team in short sprints towards your end result, using feedback from stakeholders along the way. Scrum is a flexible way of working, made for a rapidly changing world.

Scrum is widely used in software development, but is suitable for almost all projects and organizations. We specialize in the application of Agile and Scrum throughout the business.

We are the biggest Agile and Scrum training, consultancy and coaching firm in The Netherlands and the United States. Our products include Scrum, Agile Portfolio Management, Agile Strategy, Agile Marketing, Agile HR, Agile Healthcare and Agile Transformation.

[ButlerBranding]

Just finished reading the book Scrum from the guy who created the process. It was good but unnecessarily long and drug out. It could have been written in one chapter. This video was exactly what I would have hoped the book would be. No fluff, all info.

Great job!

[blitzblix]

I just wanted to watch rugby but this is fine I guess

[kalr]

I appreciate the simplified explanation. Thanks

[VeeouR]

Brilliant and nice to see a Scrum guide that isn't software development centric. To those who commented on what things are called I would ask why that matters? It's Agile culture, mindset, values and principles that deliver results, not naming conventions associated with software teams.

[full-of-ideas]

i did a 2-day product owner course and honestly this kind of summary would have been very helpful

[thgorkha-zmmc]

The "team" you mentioned is actually called "Developers". Theres only one team i.e. scrum team which comprises of a product owner(owns the product backlog), developers(team responsible for developing the product by actually coding for it) and the scrum master(facilitation and process owner)

[BryonLape]

I've been on scrum teams in multiple companies and there were always more meetings with the process than with any other.

[tadaasam]

so beautiful, this video should be a contestant for miss world

[AktharHussain]

Good and extremely simplified explanation of scrum, best suited to someone who has never come across it before.

The first 30 seconds was not correct though and unnecessary.

Scrum is not a replacement for project management. This is because scrum is a framework for developing complex products in complex environments, that can sit within a project methodology. I have done this myself quite successfully as a PM and Scrum Master.

Scrum on its own doesn't bother with all the governance tasks of running a project, or the resource management, or the budget and risk management, or all the other project management tasks..etc. etc.

Ken Schwaber's book, Agile project management with Scrum explains it quite well...

[Wastenotkill]

Nice video, I would recommend using defined names for things like the scrum team and scrum ceremonies which are in the scrum guide. For example, the scrum team consists of a product owner, scrum master and a development team. The ceremonies are, sprint planning, daily scrum, sprint review and sprint retrospective. I really like the example that you used for the design of a new car, which really showed the goal of a sprint which is an incremental delivery of “Done” product ensuring a potentially useful version of working product is always available.

[anish-babusathagopanchella]

For those who want to get straight to the matter: Scrum explanations begin a little after 2 mins into the video. Also, simplification of something already very simple has resulted in misinformation. Scrum events aren't called meetings for a reason - participants in a Scrum environment need to align to mindset that differs from that of 'meetings'. Stand-ups aren't an "are we there yet?" session. I don't understand why random organisations insist on corrupting something as simple as Scrum - if you're really interested in knowing more about Scrum, there're much better videos ...and the Scrum Guide explains everything in a very simple manner.

[dawnmarie]

I'd love how this explained Scrum the easiest way. Thank you for the video!

[IulianBanhammer]

The first seconds imply that you can use scrum everywhere but I would love seeing you using an Agile methodology on a project where u have 8.000 people involved like a nuclear powerplant for example and if the end result will be better than with PMP. The rest looks OK to me.

[thiiiRJ]

Why people spend too much time watching a lot o videos that increase nothing? Self-promotions, sales etc. This is the best video ever. I have PSM and PSPO, so I can confirm, this video was the best I’ve watched on YouTube.

[Covkiller]

As with all scrum explanations, it seems this is a happy-go-lucky approach. No, there has to be a plan and it needs to be followed. Of course, things can be broken down into a sensible number of scrums, which need to be defined and planned, with SIT, Training, UAT sign-off, Go live cutover, hypercare and handover to operational support.

[sallymichaud]

This concept is very interesting. I have never heard of Scrum so I was very curious to learn more about what it is and why it helps with making projects more efficient. As a planner for both my personal and professional life it is so important to stay on target and that can be so hard to do on a team. I definitely think this concept can help many teams become more efficient and effective, allowing for more positive outcomes and help from keeping a team burnt out. Great video! I will be looking for more concepts like this one to use in the future.

[Voxie]

Very professional video, great way to explain how Scrum works. However, there are a couple of big misunderstandings that are explained in this video that are incorrect and therefore can cause confusion.

The Development Team, what's called team in this video is the team of development (software or otherwise) professionals. Most importantly the Scrum Master and Product Owner are also part of the Scrum Team. Each with their own responsibility.

The Scrum Master focus on the process is an easy explanation, however runs the risk of just facilitating meetings. Professional Scrum Masters focus on making sure Scrum and it's empirical process control is understood by the team, organisation and acts in different stances on that. Making the way for change.

Daily Scrum is often practiced standing, but not required, because that would exclude people with the inability to stand.

The Scrum board is another practice not part of Scrum. The only requirement is that Development Teams create transparency on their Sprint Backlog.

The definition of done does not state what exactly should be done. The way things are done is up to the Development Team, because that is their expertise. The Definition of Done creates transparency on what done means in terms of quality for the Development Team.

Some of these things might seem small, but the right understanding of Scrum makes a big difference in the real world. Where teams and organisations struggle to make good use of empiricism, a solid understanding of Scrum is imperative.

[johnm]

Thank you for this wonderful presentation!! You kept the video short, but it's very informative.

[ineuifity]

So cute. This is just humanogogy in action. We learn and communicate naturally this way. It only works when teams are small and talented, it doesn't scale easily, as everyone needs to be aligned to the main goal. I've personally only seen tech companies adopt scrum. They should have quoted the source of the bridge... I can't imagine a bridge being half built, collecting feedback, and being built differently. Basically gaining perspective is your ally. You need to think of as much as possible and consider all variables before the final launch, that what this workflow promotes

[timmy]

Then there is my boss, who likes to change his mind 20 times a day and gives us 'sprints' of 30 minutes.