Scrum guide

Scrum (Scrum.org) - Ken Schwaber and Jeff Sutherland February 2010 1 Scrum has been used to develop complex products since the early 1990s. This paper describes how to use Scrum to build products. Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques. The role of Scrum is to surface the relative efficacyof your development practices so that you can improve upon them while providing a framework within which complex products can be developed. Theory 2 Scrum, which is grounded in empirical process control theory, employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control. The first leg istransparency 3 Transparency ensures that aspects of the process that affect the outcome must be visible to those managing the outcomes. Not only must these aspects be transparent, but also what is being seen must be known. That is, when someone inspecting a process believes that something is done; it must be equivalent to their definition of done. The second leg is inspection 4 The various aspects of theprocess must be inspected frequently enough so that unacceptable variances in the process can be detected. The frequency of inspection has to take into consideration that all processes are changed by the act of inspection. A conundrum occurs when the required frequency of inspection exceeds the tolerance to inspection of the process. Fortunately, this doesn’t seem to be true of software development.The other factor is the skill and diligence of the people inspecting the work results. The third leg is adaptation 5 If the inspector determines from the inspection that one or more aspects of the process are outside acceptable limits, and that the resulting product will be unacceptable, the inspector must adjust the process or the material being processed. The adjustment must be made as quicklyas possible to minimize further deviation. There are three points for inspection and adaptation in Scrum. The Daily Scrum meeting is used to inspect progress toward the Sprint goal, and to make adaptations that optimize the value of the next work day. In addition, the Sprint Review and Planning meetings are used to inspect progress toward the Release Goal and to make adaptations that optimize thevalue of the next Sprint. Finally, the Sprint Retrospective is used to review the past Sprint and determine what adaptations will make the next Sprint more productive, fulfilling, and enjoyable.

Traducción del Scrum Guide - February 2010 - Ken Schwaber and Jeff Sutherland David Arteaga Scrum se usa para desarrollar productos complejos desde principios de los 90. Este documento describe cómo usarScrum para construir productos. Scrum no es un proceso o una técnica para construir productos; mas bien es un marco de referencia en el cual podemos emplear distintos procesos y técnicas. El rol del Scrum es destacar la eficiencia relativa de sus prácticas de desarrollo de modo que podamos mejorarlas y a la vez proporcionar un marco de referencia para desarrollar productos complejos. Teoría ElScrum, que se basa en la teoría del control de proceso empírico, emplea un enfoque iterativo, incremental para optimizar la predictibilidad y el control del riesgo. Tres pilares sostienen cada implementación del proceso de control empírico. El primer soporte es la transparencia La transparencia asegura que los aspectos del proceso que afectan el resultado deben ser visibles a aquellos que gestionanlos resultados. No sólo estos aspectos deben ser transparentes sino también que, lo que se ve debe ser conocido. Es decir, cuando alguien que inspecciona un proceso cree que algo está hecho, esto debe ser equivalente a su definición de hecho. El segundo soporte es la inspección Los distintos aspectos del proceso deben ser inspeccionados frecuentemente de modo que las variaciones inaceptables en...