# Scrum

> **Note:** Have the same definition of Done
>
> ### Values
>
> * Commitment
> * Courage
> * Focus
> * Openness
> * Respect
> * Transparency

## Roles

* Product Owner (1 ppl):
  * Clearly expressing Product Backlog items;
  * Ordering the items in the Product Backlog to best achieve goals and missions;
  * Optimizing the value of the work the Development Team performs;
  * Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
  * Ensuring the Development Team understands items in the Product Backlog to the level needed.
* Development Team (2 < x < 10 ppl):
  * Clearly expressing Product Backlog items;
  * Ordering the items in the Product Backlog to best achieve goals and missions;
  * Optimizing the value of the work the Development Team performs;
  * Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
  * Ensuring the Development Team understands items in the Product Backlog to the level needed.
* Scrum Master:
  * The Scrum Master’s job is to work with the Scrum Team and the organization to increase the transparency of the artifacts.
  * To the Product Owner:
    * Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;
    * Finding techniques for effective Product Backlog management;
    * Helping the Scrum Team understand the need for clear and concise Product Backlog items;
    * Understanding product planning in an empirical environment;
    * Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
    * Understanding and practicing agility; and,
    * Facilitating Scrum events as requested or needed.
  * To the Development Team:
    * Coaching the Development Team in self-organization and cross-functionality;
    * Helping the Development Team to create high-value products;
    * Removing impediments to the Development Team’s progress;
    * Facilitating Scrum events as requested or needed; and,
    * Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.
  * To the Organization:
    * Leading and coaching the organization in its Scrum adoption;
    * Planning Scrum implementations within the organization;
    * Helping employees and stakeholders understand and enact Scrum and empirical product development;
    * Causing change that increases the productivity of the Scrum Team; and,
    * Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

## Events

* Sprint(a time-box, max one month, during which a “Done”, useable, and potentially releasable product Increment is created):
  * No changes are made that would endanger the Sprint Goal;
  * Quality goals do not decrease; and,
  * Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
  * A Sprint would be cancelled if the Sprint Goal becomes obsolete (Uncommon and traumatic).
  * Main concerns:
    * What can be delivered in the Increment resulting from the upcoming Sprint?
    * How will the work needed to deliver the Increment be achieved?
  * Development Team can assess what it can accomplish over the upcoming Sprint (from the backlog).
  * Sprint Goal should be discussed by the scrum team.
  * Work should be decompose to units of one day or less.
* Daily (15minutes) Responsible Scrum Master:
  * Plans next 24hr work.
  * Track progress.
  * Guide:
    * What did i do yesterday towards the sprint goal.
    * What will i do today towards the sprint goal.
    * Any impediments towards sprint goal.
* Sprint review (max 4hr results in a reviewed product backlog) Responsible Scrum Master:
  * Detail what is done
  * What is not
  * Detail insights, problems and solutions.
  * Check the increment
  * Most valuable thing to do next
  * Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.
* Sprint retrospective
  * Improve work processes
  * Adapt "Done" definition

## Artifacts

* Product backlog (Product Owner):
  * Ordered list of every needed item in the product
  * Each item:
    * Description
    * Order (Higher the sooner is going to be done)
    * Estimate (By the people that is going to perform the work)
    * Value (Sum up sprint values for track performance)
    * Test descriptions
* Sprint backlog:
  * What is going to be done in the sprint.
  * It includes at least one high priority process improvement identified in the previous Retrospective meeting.
  * As new work is required, the Development Team adds it to the Sprint Backlog.