GET THE PICTURE

Scrum Sum Up...

Scrum was born in the 1990’s.
The first version of the Scrum Guide emerge in 2010.
Scrum is a basic structure (framework) with guidelines to help us organize work to maximize value for customers.
Each element of the framework has a purpose, don’t try to do Scrum in other way.

Scrum is ...

Lightweight, easy to understand and hard to master.
Like it’s written in the Scrum Guide: “Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.”
Scrum is a framework, a basic structure with guidelines to help organize our work in order to maximize value for the Customer. It’s composed of 3 pillars, 5 values, 3 roles, 5 events (4 formals), and 3 artifacts. 
Uses a team approach and each element has a specific role.  Is based on empiricism that states that knowledge comes from experience and decision-making based on what is observed, and lean thinking that seeks to reduce waste and focuses on the essentials. Scrum employs an iterative and incremental approach to optimize predictability and to control the risk.

Pillars

There is 3, TRANSPARENCY, INSPECTION AND ADAPTATION.
Transparency aims to let everyone know what is happening. The process used by the team, activities and expectations should be visible to all interested parties reflected in their 3 artifacts. Transparency enable and allow inspection. 
The Inspection take place on a regular basis, where there is verification of the work performed; the team evaluates whether you are on the right track and analyses whether you can improve or improve your working method, team environment and product quality. The inspection enables and allow adaptation. Following the inspections that occurred throughout the cycle, there is adjustment, that is, Adaptation of processes as early as possible, in order to minimize risks, towards an Objective.

Values

There is 5, COMMITMENT, FOCUS, COURAGE, RESPECT AND OPENNESS.
The team is committed to achieving its goals and supporting each other. The main focus is Sprint’s work toward a goal.
Team members have the courage to do the right thing and work on difficult problems. 
There is respect between the team and with every one else.
The team and its stakeholders are open about work and challenges.

 

The Team

A Scrum Master, a Product Owner and Developers
ü  It is a cohesive unit of professionals, focused on a goal.
ü  Multifunctional, i.e. with all the skills to create value in each sprint and self-organized, which means that they decide internally who does what, when and how.
ü  Small enough to remain agile and large enough to complete meaningful work within a Sprint, typically 10 or fewer people.
ü  In scrum teams there are no sub teams or hierarchies.

 

Product Owner

  • Defines the product view.
  • Responsible for maximizing the value of the product resulting from the work of the developers.
  • Responsible for managing the
    Product     backlog.
  • Defines priorities.
  • Anticipates the needs of customers.
  • Evaluates product progress with
    each     iteration.
  • Ensures that the Product Backlog is visible, transparent and clear to all.

Scrum Master

  • Establishing Scrum as defined on the Scrum Guide.
  • Establish an environment where the team can be efficient.
  • Ensure good environment and good relations within the team, as well as with others outside the team.
  • Protect the team from distractions and external interruptions.
  • Ensure that all Scrum events take place and are positive, productive  and maintained within the expected time.

Developers

  • Self-organized.
  • Focused on delivery quality.
  • With all the skills needed to create a usable increment in each sprint.
  • Dedicated to the project, adapting daily, if necessary, their plans towards the sprint goal.
  • Creating a plan for the Sprint – Sprint Backlog.
  • Includes developers, testers, designers, UX experts and DevOps engineers.

Events

Ultimately there is 5 events, the Sprint is the main event. He contains the other 4 formal events, the Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. 
The Sprint are “the heartbeat of Scrum”, it’s fixed length – one month or less. 

Sprint Planning

  • Sprint Planning starts the Sprint, determining the work to be done for it.
  • PO describes the goal of Sprint and presents the features you want to be developed. 
  • The sprint plan is drawn up collaboratively by the entire team.
  • Items are removed from the Product Backlog and placed on the Sprint Backlog.
  • There must be a Sprint Goal: goal for the Sprint to keep the team focus.
  • Sprint Planning is limited to a maximum of eight hours for a one-month Sprint. 
  • For smaller Sprints, the event is usually shorter.

