The Scrum Guide recently received an update in November 2017. Before the official version is released in French, I offer you a first translation of the changes made between 2016 and 2017 as well as the paragraphs concerned.
The main topics covered are:
- Uses of Scrum
- Refining the role of Scrum Master
- Details on the Daily Scrum, Time-boxes and Sprint Backlog
Note: you can find the original information in the Scrum reviews.
1. Uses of Scrum
Scrum was originally developed to manage and develop products. Born in the early 90s, Scrum has been widely used around the world, for:
- Research and identify viable markets, technologies and product capabilities;
- Develop products and improvements;
- Deliver products and improvements, several times a day;
- Develop and support Cloud (online, secure, on-demand) and other operational environments for product usage; And,
- Maintain and renew products.
Scrum has been used to develop software, hardware, embedded software, networks of interacting functions, autonomous vehicles, schools, governments, marketing, managing the operations of organizations and almost everything else. uses in our daily lives, as individuals or societies.
As technology, market, and environmental complexities and their interactions have rapidly increased, the usefulness of Scrum in managing complexity is proven day after day. Scrum has proven especially effective in iterative and incremental knowledge transfer. Scrum is now widely used for products, services, and parent organization management. The essence of Scrum is a small team of people. The individual team is highly flexible and adaptable. These forces continue to operate alone, together, and in networks of teams that develop, deliver, operate, and maintain the work and products of thousands of people. They collaborate and interoperate in sophisticated development architectures and target delivery environments.
When the words “develop” and “development” are used in the Scrum Guide, they refer to complex work, such as those types identified above.
2. The role of Scrum Master
The text now describes:
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand the theory, practices, rules, and values of Scrum.
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside of the Scrum Team to understand which interactions – with the Scrum Team – are useful and which are not. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
3. The Scrum Master at the service of the Product Owner
Addition of :
He makes sure that the goals, scope, and product area are understood by everyone on the Scrum Team as well as possible.
4. Daily Scrum – Daily Scrum
Update to first paragraph:
The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum takes place every day of the Sprint where the Development Team plans the work for the next 24 hours. This optimizes team collaboration and performance by inspecting work since the last Daily Scrum and forecasting work for the next Sprint. Daily Scrum takes place at the same time and place every day to reduce complexity.
5. Daily Scrum Objectives
The structure of the meeting is defined by the Development Team and can be conducted in different ways if it focuses on progress towards the Sprint Goal. Some Development Teams will use questions, others will be more discussion-based. Here is an example of what could be used:
- What did I do yesterday that helped the Development Team reach the Sprint Goal?
- What am I going to do today to help the Development Team reach the Sprint Goal?
- Do I see impedimentas preventing me or the Development Team from reaching the Sprint Goal?
6. Time-Boxes
Using the words "maximum" to remove any question that the timebox for Events means maximum length, but can be shorter.
7. Sprint Backlog
To ensure continuous improvement, it includes at least one high priority item on how the team will work, identified in the previous Retrospective meeting.
8. Increment
An Increment is an inspectable set of “Done” work that supports empiricism at the end of the Sprint. The increment is a step towards the vision or goal.
Additional resource
A article (eng) of Stacey Louie summarizing updates to the 2017 Scrum Guide.
