OUTCOMES OVER OUTPUTS - Scrum Alliance
OUTCOMES OVER OUTPUTSBEN RODILITZ AND CHERIE SILAS
BEN RODILITZ –PROJECT MANAGER/AGILIST - TERADATA LABSBen is currently on staff at Teradata Labsfollowing a 3 ½ year stint as part ofDealer.Com's successful agiletransformation.
CHERIE SILAS, ENTERPRISE AGILE COACHMy Mission: To leave youbetter than I found youwith each encounter
LEARNING OBJECTIVESLearning Outcomes: Recognize the difference between outputs (what we produce) and outcomes (theimpact we want) Identify the desired outcomes and outputs of Scrum events Develop effective and measurable outcomes with user stories
OUTPUTSThe amount of something produced by a person, machine, or industryIn Scrum Practice:The ceremonies we do and what we produce as a result of them.
OUTCOMESThe consequence of doing somethingIn Scrum Practice:What we want to happen as a result of what we do.
SIMPLE EXAMPLES Making a Meal Output: Food Outcomes: Nutrition, good taste, social setting, experimentation, cultural learning, etc. GPS in Mobile Phones E911: Output is Position and Speed outcome is being able to locate someone in anemergency Turn-by-Turn navigation: output Position and Velocity outcome ability to monetizelocation based services such as turn by turn navigation
SCRUM EXAMPLE – DAILY STANDUP Daily Stand Up Refinement of Sprint plan to enhance probability of meeting sprint commitment (outcome) Status – answers to the three questions (output) Gauge how we well we are moving toward meeting our sprint commitment (output) Propose changes to our sprint execution to better meet that commitment (output) Impediments do not hinder the team’s progress (outcome) Identification of impediments (output) Action plan(s) to remove impediments (output) More successful sprint/feature execution this sprint and over time (outcome)
ACTIVITYYOU FIND THE OUTCOMES AND OUTPUTS
OUTCOMES EXAMPLES: BACKLOG REFINEMENT Backlog Refinement The work brought into the sprint is understood to increase probability of success (outcome) Stories meet the team’s definition of ready (output) Team is clear on value of the story (outcome) Team is clear on the success/acceptance criteria (outcome) Team has reached consensus on the complexity of the story (relative sizing) (outcome) Understand the problem or opportunity they are trying to solve/take advantage of (outcome)
OUTCOMES EXAMPLES: SPRINT PLANNING Sprint Planning Team understanding of the sprint goals (outcome) Team understanding what work they will be doing to meet the sprint goal (outcome) Balance between probability of successfully meeting the sprint commitment and willingness tostretch and improve (outcome) Sprint plan (output) Sprint goal (output)
OUTCOMES EXAMPLES: SPRINT REVIEW/DEMO Sprint Reviews/Demos Stakeholder partnership and alignment (outcome) Feedback on the increment produced in the sprint (output) Updated backlog that better reflects the needs and feedback of the stakeholders (output) Understanding the state of the planned release (outcome) Agreement on changes to scope or timeline of the planned release (outcome) Agreement on next priorities (outcome) Backlog prioritization changes (output)
OUTCOMES EXAMPLES: RETRO Retros Continuous Improvement (Outcome) (output) Identify issues of concern and an action plan for addressing them (output) Identify team wins to celebrate in order to increase team’s state of mind, enthusiasm, etc. (output) Reflection on previous issues to ensure they are being worked/”fixed”
FOCUSING ON OUTCOMES WHEN IMPROVING What needs to improve? Why does it need to improve? What improvement experiments will you try? What outcomes do you expect from the experiment? How will you know when you have succeeded?
HYPOTHESIS USER STORY FOR IMPROVEMENTSWe believe that this experiment Will result in this outcome We will know we have succeeded when we see thismeasurable condition
HYPOTHESIZE FEATURE SUCCESSWe Believe that increasing the size of car images on the search pageWill Result in improved customer engagement and conversionWe Will Know We Have Succeeded when: Within 3 months after release We see a 15% increase in customers who review car images on the search page We see a 5% increase in customers who convert to purchase within 48 hours of viewing carimages on the search page
HYPOTHESIZE TEAM IMPROVEMENTSWe believe that decreasing the size of our user storiesWill result in our ability to be more predictable in our delivery of workWe will know we have succeeded when: By the end of this quarter (5 sprints) The average carry over reduces from our current average of 28% Our average predictability falls between 80-95%
HYPOTHESIZE SCRUM CEREMONY IMPROVEMENTSWe believe that adopting the walk the wall method in our daily scrumWill result in increased focus and full team ownership of the sprint backlogWe will know we have succeeded when: Measure results over the next 6 sprints (Q2) WIP is reduced from our current WIP of one story per developer Focus on finishing stories rather than starting new stories becomes the norm We see no more than one started but incomplete feature at the end of the quarter
WRITE YOUR OWN HYPOTHESIS USER STORYFOR YOUR TAKE-AWAY IMPROVEMENTSWe believe that this experiment Will result in this outcome We will know we have succeeded when we see thismeasurable condition
CONTACT INFORMATION Cherie Silas Coachcherie@att.net @pastorcherie Ben Rodilitz BRodilitz@Verizon.net @BenRodilitz https://www.linkedin.com/in/ben-rodilitz/
OUTCOMES EXAMPLES: SPRINT PLANNING Sprint Planning Team understanding of the sprint goals (outcome) Team understanding what work they will be doing to meet the sprint goal (outcome) Balance between probability of successfully meeting the sprint commitment and willingness t
This Scrum and Scrum Master Guide is a free, quick reference material designed to help aspiring scrum masters discover the ins and outs of Scrum. It throws light on the fundamental principles of the scrum, scrum terminologies, Agile Manifesto, scrum theories, scrum tools, different roles, responsibilities, and more. SCRUM & SCRUM MASTER
Scrum framework, the Scrum Master and the Scrum Product Owner share the role and responsibilities of a typical project manager. Nonetheless, a Scrum Master or a Scrum Product is never allowed to overrule the democratic decision-making capability of a Scrum Team. For instance, only the Scrum team members can
enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the
priority for Scrum projects. This reflects Scrum's focus on the customer. Meanwhile, the second-highest priority is all about the business — meeting budget, time, and scope constraints. This reflects Scrum's focus on delivering shippable increments on time and on budget. Scrum improves the quality of work life. 87% agree that Scrum is
The Scrum Master Finally has some Authority .11 Conclusion .12 Purpose of Analysis In practice, Scrum is a vague concept. There are many different, incompatible, kinds of Scrum; and for each of these kinds of Scrum, there can be different descriptions. We like the Scrum that is described in the 2017 Scrum Guide, but we .
Method Scrum Scrum Scrum Scrumban Scrum Scrum Scrum Scrum Size 24 PM 30 PM 30 PM 100 PM 30 PM 12 PM 72 PM 120 PM Duration 3 M . Continuous delivery Delivery on time testing on unit le
challenges Training (Scrum Master, Product Owner, Agile Leadership, online courses, etc.) Consulting (linking Scrum and business strategy, customizing Scrum) Coaching (hands-on support to Scrum teams) Find out more at www.scruminc.com. We run our company using Scrum as the primary management framework, making us a living
scrums”. Scrum rules are product owner, scrum master and team. Scrum is easy with changes; it accommodates with changes. Scrum [1][5][6] is a simple framework used to higher quality. Scrum is easy with changes; it accommodates with changes. Some key scrum practices are discussed below [1][3][4][5].