Sprint Review

  • The Sprint Review is the second to last event of the Sprint, the Team show what was achieved – the increment for inspection.
  • Feedback is obtained from user and stakeholders.
  • Progress towards the objectives of the Product goal is discuss.
  • Updates or changes the backlog based on feedback.
  • Participants are the Scrum Team (PO, SM and Developers), users and stakeholders.
  • It has a 4 hour Time Box event for a one-month Sprint.
  • For smaller Sprints, the event is usually shorter.

Daily Scrum

  • Daily Meeting for developers, the goal is to inspect the progress toward the Sprint Goal, and if it’s necessary adapt and adjust.
  •  We discuss progress, what we have already achieved and whether there is any impediment.
  • Should not be used to troubleshooting: issues raised should be addressed after the meeting and usually with a smaller forum.
  • Time box of 15 min.  It should be carried out at the same place and the same time in order to reduce complexity.
  • Dailies improve communications, identify impediments, promote quick decision-making and consequently eliminate the need for other meetings.

Sprint Retrospective

  • Last sprint event, aiming to plan ways to increase quality and effectiveness. 
  • The goal is to plan ways to increase quality and effectiveness.
  • Determine what went well (with recommendation to continue to happen); which can be improved and identify the actions that must be taken to improve the functioning of the Team.
  • The most impactful improvements are addressed as soon as possible, preferably in the next Sprint.
  • It has a 3 hour Time Box event for a one-month Sprint. 

Note: Refinement is not a formal event on Scrum, it’s an ongoing work that ensure backlog remains populated with relevant, detailed, and prioritized items. Prioritize, clarify, and detail the Items that will be part of the planning of the next Sprint. Serves to remove items from the Backlog that are no longer relevant. 

Artifacts

“Scrum artifacts represent work or value”.
Designed to maximize transparency so that they have the same understanding and when inspecting them have the same basis for adaptation. Each artifact contains a commitment to ensure that it provides information that increases transparency and focus, against which progress can be measured:
● For the Product Backlog it is the Product Goal,
● For the Sprint Backlog it is the Sprint Goal, and
● For the Increment it is the Definition of Done.

Product Backlog

  • Emerging and ordered list of what is needed to improve the product.
  • Only source of work carried out by the team. 
  • It is a living artifact, it is dynamic and evolves.
  • The Product Owner is responsible for its content, availability, order and prioritization.
  • The first entries contain the items that have the most detail, with the best-defined requirements and with the highest priority.

Sprint Backlog

  • List of tasks that developers propose to do in a Sprint. 
  • The Sprint Backlog is then composed of the Sprint Goal which is why, the set of Backlog Product items selected for the Sprint that represents what, and an actionable plan for increment delivery (how).
  • Items are taken from the Product Backlog by the team, based on the priorities defined by the PO and the perception that developers have to develop them within the Sprint.

Increment

  • An Increment is a concrete step toward the Product Goal.

  • An Increment is a piece of the product, functional and that can potentially be delivered.

  • The increment(s) is(are) presented in the Sprint Review.




Product Goal
A future state of the Product;
The long-term objective for the Team.

Sprint Goal
The objective for the Sprint;
Keep the Team focused.

Definition of Done
“Is a formal description of the state of the Increment when it meets the quality measures required for the product”

In a simple way...

The Product Owner creates and prioritizes a list of items we call Product Backlog.
In Sprint Planning, the team will pick up a small portion of the Product Backlog, this small part is called the Sprint Backlog, which are the items that Developers plan to accomplish during the Sprint.
After the work and the goal for the Sprint is defined, the team meets every day to evaluate progress towards the goal, this meeting is called Daily Scrum.
During the Sprint the Scrum Master keeps the team focused on its goal and helps remove impediments and obstacles that arise. 
At the end of the Sprint the Increment must be something ready and functional, in order to be usable by the Customer.
The Sprint ends with the Sprint Review – where sprint work is inspected – and Sprint Retrospective – where the team inspects and plans ways to increase quality and
effectiveness.

And the cycle resumes…