How to explain Scrum in less than 5 minutes?
This is the challenge that Daphne Harris, Director of Professional Scrum Trainer program, offers me. Pretty hard to explain such a great framework in such a so small account of time, and even worse in a not native language !
I’m pretty confortable with my pen and decide to do this, which is the practice I’m doing when training people to Scrum.
I have an opportunity to assist to Gunther Verheyen scrum.org class to revisit those values and practices and I have passed again the assessment to make sure that I have understand the new Guide 2020.
Please find below the home-made video of what is Scrum… in less that 5 minutes.
What is scrum?
Scrum is an open framework that enable people to deliver value in a complex context. It’s lightness and simplicity is an opportunity for openness. The limited set of rules and instructions allow people to focus on value and tackle complexity, uncertainty, unprectibility.
Scrum history is inspires by Takeuchi and Nonaka article “the new new product development game”. It’s all about product development.
Scrum includes specific accountabilities :
- Product Owner who optimizes the value of the product.
- Developers do those ideas into a releasable version of product who instills quality.
- Scrum Master who creates an environment way of collaborating. He enables teams but also the organization to be effective.
All forming the Scrum Team which is self-managed.
Scrum has 3 artefacts :
- A product backlog, which is a long term plan for the product, full of uncertainty and complexity. It’s lead by a vision of why are we building the product named product goal.
- A sprint backlog consists of a selection of work ; short term of work, decomposed into tangible activity. Only people doing the work are able too pull on the sprint backlog. Teams commit to the work to make it happened. The sprint goal is a target, a direction for the team to understand why this sprint is worthwhile.
- The increment is the version for the product. It should be at least shippable, releasable and usable by the market. And Done obviously. Done make sure that everybody has the common understanding of what is really done. It’s provide transparency.
All events of Scrum supports the process and the frequency of inspection and adaptation.
- A Sprint takes no more than 4 weeks and it’s often shorter.
- At Sprint Planinng Scrum Teams craft the Sprint goal.
- Every Day at Daily Scrum the team look forward to the newt day of work and adapt the plan for the 24 hours
- At Sprint Review, the team inspect what has been created into the sprint, taking into account new insight or change from the market and adapt to build the right stuff for the next couples of sprints.
- At Sprint Retrospective the team inspect its own collaboration, they tackle the definition of Done and take action to improve for the next Sprint.
Employing Scrum is a journey by itself… it takes time and practices to master it.