The Scrum XXOo

Scrum Description

 

Details -> https://www.scrum.org

Scrum is an iterative and incremental agile software development methodology for managing 

product development. It defines "a flexible, holistic product development strategy where a 

development team works as a unit to reach a common goal, challenges assumptions of the 

"traditional, sequential approach to product development, and enables teams to self-organize by 

encouraging physical co-location or close online collaboration of all team members, as well as daily 

face-to-face communication among all team members and disciplines in the project.

A key principle of scrum is its recognition that during production processes, the customers can 

change their minds about what they want and need , and that unpredicted challenges cannot be 

easily addressed in a traditional predictive or planned manner. As such, scrum adopts an empirical 

approach—accepting that the problem cannot be fully understood or defined, focusing instead on 

maximizing the team's ability to deliver quickly and respond to emerging requirements.

There are three core roles in the scrum framework. These core roles are those committed to the 

project in the scrum process—they are the ones producing the product (objective of the project). 

They represent the scrum team. Although other roles may be encountered in real projects, scrum 

does not define any team roles other than those described below.

 

Product owner

 

The product owner represents the stakeholders and is the voice of the customer. He or she is 

accountable for ensuring that the team delivers value to the business. The product owner writes (or 

has the team write) customer-centric items (typically user stories), ranks and prioritizes them, and 

adds them to the product backlog. Scrum teams should have one product owner, this role should not 

be combined with that of the scrum master. The product owner should be on the business side of the 

project, and should never interfere or interact with team members on the technical aspects of the 

development task. This role is equivalent to the customer representative role in some other agile 

frameworks.

 

Development team

 

The development team is responsible for delivering potentially shippable increments (PSIs) of 

product at the end of each sprint (the sprint goal). A team is made up of 3–9 individuals who do the 

actual work (analyse, design, develop, test, technical communication, document, etc.). Development 

teams are cross-functional, with all of the skills as a team necessary to create a product increment. 

The development team in scrum is self-organizing, even though there may be some level of interface 

with project management offices (PMOs).

 

Scrum master

 

Scrum is facilitated by a scrum master, who is accountable for removing impediments to the ability of 

the team to deliver the product goals and deliverables. The scrum master is not a traditional team 

lead or project manager, but acts as a buffer between the team and any distracting influences. The 

scrum master ensures that the scrum process is used as intended. The scrum master helps ensure 

the team follows the agreed scrum processes, often facilitates key sessions, and encourages the 

team to improve. The role has also been referred to as a team facilitator[16] or servant-leader to 

reinforce these dual perspectives.

 

Events

 

Sprint planning

 

At the beginning of a sprint, the team holds a sprint planning event: that:

● Communicates the scope of work likely during that sprint (aka team velocity)

● Selects product backlog items that likely can be done

● Prepares the sprint backlog that details the work needed to finish the selected product 

backlog items, with the entire team

● Sets a four-hour time planning event limit for a two-week sprint (pro rata for other sprint 

durations) 

● During the first half, the whole team (development team, scrum master, and 

● During the second half, the development team decomposes the work (tasks) 

product owner) agree what product backlog items to consider for that sprint

required to deliver those backlog items, resulting in the sprint backlog

Once the development team prepares the sprint backlog, they commit (usually by voting) to deliver 

tasks within the sprint.

 

Daily scrum

 

Each day during a sprint, the team holds a daily scrum (or stand-up) with specific guidelines:

● All members of the development team come prepared. The daily scrum...

● ...starts precisely on time even if some development team members are 

● ...should happen at the same time and place every day

● ...is limited (timeboxed) to fifteen minutes

missing

● Anyone is welcome, though normally only scrum team roles contribute.

● During the daily scrum, each team-member answers three questions:

● What did I do yesterday that helped the development team meet the sprint 

● 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 

goal?

 

meeting the sprint goal?

Any impediment (stumbling block, risk or issue) identified in the daily scrum should be captured by 

the scrum master and displayed on the team's scrum board, with an agreed person designated to 

working toward a resolution (outside of the daily scrum). No detailed discussions should happen 

during the daily scrum.

Sprint review and sprint retrospective

At the end of a sprint, the team holds two events: the sprint review and the sprint retrospective.

At the sprint review, the team:

● Reviews the work that was completed and the planned work that was not completed

● Presents the completed work to the stakeholders (a.k.a. the demo)

Guidelines for sprint reviews:

● Incomplete work cannot be demonstrated

● The recommended duration is two hours for a two-week sprint (pro-rata for other sprint 

durations)

At the sprint retrospective, the team:

● Reflects on the past sprint

● Identifies and agrees continuous process improvement actions

Guidelines for sprint retrospectives:

● Two main questions are asked in the sprint retrospective: What went well during the 

sprint? What could be improved in the next sprint?

● The recommended duration is one-and-a-half hours for a two-week sprint (pro-rata for 

other sprint durations)

● This event is facilitated by the scrum master

How Team used Scrum -> task planning using planning poker, effective job division.

Affects -> clear work organization, more efficient at work progress