Summary Scrum Guide 2020

Scrum

Scrum is being used pattern, process and insight that fit the scrum framework.

Scrum is a light weight framework that helps people, team and organization generation value through adoption solution for complex problem.

Scrum require scrum master to faster an environment

·       Product owner order the work for a complex problem into a product backlogs.

·       The scrum team turns a selecting of work into an incremental work during sprint.

·       The scrum team and product owner inspect the results and adjust for next sprint.  

·       Repeat

 

Scrum Theory:

·       Scrum is a fundamental of empiricism and lean thinking.

·       Scrum employs iterative, incremental approach to optimized the predictability and control the risk.

·       Scrum combine 4 formal events for inspection and adaptation.

·       The event works because they implement the empirical scrum pillar of

o   Transparency

§  Work must be visible

§  Low transparency led to decision that diminish value and increase risk

o   Inspection

§  Scrum artifact and progress toward goal must be inspected frequently to detect undesirable variance and problem.

o   Adaptation  

§  If anything is deviated or any results is unaccepted, the process must be adopted.

§  It minimizes further deviation

 

Scrum value:

CCFOR:

C=Commitment

C=Courage

C=Focus

O=Openness

R=Request

 

The scrum team and stakeholder are open about the work and the challenges.

 

Scrum Team:

The scrum team consist of

·       One scrum master

·       One product owner

·       Developers

 

Ø In the scrum team, there is no sub-team or hierarchies.

Ø Focus on object at a time, the product goal.

Ø Scrum team is cross-functional, meaning that team member has all the skill to create the value.

Ø Self-managing internally, who does what, when and how.

Ø Typically, 10 or few people

Ø Cohesive scrum team

Ø Scrum team responsibility for product related activities from stakeholder collaboration, verification, maintenance, operational, experimental and research and development. 

Ø Scrum define 3 specific responsibilities within the scrum team

a.     The developer

b.    Product owner

c.     Scrum master

 

Developer:

·       Creating a plan for sprint and sprint backlogs

·       Adopting the plan

·       Holding each other accountability

 

Product owner:

·       Product owner is accountable to maximize the value of the product resulting from the scrum team.

·       Product owner accountable to manage product backlog that includes

o   Explicitly communicating the product goal

o   Clear communicating product goal

o   Ordering product backlog

o   Ensure that product backlog is transparent, visible and understood.

·       Product owner may delegate the responsibility but product owner will remain accountable.

·       Product owner is one person not the committee.

·       Product owner represent the need of the stakeholder in the product backlog.

 

Scrum Master:

·       Scrum master is accountable for establishing scrum. They do within the scrum team and organization.

·       Scrum master is accountable for team effectiveness and do practice scrum using scrum framework.

·       Scrum master are true leader to serve scrum team and organization.

 

Scrum master serve three major responsibilities:

·       Scrum master serves scrum team

o   Coaching, do self-management and cross-functionality

o   Help team to create high value increment that meet the definition of done.

o   Remove the impediments

o   Ensure that event take place are positive, productive and kept within timebox.

·       Scrum master serves product owner

o   Helping finding technique defining product goal and product backlogs management.

o   Helping scrum team to understand clear and concise need of product backlog items with product owner.

o   Helping establish empirical product planning for complex environment.

o   Facilitating stakeholder collaboration as request.

·       Scrum master serves organization

o   Leading, training and coaching scrum in the organization

o   Adopt scrum practice

o   Plan and implementing scrum

o   Helping employee and stakeholder understand

o   Removing barriers between stakeholder and scrum team.

 

Scrum events:

·       Sprint is a container for all the event.

·       Event are held to reduce the complexity

 

Sprint:

·       Sprint is the heartbeat of scrum where idea turn into value

·       sprint is fixed length event 1 month or less

To achieve the product goal that includes

·       Sprint planning

·       Daily scrum

·       Sprint review

·       Sprint retrospective

During the sprint:

·       No change is made

·       Quality does not decrease

·       Product backlog refines as needed

·       Scope may be clarified and renegotiated with the product owner

 

 

Ø Sprint enable predictability by ensuring inspection and adaptation of progress of product goal at least every calendar month.  

Ø If sprint horizon is too long, the sprint goal is valid.

Ø Shorter sprint generate value, limit risk, cost and effort to smaller time frame.  

Ø Each sprint called short project

Ø Burn-downs and burn-ups show/forecast the progress

Ø Sprint goal cancel if sprint goal is obsolete. Product owner have right to cancel it.

 

Sprint planning:

·       Sprint team may invite other people in the sprint planning to give advice.

Sprint planning contain the below topics:

Topic-1: why sprint is valuable?

·       Product owner propose how product could increase value.

·       Scrum team define sprint goal and sprint is valuable to the stakeholder.

·       Sprint goal must be finalized before the sprint planning.

Topic-2: what can be done in the sprint?

·       After discussing with the product owner, developer select the item from the product backlog and put into the current sprint.

·       Developer set items to work

Topic-3: how the chosen work can be done?

·       Developer plans the work, create an increment that meet the definition of done.

·       Make product backlog items into smaller work items.

·       How will be done is solely responsible to the developer

·       Sprint backlog = product backlog items selected + sprint plan for delivery

·       Sprint planning max 8 hours for a month sprint.

·       For shorter sprint, event is shorter

 

Daily Scrum:

·       Inspect progress toward goal

·       15 minutes event for the developer happen in the same time and same place.

·       Product owner and scrum master participate as developer

·       Developer selects technique and structure they want

·       Create focus and do self-management

·       Daily scrum improve communication, identify impediment and take quick decision if require.

 

Sprint Review:

·       Inspect outcome of the sprint

·       Scrum team present the result to stakeholder

·       Scrum team and stakeholder review what was completed

·       Maximum 4-hour timebox for a month sprint

 

Sprint Retrospective:

·       Increase quality and effectiveness

·       It discusses last exercise such as what went well, what can be adopted, what problem encountered and how it has resolved.

·       It concludes the sprint. Maximum 3 hour for a month sprint.

 

Scrum artifact:

·       It represents work or value.

·       It is designed to maximized the information.

o   For product backlogs, it is product goal

o   For spring backlogs, it is sprint goal

o   For increment, it is definition of done

 

Product backlogs

·       It is an order list. What need to be done for the product.

·       It is single source for the scrum team.

·       Developer is responsible for sizing of the product backlogs.

Commitment: Product goal

·       A product is vehicle to deliver value.

·       It has clear boundary, stakeholder and customer

 

Sprint backlogs:

Why: sprint backlogs are composed of spring goal.

What: product backlog item selects for sprint backlog

How: actionable plan to delivery the items

Commitment: sprint goal.

·       A single objective for the sprint

 

Increments:

·       It is stepping stone towards product goal.

·       Multiple increment may be created within the same sprint.

·       Total/sum increment are present in the sprint review.

·       We cannot say increment until it meets definition of done.

·       Increment may be delivered prior to end of sprint

Commitment: Definition of Done

·       It is formal description of increment when it meets the product quality

·       When product backlogs item meets the Definition of Done, then an increment born.

·       If the product backlogs item does not meet the definition of done, item will not be release in the sprint review. Instead, item will move to product backlogs for future consideration.