Hi, I'm Mike Cohn. Welcome to Scrum Foundations. One of the first things you need to understand about Scum is that we tend to think of it as a framework rather than a methodology or process. What's the difference? A methodology of process is much more complete. A Methodology or Process will specify essentially everything about how work should be performed when using that approach. For example, a methodology might specify exactly how testing and quality assurance should be performed. Or it might specifiy how a team should go about gathering requirements for a new product. A framework, on the other hand, is purposefully incomplete. Scrum, for example, has an artifact called the Product Backlog, which is essentially a prioritized requirements list. Scrum is absolutely silent on how the product backlog comes into existence. It could be delivered to the team by little green men on a spaceship, as far as Scum Similarly, Scrum says a team needs to produce high-quality work, but doesn't say how the team is to achieve that. Things like these are left to the Team because a Team owning its own process is a critical success factor for Scum. A Team is going to be much more bought into a way of working if they contribute to determining that way working. So, Scrum is a deliberately incomplete framework to which each team adds whatever is necessary given that team's context. Scum takes the position that the team knows best how it should work and provides tremendous flexibility for teams to choose what needs to be added to make the Sc rum framework into an appropriate methodology for that teams work. I want to caution you, however, about removing things from a scrum. As a framework, scrums are very small, but the things that are there have been shown to work over and over again. Be very careful about deciding to remove something, especially before you have sufficient experience to make very educated guesses about how removing something from scrumb would affect the other parts of scrumm. In a nutshell, Scrum is a series of events that happen over a defined period of time called a sprint. Those events are repeated every sprint If Scum is so simple, why is it so difficult to implement? Because it's fundamentally different than how most of us are used to working. It's a change. And change is hard.