Sprint Goal, Product Goal, and Definition of Done 

This is me PST Developer Strategist Consultant Trainer www.Suscheck.com 

Commitments What are they and why the change to Scrum Guide 2020 

Scrum Guide 2020 Changes • Made a new term: commitments • Promoted Definition of Done to a commitment • Promoted Sprint Goal to a commitment • Created Product Goal commitment 

Why the change? Emphasis on WHY in Scrum 

Why the change? Wrong way of thinking Commitment = a certainty to provide output Leaders can push people to complete a commitment Individuals complete “their” commitment Right way of thinking Commitment = a solemn promise Commitment to a goal overrides details of the “what” and “how” The group commits to a shared goal 

Commitment relationships Product Goal Sprint Goal Def of Done Product Backlog Sprint Backlog Increment Provides meaning for Provides meaning for Validates Qualifies Constrains 

Plan Promise Product and Sprint Goals are aspirations, DOD is a promise Singular Goal Product Backlog Sprint Backlog Sprint Goal Product Goal Singular Goal ….. ….. ….. ….. Selected PBIs ….. ….. ….. ….. PBIs ….. ….. ….. ….. PBIs Definition of Done q This q That q Another thing q Etc. q Etc. q … Increment How do we get there? How do we get there? Increment Did PBI meet DOD? Yes! 

What is a Goal 

You don’t need goals Poker Canasta Go Fish 

Start with why – Simon Sinek 

Do you have SMART goals?? SMART goals are: • Specific • Measurable • Achievable • Relevant • Time-bound Commitment goals are: • The objective of the related artifact • Observable when achieved • Focused on enhancing value for the customer • Product focused • Outcome based (not output based) • Aligned to fulfilling the higher level • Singular – not compound • Do not assume future goals • Achieved before the artifact is exhausted 

Product Goals 

You don’t need a product goal We have a product vision We have a product strategy How do you respond to this? 

Product Goal • future state of the product • target for the Scrum Team to plan against • long-term objective • fulfill (or abandon) one objective at a time • The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal. • The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next. Product Goal: Summary from SG2020 

Product Vision, Product Goal, and Sprint Goal Relationship Save lives by reducing accidents at traffic lights Autonomously change traffic flow via traffic lights depending on volume Establish core communication with traffic lights Product Vision Product Autonomous Traffic Light Coordinator Product Goal Sprint Goal Send simple ping between two TL PBIs in the sprint Centrally determine state of TLs ….. ….. ….. ….. Centrally Determine Geolocation of TL What is the difference? 

No content

Product Goal is Teflon for the Product Backlog Product Goal can help determine what should NOT be in the product backlog Product Backlog Product Goal Product Goal Idea 

What is a good Product Goal • The objective of the product backlog • Observable when achieved • Focused on enhancing value for the customer • Product focused • Outcome based (not output based) • Aligns to fulfilling the product vision • Singular – not compound • Does not assume future product goals • Achieved before the product backlog is exhausted future state of the product target for the Scrum Team to plan against long-term objective fulfill (or abandon) one objective at a time 

Product Goal Level Might Vary Go to the moon Make hybrid lawnmowers Strategic Tactical Low Risk High Risk Launch a Self- driving car in a new market Expand current offering with existing target audiences Typical realm of the Product Goal Typical realm of the Sprint Goal 

Product Goal Example 1 Customers in Brazil can purchase our products Our product will allow sales of our products to customers in Brazil. q The objective of the product backlog q Observable when achieved q Focused on enhancing value for the customer q Product focused q Outcome based (not output based) q Aligns to fulfilling the product vision q Singular – not compound q Does not assume future product goals q Achieved before the product backlog is exhausted 

Product Goal Example 2 Create a product to load all customer complaints from multiple systems and manage the complaints What’s the customer value? Seems very large! q The objective of the product backlog q Observable when achieved q Focused on enhancing value for the customer q Product focused q Outcome based (not output based) q Aligns to fulfilling the product vision q Singular – not compound q Does not assume future product goals q Achieved before the product backlog is exhausted 

Product Goal Example 3 Ensure reliability and accuracy of the product. How will you know? Is this a PRODUCT goal? q The objective of the product backlog q Observable when achieved q Focused on enhancing value for the customer q Product focused q Outcome based (not output based) q Aligns to fulfilling the product vision q Singular – not compound q Does not assume future product goals q Achieved before the product backlog is exhausted 

Product Goal Examples Enable users to run daily scrums asynchronously. Help the users understand their eating habits. Grow customer base by 15%. Make a manageable product catalog for our sales department. The fitness app should have the largest partner ecosystem. After 6 months the revenue of the company should double. q The objective of the product backlog q Observable when achieved q Focused on enhancing value for the customer q Product focused q Outcome based (not output based) q Aligns to fulfilling the product vision q Singular – not compound q Does not assume future product goals q Achieved before the product backlog is exhausted 

Questions • When does a Product Goal Change? • Can you have “inactive” Product Goals? • Can you have more than 1 release toward a Product Goal? • Does every PBI need to contribute to the product goal? 

