PSPO I

professional scrum product owner

Scrum

lightwork framework that helps teams generate value through adaptive solutions for complex problems

Product Owner accountability

accountable for maximizing the value of the product

Product Owner responsibilities

• developing and communicating the product goal

• creating and clearly communicating product backlog items

• ordering the product backlog

• ensuring the product backlog is transparent and understood

Scrum Master accountability

accountable for for establishing scrum

Scrum Master responsibilities

• coaching the scrum team

• helping remove impediments

• facilitating scrum events

• helping the organization understand scrum

Developers accountability

accountable for creating a usable increment every sprint

Developers responsibilities

• creating sprint backlog

• planning the work

• maintaining quality

• adapting the plan daily

Sprint

• one month or less

• fixed length

• creates a usable increment

• container for all other events

Sprint Planning purpose

decide what will be built and how

Sprint Planning outputs

• sprint goal

• selected product backlog items

• initial sprint backlog

Daily Scrum length

15 minutes

Daily Scrum purpose

inspect progress toward the sprint goal and adapt the plan if needed

Daily Scrum required participants

only the developers

Sprint Review purpose

• inspect the increment and adapt the product backlog

• focuses on what to do next based on feedback

Sprint Review participants

scrum team and stakeholders

Sprint Retrospective purpose

improve the team’s way of working

Sprint Retrospective reflection

• what went well

• what didn’t

• what improvements to try next

Product Backlog

ordered list of everything that might be needed for the product

Product Backlog owned by

product owner

Sprint Backlog

• sprint goal

• selected product backlog items

• plan for delivering them

Sprint Backlog owned by

developers

Increment

completed work produced during the sprint

Increment must be

• usable

• valuable

• meet the definition of done

Each artifact

has one commitment

Product Backlog commitment

product goal

Sprint Backlog commitment

sprint goal

Increment commitment

definition of done

Who orders the product backlog?

product owner

Who decides how to accomplish the sprint work?

developers

Who is accountable for helping everyone understand and use scrum?

scrum master

Empiricism

asserts that knowledge comes from experience and making decisions based on what is observed

Lean Thinking

reduces waste and focuses on the essentials

Transparency

emergent process and work must be visible to those performing the work and those receiving

Low Transparency Artifacts

can lead to decisions that diminish value and increase risk

Transparency enables

inspection

Inspection

frequently and diligently to detect potentially undesirable variances and problems

Inspection enables

adaptation

Adaptation

if any aspects of the process deviates outside acceptable limits or if resulting product is unacceptable

Scrum Values

• commitment

• focus

• openness

• respect

• courage

Scrum Team consists of

• one scrum master

• one product owner

• developers

Scrum Team make-up

• no sub-teams or hierarchies

• cohesive unit of professionals focused on one objective at the time

• cross-functional and self-managing

Scrum Team members

10 or fewer people

multiple scrum teams

each focused on the same product and and should share the same product goal, product backlog, and product owner

Scrum Team responsible for

all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research, and development

Scrum Team accountable for

creating a valuable, useful increment every sprint

Developers

people in the scrum team that are committed to creating any aspect of a usable increment each sprint

Developers accountable for

• creating a plan for the sprint, the sprint backlog

• instilling quality by adhering to a definition of done

• adapting their plan each day toward the sprint goal

• holding each other accountable as professionals

Product Owner

accountable for maximizing the value of the product and for effective product backlog management

Effective Product Backlog Management

• developing and explicitly communicating the product goal

• creating and clearly communicating product backlog items

• ordering product backlog items

• ensuring that the product backlog is transparent, visible, and understood

Scrum Master accountability

• accountable for establishing scrum by helping everyone understand scrum theory and practice

• accountable for scrum team’s effectiveness by enabling scrum team to improve its practices

Scrum Master serves Scrum Team by

• coaching the team members in self-management and cross-functionality

• helping the scrum team focus on creating high-value increments that meet the definition of done

• causing the removal of impediment to the scrum team’s progress

• ensuring that all scrum events take place and are positive, productive, and kept within the timebox

Scrum Master serves the Product Owner by

• helping find techniques for effective product goal definition and product backlog management

• helping the scrum team understand the need for clear and concise product backlog items

• helping establish empirical product planning for a complex environment

• facilitating stakeholder collaboration as requested or needed

Scrum Master serves the organization by

• leading, training, and coaching the org in its scrum adoption

• planing and advising scrum implementations within the org

• helping employees and stakeholders understand and enact an empirical approach for complex work

• removing barriers between stakeholders and scrum teams

Scrum Events

• each event in scrum is a formal opportunity to inspect and adapt scrum artifacts

• designed to enable the transparency required

• used to create regularity and to minimized need for meetings not defined in scum

Sprints

ideas are turned into value

Sprint lengths

fixed length events of one month or less to create consistency

During Sprint

• no changes are made that would endanger the sprint goal

• quality does not decrease

• product backlog is refined as needed

• scope may be clarified and renegotiated with the product owner as more is learned

Sprint cancelled when

sprint goal becomes obsolete

Who can cancel a sprint?

only the product owner has the authority

Sprint Planning

• initiates the sprint by laying out the work to be performed for the sprint

• discuss the most important product backlog items and how they map to the product goal

Sprint Planning topics

1) why is the sprint valuable?

2) what can be done this sprint?

3) how will the chosen work get done?

Sprint Planning length

timeboxed to a maximum of eight hours for a one month sprint

Daily Scrum

inspect progress toward sprint goal and to adapt the sprint backlog as necessary, adjusting upcoming planned work

Daily Scrum length

15 min event for developers

Daily Scrum purpose

improves communications, identify impediments, promotes quick decision-making, and consequently eliminate the need for other meetings

Sprint Review

• inspect outcome of sprint and determine future adaptations

• scrum team presents results to key stakeholders and progress toward product goal is discussed

Sprint Review length

second to last event and timeboxed to a maximum of four hours for a one month sprint

Sprint Retrospective

• plan ways to increase quality and effectiveness

• team inspects how the last sprint went and their definition of done

Sprint Retrospective discusses

• what went well during the sprint

• what problems it encountered

• how those problem were or were not solved

• identifies the most helpful changes to improve its effectiveness

Sprint Retrospective length

timeboxed to a maximum of three hours for a one month sprint

Scrum Artifacts

• represent work/value and designed to maximize transparency of key info

• each contains commitment to ensure it provides info that enhances transparency and focus against which progress can be measured

Product Backlog

• emergent, ordered list of what is needed to improve the product

• single source of work undertaken by the scrum team

Product Backlog refinement

• act of breaking down and further defining product backlog items into smaller more precise items

• ongoing activity to add details

responsible for product backlog sizing

developers

Product Goal

describes future state of the product which can serve as a target for the scrum team to plan against

Product

• vehicle to deliver value

• clear boundary, known stakeholders, well-defined users or customers

Sprint Backlog composed of

composed of the sprint goal (why), the set of product backlog items selected for the sprint (what), and actionable plan for delivering the increment (how)

Sprint Backlog planned by

developers

Sprint Backlog

highly visible, real-time picture of the work that the developers plan to accomplish during the sprint in order to achieve the sprint goal

Sprint Goal

• single objective for the sprint

• create coherence and focus

• created during sprint planning event and then added to sprint backlog

Increment

concrete stepping stone toward the product goal

Sum of Increments

presented at the sprint review, supporting empiricism

Definition of Done

formal description of the state of the increment when it meets the quality measures required for the product

product backlog item meets the definition of done

increment is born

final say of the order of the backlog

product owner

multiple scrum teams

single product backlog

scum focus

delivering value