Scrumguide 2017 update details

7 november 2017 is er een nieuwe versie uitgekomen van de Scrumguide, met vooral input van de gebruikers van Scrum. Ken Schwaber en Jeff Sutherland hebben de revisie toegelicht in een webinar.

Hieronder de wijzigingen. Vooral veel aanvullingen. Tekstuele wijzigingen laat ik even buiten beschouwing.

Definition of Scrum:
Extra (Om duidelijker te maken dat het om meer gaan dan alleen product improvement).

Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.

User of Scrum:
Een hele paragraaf extra over de brede toepassingsmogelijkheden en ervaringen met Scrum.

Scrum was initially developed for managing and developing products. Starting in the early 1990s, Scrum has been used extensively, worldwide, to:

Research and identify viable markets, technologies, and product capabilities;
Develop products and enhancements;
Release products and enhancements, as frequently as many times per day;
Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use;
and, Sustain and renew products.

Scrum has been used to develop software, hardware, embedded software, networks of interacting function, autonomous vehicles, schools, government, marketing, managing the operation of organizations and almost everything we use in our daily lives, as individuals and societies.

As technology, market, and environmental complexities and their interactions have rapidly increased, Scrum’s utility in dealing with complexity is proven daily.

Scrum proved especially effective in iterative and incremental knowledge transfer. Scrum is now widely used for products, services, and the management of the parent organization.

The essence of Scrum is a small team of people. The individual team is highly flexible and adaptive. These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architectures and target release environments.

When the words “develop” and “development” are used in the Scrum Guide, they refer to complex work, such as those types identified above.

The Scrum Team

Extra zin, om de kracht en toegevoegde waarde van het hele team te benadrukken. Ook in bijvoorbeeld portfolio besluitvorming.

The Scrum Team has proven itself to be increasingly effective for all the earlier stated uses, and any complex work.

The Development Team

Extra zin, want alleen een AF product wordt getoond tijdens de review. Iets wat niet af is, gaat terug naar de product backlog. En het gelijk een streven naar het af krijgen van een product (onderdeel). Een stok achter de deur.

A “Done” increment is required at the Sprint Review.

The Scrum Master

De eerste zin is iets aangepast qua taal. Het woordje “ensure that” is vervallen. Meer benadrukking van de supporting en promoting rol van de Scrum Master. En het woord “Value” is erbij gezet.

The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.

Scrum Master Service to the Product Owner

1 extra bullet erbij.

Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;

The Sprint

1 zin is iets aangepast. Een sprint heeft een goal (ipv een definition). En het is nu een product increment (ipv product).

Each Sprint has a goal of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product increment.

Daily Scrum

Extra nadruk op het feit dat deze elke dag moet plaatsvinden. En wat de toegevoegde waarde hiervan is.

The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work.

Meer uitleg over de structuur van de meeting en dat het Development team zelf hier vrij in is, mits het Focus aanbrengt op het realiseren van het Sprint doel.

The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. Here is an example of what might be used:

What did I do yesterday that helped the Development Team meet the Sprint Goal?
What will I do today to help the Development Team meet the Sprint Goal?
Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

Vaak krijg ik de vraag… “mag de Product Owner of stakeholders bij de Daily Scrum zijn?” Daar is nu dit antwoord op gekomen.

The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

Product Review

Kleine aanpassing in deze bullet. Er stond eerst: “He or she projects likely completion dates based on progress to date (if needed)”

The Product Owner discusses the Product Backlog as it stands. He or she projects likely target and delivery dates based on progress to date (if needed);

Kleine aanvulling in deze bullet. Er stond eerst alleen “release of the product“.

Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.

Sprint Retrospective

Extra toevoeging.

The Scrum Master ensures that the meeting is positive and productive.

En deze zin is aangevuld met “if appropriate and not in conflict with product or organizational standards”

During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done”, if appropriate and not in conflict with product or organizational standards.

Product Backlog

Extra zin.

Product Backlog items often include test descriptions that will prove its completeness when “Done”.

Sprint Backlog

Extra zin. En dit geeft nogmaals het belang van de Retrospective aan.

To ensure continuous improvement, it includes at least one high priority process improvement identified in the previous Retrospective meeting.

Increment

Extra zin.

An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal.

Definition of “Done”

Extra zin. Dat aangeeft dat de DoD zich ook Agile ontwikkeld. En dat daardoor de kwaliteit gaat toenemen en daardoor wellicht ook extra werk om te kunnen voldoen aan deze nieuw gedefinieerde kwaliteitseis.

New definitions, as used, may uncover work to be done in previously “Done” increments.

Reactie verzenden Reactie annuleren

Nieuwsbrief

Aanmelden

Actuele publicaties

Archief

Pin It on Pinterest