From the course: Scrum: The Basics

Scrum: The leading project methodology

From the course: Scrum: The Basics

Start my 1-month free trial Buy for my team

Scrum: The leading project methodology

“

- Scrum wants you to fail. In fact, it's known for the slogan, "Fail fast." No, I'm not joking. I realize it sounds weird, but there's a very good reason for this. Traditionally, project managers and developers would work for months or years before seeing the results. Most of the time, around 80% in fact, the software and projects failed. So, why, you might ask, are they signing up for more failure? Well, really they're not. The trick is in focusing on the second word, fast. Failure is okay, as long as you're learning from it, but if you have to wait too long, you're not going to learn nearly as much from it. Scrum takes the agile manifesto and its key principles and boils them down to a very simple framework that encourages small scale focus and rapid learning cycles. That's what fail fast really means, learn fast. With that in mind, the basics of the framework are designed to encourage that fast feedback loop. The scrum framework is not prescriptive. We generally refer to it as guardrails, like the ones you see on the highway. Those guardrails don't tell you exactly where to drive in the lane, but they keep you within the boundaries that will result in a successful road trip. Scrum is much the same. With the agile principles as the guideposts and a loose framework of activities executed on a regular, short schedule, your project will be get up for success. In a nutshell, here's the scrum framework in its simplest form. To start, the product owner has a prioritized backlog of work for the team to do. Every two weeks or so, the team looks at the backlog and decides what they can accomplish in the next two weeks. The team develops and tests their solution to the backlog items until they're done and ready for use. At the end of the two weeks, the team demonstrates their accomplishments to the product owner and stakeholders. Finally, they reflect on how things went during the two weeks and they decide what they can do to improve their work practices. That's it. The short timeframe and the focus on a completed product at the end forces the the team to fail fast or more appropriately, learn fast.

Contents