Thence, Scrum identifies 3 pillars as the basis of its utilization. Scrum is based on an empirical model, where continuous learning comes from experimentation and, therefore, decision making is taken according what we have learnt.
Which are them? What is not seen in Scrum We usually skip the foundations and more important components of this framework. The issue is that Scrum is not only a team, events and artifacts, it’s much more than that. Lightweight and simple to understand? Probably. More information about Scrum team, events and artifacts on The Scrum Guide. Scrum team: The Product Owner, the Dev Team and the Scrum Master.Įvents: Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective (and sometimes backlog groomings or refinements).Īrtifacts (or elements): Product Backlog, Sprint Backlog and product increment. When che cking Scrum-related stuff on internet, on many of the events, courses and workshops we attend, or just in conversations about this framework in our daily basis, among various other instances, we find that Scrum is usually described as a framework composed by this: How is something lightweight and simple to understand but also difficult to master? What is it that Scrum is a framework tough to dominate? How do we describe Scrum? There are 3 short characteristics that describes the framework, according the Scrum Guide. The use of Scrum as a framework to deliver continuous value to our clients has been hugely increasing during the last years in different types of organizations in the world ( VersionOne 12th Annual State of Agile Report), offering the chance to create innovative solutions in highly uncertain, complex and changing environments.