Sprint Goals 

Sprint goal is just a restatement of the selected PBIs • We can just say we are completing ….. • Our sprint goal is to get the work done • Sprint goal has at least 6 “ands” Complete Five User Stories and Fix All Production Bugs How do you respond to this? 

Sprint Goal • single objective for the Sprint • creates coherence and focus to work together • created during the Sprint Planning • negotiate the scope of the Sprint Backlog without affecting the Sprint Goal • The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives. • The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog. As the Developers work during the Sprint, they keep the Sprint Goal in mind. If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal. Sprint Goal: Summary from SG2020 

Sprint Goals • Through the implementation of the PBIs selected in Sprint Planning • Providing guidance to the Scrum Team • Acts as a step towards the Product Goal An objective to be met in the Sprint • Allows flexibility for exact implementation of PBIs • Although the Sprint Goal is fixed Allows flexibility in delivering the Increment • As the Scrum Team works, it keeps this goal in mind • Each Daily Scrum assesses the Team’s progress toward meeting the Sprint Goal Is sacrosanct throughout the Sprint Can we build the hazard warning line assistance with the new hardware sensor for our trucks? A visitor has ability to order a product Allow users to order by using pre-paid cards Set up deployment pipeline & release an empty site to production Show top-selling products on the homepage Enable visitors to search for properties 

Sprint Goal is Magnet for the Sprint Backlog Sprint Goal can help determine what goes into the sprint backlog Sprint Goal Product Backlog Sprint Backlog 

What is a good sprint goal • The objective of the Sprint • Observable as part of the Sprint • Focused on enhancing value for the customer • Product focused • Singular – not compound • Do not assume future sprints • Contributes to the product goal • Outcome based (not output based) • Achievable within a Sprint single objective for the Sprint creates coherence and focus to work together created during the Sprint Planning negotiate the scope of the Sprint Backlog without affecting the Sprint Goal 

Sprint Goal Example 1 Translate user-facing sites and messages to the user’s language Achievable within a Sprint? q The objective of the Sprint q Observable as part of the Sprint q Focused on enhancing value for the customer q Product focused q Singular – not compound q Do not assume future sprints q Contributes to the product goal q Outcome based (not output based) q Achievable within a Sprint 

Sprint Goal Example 2 Improve customer retention by 20% by implementing a feedback system Achievable within a Sprint? Customer focused? q The objective of the Sprint q Observable as part of the Sprint q Focused on enhancing value for the customer q Product focused q Singular – not compound q Do not assume future sprints q Contributes to the product goal q Outcome based (not output based) q Achievable within a Sprint 

Sprint Goal Example 3 Develop an enterprise-class durable customer service application to tackle the recent surge in consumer complaints Achievable within a Sprint? Outcome Based? Service = better complaint numbers? q The objective of the Sprint q Observable as part of the Sprint q Focused on enhancing value for the customer q Product focused q Singular – not compound q Do not assume future sprints q Contributes to the product goal q Outcome based (not output based) q Achievable within a Sprint 

Sprint Goal Examples q The objective of the Sprint q Observable as part of the Sprint q Focused on enhancing value for the customer q Product focused q Singular – not compound q Do not assume future sprints q Contributes to the product goal q Outcome based (not output based) q Achievable within a Sprint Create a dashboard with basic widgets for the most common two platforms After purchase, guide customers through the set-up and configuration of [Product A] Allow customers to log in to the various products with OpenID (single sign-on); Add Amex processing Add a “WOW” factor to the product Allow users to order by using pre-paid credit 

Questions • What happens if the Sprint Goal can’t be met? • Can you have a Sprint Goal that doesn’t feed the Product Goal? • Do you have to have a release to achieve a Sprint Goal? • Does every SBI need to contribute to the sprint goal? • If not, how many can you have in a sprint? 

Definition of Done 

Definition of Done • Description of quality measures • Applied to each PBI • PBI not meeting DOD = no increment • Fulfill (or abandon) one objective at a time • Scrum team creates it (or organization) • Developers conform to it • Multiple teams = 1 DOD • The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. • The moment a Product Backlog item meets the Definition of Done, an Increment is born. • The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration. • If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. • The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done. Product Goal: Summary from SG2020 

What do you think? Done / Done / Done Done / Done Done Released Tested Coded Code 2 weeks Test 2 weeks Bug Fix 2 weeks 

Our Definition of Done is Great qCode has been tests qProduct is signed off qProduct is in production Big Whoot 

The Healthy Tension The Pollyanna Purist The Wilting Pragmatist Scrum is always the answer No schedules and no budgeting Management is stupid It’s leadership’s fault Nothing is DONE until released Each PBI must be DONE in the sprint We are Scrum-ish Sprints are force fed work Management is responsible for project Leadership’s sets dates and scope DONE is a dream Get Real 

DOD 

