Scrum

Input of Sprint Planning Meeting

1. Product Backlog 2. The latest Product Increment 3. Projected capacity of the Development Team during the Sprint 4. Past performance of the Development Team

Impediment

A hindrance or obstruction to doing something. Frequently used to describe some issue or blocker that is preventing a team or organization from performing Scrum in an effective way.

Scrum of Scrums

A meeting held each day, normally after the daily scrum. These meetings allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration. A designated person from each team attends.

Fibonacci Sequence

By definition, the first two numbers in the Fibonacci sequence are 0 and 1, and each subsequent number is the sum of the previous two. 0, 1, 2, 3, 5, 8...

Daily Scrum

Daily Scrum is a synchronization, inspection, and adaptive planning activity that a development team performs each day. This core practice in the Scrum framework is time-boxed to no more than 15 minutes.

Definition of Done (DoD)

DoD is a comprehensive checklist of necessary, value-added activities that assert the quality of a feature. It captures activities that can be committed by the team to be completed at each level (feature, sprint, release). DoD is not static and shared understanding among the team on what 'done' means. It is also used as an auditable checklist.

Empirical Process

Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Scrum is founded on empirical process control theory, or empiricism.

Scrum Master

Ensure that the value, practices, and rules of Scrum are understood and followed.

Development Team

Generates value for the customer, building high-quality product increment. The Development Team is responsible for selecting the number of items for the sprint from the Product Backlog.

Backlog Grooming Meeting

Meetings should 3 be longer than an hour Meeting does not include breaking stories into tasks The team can decide how many meetings are needed per week.

Managers

People who control the environment in which the scrum development takes place.

Planning Poker

Planning Poker, also called Scrum poker, is a consensus-based technique for estimating effort for user stories, mostly used to estimate effort or relative size of user stories in software development. Estimating is initially anonymous to avoid undue influence / bias. Estimates tend to be less optimistic and more accurate than task estimates mechanically combined (via some formula).

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. Writes and Prioritizes customer-centric user stories to add to the product backlog. There should be one product owner per team.

Sprint Review Meeting

Review the work that was completed and not completed; Present the completed work to the stakeholders (a.k.a. the demo); Incomplete work cannot be demonstrated; Four-hour time limit The success of the sprint will later be assessed during the Sprint Review Meeting against the sprint goal, rather than against each specific item selected from the product backlog.

Core Team Roles (Pigs)

Roles that involved with producing the product (pigs, committed to putting their bacon on the line!). Includes Product Owner, Development Team and Scrum Master.

Scrum & Uncertainty

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.

Co-location and Self-organization

Scrum enables the creation of self-organizing teams by encouraging co-location of all team members, and verbal communication between all team members and disciplines in the project.

Scrum

Scrum is a management framework for incremental product development using one or more cross-functional, self-organizing teams and provides a structure of roles, meeting, rules and artifacts.

Servant Leadership

Servant-leaders achieve results for their organizations by giving priority attention to the needs of their colleagues and those they serve. Servant Leadership can be most likely associated with the participative management style. the practice of a participative leadership style involves employees in decision-making. More extensive tasks are delegated.

Planning Poker Cards

Sets of cards with estimation numbers on, one deck per person. Sometimes use a Fibonacci sequence to represent the relative uncertainty of estimating larger numbers.

Sprint Backlog

Sprint backlog is the set of items from the product backlog that were selected for a specific sprint. The sprint backlog is accompanied by a plan of how to achieve the sprint goal. It is highly visible view of the work being undertaken and may only be updated by the Development Team.

Scrum Ceremonies

Sprint planning > Daily Scrum > Sprint Review > Sprint Retrospective

Sprint

Sprints last between one week and one month, and are a "timeboxed" (i.e. restricted to a specific duration) effort of a constant length. A sprint is the basic unit of development.

Sprint Planning Meeting

The Sprint Planning Meeting is divided into two main sessions, the main topic discussed in each one are: What can be done this Sprint? How will the chosen work get done? Select what work is to be done; Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team; Identify and communicate how much of the work is likely to be done during the current sprint Eight-hour time limit (1st four hours) Entire team : dialog for prioritizing the Product Backlog; (2nd four hours) Development Team : hashing out a plan for the Sprint, resulting in the Sprint Backlog

Ancillary Team Roles (Chickens)

The ancillary roles in Scrum teams are those with no formal role and infrequent involvement in the Scrum process (only during sprint reviews) —but nonetheless, they must be taken into account. Includes stakeholders such as customers and managers.

Product Increment

The product increment is the sum of all the product backlog items completed during the sprint and all previous sprints. At the end of a sprint, the new increment must be "done," which means it must be in useable condition and meet the Scrum team's definition of "done." It must be in useable condition regardless of whether the product owner decides to actually release it.

Sprint Retrospective

The purpose of Sprint Retrospective is Inspect how the last Sprint went with regards to people, relationships, process, and tools. Identify and order the major items that went well and potential improvements. Create a plan for implementing improvements to the way the Scrum Team does its work. Event should be limited to a three hour time limit.

Stakeholders

The stakeholders are the customers, vendors. They are people who enable the project and for whom the project produces the agreed-upon benefit[s] that justify its production. They are only directly involved in the process during the sprint reviews.

Scrum Artifacts

There are many artifacts team can generate, the three main artifacts of Scrum are: 1. Product Backlog 2. Sprint Backlog 3. Increment

Backlog Grooming Storytime

This is the process of estimating the existing backlog using effort, refining the acceptance criteria for individual stories, and breaking larger stories into smaller stories.

Scrum Pillars

Three pillars uphold every implementation of empirical process control: TRANSPARENCY - Giving visibility to those responsible INSPECTION - Timely checks of progress and deviation ADAPTATION - Adjusting team process to minimize issues

Planning Poker Procedure

User story explained by product manager; estimators can discuss scope but not numbers; estimators lay down cards and reveal them all at once; high/ low estimators justify choices; Consensus is moderated with bias towards potential owner of work.

Daily Scrum Questions

What did you do yesterday? What will you do today? Are there any impediments in your way? It is the role of the Scrum Master to facilitate resolution of these impediments, although the resolution should occur outside the Daily Scrum itself to keep it under 15 minutes.

Definition of Ready (DoR)

What does it mean to be ready? DoR describes a state of product backlog items which they must be in order for them to be eligible for discussion on the sprint planning meeting.

Scrum of Scrums Questions

What has your team done since we last met? What will your team do before we meet again? Is anything slowing your team down or getting in their way? Are you about to put something in another team's way?