Differentiating DOD, Sprint Goal, Acceptance Criteria 43 Sprint Goal Definition of Done Acceptance Criteria Increase product responsiveness Complies with legislation on drug interactions Data collection is set up to support validations Works with keyboard and gamepad Accepts Visa, Mastercard, American Express Should use hamburger menu style on iPhone Documentation is updated Increase capacity to 100K customers Use UK English on screens Reviewed by the stakeholders Use latest Yuan to Euro conversion algorithm User Acceptance Test instructions are updated Address debit card overdrafts No unreachable components 

Coded Tested on my machine Code Reviewed Change Log Checked in Tagged Version Integration Tested Migration Script UAT Manual Compliance Performance Tested Know Defects Updated Support Notified Customer Compiles Code Metrics PBI Complete Sprint Complete Release Ready In Support Where do these go? Definition of Done: 

Coded Tested on my machine Code Reviewed Change Log Checked in Tagged Version Integration Tested Migration Script UAT Manual Compliance Performance Tested Know Defects Updated Support Notified Customer Compiles Code Metrics PBI Complete Sprint Complete Release Ready In Support Where do these go? Definition of Done: 

Coded Tested on my machine Code Reviewed Change Log Checked in Tagged Version Integration Tested Migration Script UAT Manual Compliance Performance Tested Know Defects Updated Support Notified Customer Compiles Code Metrics PBI Complete Sprint Complete Release Ready In Support Where do these go? Definition of Done: 

Code Reviewed Checked in Tagged Version Integration Tested Migration Script UAT Manual Compliance Performance Tested Know Defects Updated Support Notified Customer Code Metrics PBI Complete Sprint Complete Release Ready In Support Where do these go? Coded Tested on my machine Change Log Compiles Definition of Done: 

Tagged Version Migration Script UAT Manual Compliance Performance Tested Know Defects Updated Support Notified Customer PBI Complete Sprint Complete Release Ready In Support Where do these go? Definition of Done: Coded Tested on my machine Code Reviewed Change Log Checked in Integration Tested Compiles Code Metrics 

Tagged Version Migration Script Executed UAT Performed Manual Created Compliance Turned Over Performance Tested PBI Complete Sprint Complete Release Ready In Support Where do these go? Definition of Done: Coded Tested on my machine Code Reviewed Change Log Checked in Integration Tested Compiles Code Metrics UAT Script Updated Manual Notated Performance Test Plan updated Migration Script Updated Compliance Document Updated Know Defects Updated Support Notified Customer 

Tagged Version Migration Script Executed UAT Performed Manual Created Compliance Turned Over Performance Tested Know Defects Updated Turnover Sent Customer Notification Sent PBI Complete Sprint Complete Release Ready In Support Where do these go? Definition of Done: Coded Tested on my machine Code Reviewed Change Log Checked in Integration Tested Compiles Code Metrics UAT Script Updated Manual Notated Performance Test Plan updated Migration Script Updated Compliance Document Updated Updated Turnover Notated Cust Notification Notated 

Questions • When does the DOD change? • Who has the final say for the DOD? • Where do you start • Does every SBI need to conform to the DOD? • If not, how many can you have in a sprint? 

Summary and end Questions too 

Product Goal (Product Backlog) • future state of the product • target for the Scrum Team to plan against • long-term objective • fulfill (or abandon) one objective at a time Summary in 1 slide Definition of Done (Increment) • Description of quality measures • Applied to each PBI • PBI not meeting DOD = no increment • Fulfill (or abandon) one objective at a time • Scrum team creates it (or organization) • Developers conform to it • Multiple teams = 1 DOD Commitment = a solemn promise Commitment to a goal overrides details of the “what” and “how” The group commits to a shared goal Sprint Goal (Sprint Backlog) • single objective for the Sprint • creates coherence and focus to work together • created during the Sprint Planning • negotiate the scope of the Sprint Backlog without affecting the Sprint Goal 

You can take a class to learn more! Thank you! Charles Suscheck [email protected] www.Suscheck.com https://www.scrum.org/classes?uid=128 

1.If we don’t work towards this Sprint Goal, what will be inevitably lost or become much harder later? 2.If we wouldn’t have another Sprint after this one, what would be the one thing we’d have to deliver in order to return some value? 3.If we were paying for this Sprint with our own money, what work would give us the highest chance to get that money back? 4.When we achieve this Sprint Goal, what has clearly changed or improved from the perspective of stakeholders? 5.Which steps are required to achieve this Sprint Goal? Which are the least required or could we do without if we really have to? 6.If we suddenly have half the team available and we can do only half the work required for the Sprint Goal, what should absolutely be in there in order for us to still be okay with the outcome? What can we let go of for now and return to later? 7.If there’s an ‘AND’ in the Sprint Goal: which would you naturally do first if you have to choose? What is irrevocably lost if we do that thing first, and the second thing in another Sprint? 8.What would need to happen while working on this Sprint Goal that would be cause for celebration? 9.What worry about our product is keeping you up at night? What can we build or test this Sprint to make you sleep a bit better? 10.In terms of value and learning about what else is needed from us a team, what is the worst way to spend the upcoming Sprint? What should we focus on this Sprint to prevent that? Good Questions for a Sprint Goal 

You’re still here? 56 [email protected]