SlideShare a Scribd company logo
1 of 52
Download to read offline
#Only90sKidsWillGetThis
Photo by Quino Al on Unsplash
A scrum (short for scrummage) is a
method of restarting play in rugby that
involves players packing closely together
with their heads down and attempting to
gain possession of the ball.
For other uses, see Scrum (disambiguation).
Scrum may refer to:
•Scrum (rugby), a method of restarting play in rugby
•Scrum (media), an impromptu press conference, often
held immediately outside an event
•Autozam Scrum, a microvan and pickup truck sold in
Japan by Mazda
•“Scrum", a song on the album Diabolus in Musica by Slayer
•Scrum (software), a variant of the agile methodology used
for software development
Scrum (software)
•The product is built in a series of fixed-length
iterations called sprints that give teams a
framework for shipping on a regular cadence.
•Milestones–i.e., the end of a sprint–come
frequently, bringing with them a feeling of
tangible progress.
•Short iterations reinforce the importance of good
estimation and fast feedback from tests.
Justin Searls
@searls
To be clear, apathy isn't a moral failing—
it's actually a rational coping mechanism
in unhealthy environments.
Want an apathetic software team?
Pressure them to meet aggressive
arbitrary deadlines or exert undue
control over how they do their work
Scrum Values
•Transparency: nothing happens in the dark. The
product backlog is visible, estimates are shared,
velocity is tracked, definition of done is clear, etc.
•Inspection: Inspect Scrum artifacts frequently,
but not so frequently it gets in the way of work.
•Adaption: If something isn’t working, adjust
course as quickly as possible.
— meet the —
Scrum Team
— the —
Product
Owner
— the —
Scrum
Master
— the —
Dev
Team
photo by rawpixel on unsplash
Here's the catch: reaching
the “performing” stage is
impossible if a team's
make-up keeps changing!
image credit: Atlassian
photo by rawpixel on unsplash
— the —
Product
Owner
photo by rawpixel on unsplash
Product Owner
•Champion of their product
•One person, not a committee
•Focused on understanding business and market
requirements, then prioritizing the work to be
done by the Dev Team accordingly
•Responsible for managing product backlog
•Not a project manager!
photo by rawpixel on unsplash
— the —
Dev
Team
photo by rawpixel on unsplash
Development Team
•Champions of sustainable development practices
•Consists of 3-9 professionals
•Responsible for planning the sprint and delivering a
potentially releasable increment of “Done” work
•Self-organizing: No one (not even the Scrum Master)
tells the Dev Team how to work
•Cross-functional: Has all competencies needed to do
the work without depending on non-team members
photo by rawpixel on unsplash
— the —
Scrum
Master
photo by rawpixel on unsplash
Scrum Master
•Champion of process within their team
•Coach the team and the business on Scrum & look for
ways to fine-tune their process
•Resolve impediments for the Dev Team, insulating
them from external disruptions when possible
•Defend against a common Scrum anti-pattern:
changing a sprint's scope after it has begun
•Also not a project manager!
Scrum Master
•What happens when there’s no dedicated Scrum
Master?
•Avoid conflicts of interest — Product Owners should
not act as Scrum Masters
•Rotating the Scrum Master role through the Dev Team
can inject fresh ideas
•Best to worst: Dedicated Scrum Master, Shared Scrum
Masters, Engineer Scrum Master, No Scrum Master
— the —
Scrum Rituals
Scrum Rituals
•Prescribed events create regularity and minimize
the need for meetings not defined in Scrum
•All events are time-boxed
•Other than the sprint itself, each event is a formal
opportunity to inspect and adapt
The Sprint
A fixed length of work during which a
“Done,” useable, and potentially releasable
product increment is created.
The Sprint
•Once started, no changes that would endanger the
sprint goal
•That includes adding user stories or changing
sprint length
•Sprint cancellations are traumatic to the Scrum
team, and are very uncommon
How Long is a Sprint?
•Sprint length can range from 1–4 weeks
•2 weeks is pretty standard
•You can get more done in a longer sprint, 

but you’re less capable of reacting to changes
•Keeping sprint length consistent gives the Dev
Team critical feedback on estimation & delivery
process, makes forecasts increasingly accurate
over time.
Product Backlog
Grooming
The team reviews and estimates
user stories in the product backlog
Product Backlog Grooming
•Duration: 1 hour / week of sprint
•Happens: Could be anytime, but often first day of
sprint, or alternate Mondays
•Attendees: scrum team
•Purpose: The Product Owner gets help with the
product backlog.
What’s a Product Backlog?
An ordered list of user stories for everything known
to be needed in the product
•Single source of requirements for any changes to
be made to the product
•Product Owner is responsible for the product
backlog, including its content, availability, and
ordering
•A product backlog is never complete
What are User Stories?
•As a {type of user}, I want {functionality} 

so that I {receive benefit}
•Sketched out by Product Owner
•Should describe a problem, not prescribe a solution
•Dev Team helps refine
•Can this be done? Do we need more information?
Should it be broken into smaller stories?
How Do We Estimate?
•Dev Team plays planning poker to assign story points
•Points rate the relative effort of work, not time to complete
•Estimated relative to other well-understood work.

“Is this more or less complicated than that story?”
•Abstraction avoids the “Architect can do it in 2 hours, but
the intern needs a full week” problem
•Estimates will be inaccurate until the team establishes a
common baseline after a few sprints
Sprint Planning
The team determines their sprint capacity
and pulls stories from the product backlog
Sprint Planning
•Duration: 2 hours / week of sprint

(new teams may need more time)
•Happens: first day of the sprint
•Attendees: scrum team
•Purpose: The Dev Team plans their work with
guidance from the Product Owner
Sprint Planning
•Capacity for the sprint is determined by
reviewing velocity
•User stories are pulled in order from the top of
the product backlog
•The team breaks user stories into tasks for the
sprint backlog
•Define a sprint goal to provide context and
guidance to the team
What’s a Sprint Backlog?
An ordered list of tasks created from user stories accepted
into the current sprint
•Stories must be estimated and contain clear

acceptance criteria
•Should not change once the sprint starts, because the
Dev Team is making a informed commitment to deliver
this body of work.
•What about bugs and P0 interruptions?

(they’re going to happen!)
What is Velocity?
A measure of the amount of work a Scrum team can
complete during a single Sprint
•Calculated as a rolling average of the story points
completed in previous sprints
•It takes several sprints before a useful velocity
metric can be determined
•Velocity is only for planning! Team success should
be based on value delivered.
image credit: Atlassian
Daily Scrum
a.k.a. Standup
The Dev Team plans their work
for the next 24 hours and checks
progress towards sprint goal
Daily Scrum
•Duration: 15 min timeboxed
•Happens: every day
•Attendees: Dev Team, Scrum Master. Product
Owner optional.
• If others are present, the Scrum Master ensures that they do not disrupt the meeting.
•Purpose: The Dev Team checks their progress
toward the sprint goal
Daily Scrum
•Check progress by:
•Answer the three questions
•Review the burndown chart
•This is a meeting for the Dev Team,

not a detailed status report for management
•Blockers should be escalated to Scrum Master
What are the Three Questions?
•What did I do yesterday that helped the Dev Team
meet the sprint goal?
•What will I do today to help the Dev Team meet the
sprint goal?
•Do I see any impediment that prevents me or the
Dev Team from meeting the sprint goal?
•This is not “justify your salary” time.

Answers should be relevant to the sprint goal.
What’s a Burndown Chart?
Shows the work completed over time compared to an
ideal trend line
•Reviewing this chart can be a useful tool to see if
the Dev Team is on-track to complete their work
•If the burndown line extends beyond the trend line,
the team may be falling behind their goal
•If the burndown line makes steep drops, the team
should work on breaking stories into smaller tasks
image credit: Atlassian
Sprint Review
An informal demo of what was
achieved by the team to the Product
Owner and other stakeholders
Sprint Review
•Duration: 30 min / week of sprint
•Happens: last day of the sprint
•Attendees: scrum team, key stakeholders invited
by Product Owner
•Purpose: Demonstrate work and get feedback
Sprint Review
•Focus on the product, not the process
•Work should be fully demonstrable and meet the
team's definition of “Done” to be considered
complete and ready to showcase in the review
•Celebrate success
•Gather feedback, which should channel back into
the product backlog
Sprint Retrospective
A review of what did and didn't go well
with actions to make the next sprint better.
Sprint Retrospective
•Duration: 30 min / week of sprint
•Happens: last day of the sprint
•Attendees: scrum team (no management!)
•Purpose: Review and improve process
Sprint Retrospective
•Focus on improving process, not the product
•Not a time for complaints without action
•Reflect on what went well during the sprint so the
team can continue to focus on those areas
•Find out what's not working and use the time to
find creative solutions and develop an action plan
— let’s —
Recap
image credit: scrum.org
Scrum Values
•Transparency: nothing happens in the dark. The
product backlog is visible, estimates are shared,
velocity is tracked, definition of done is clear, etc.
•Inspection: Inspect Scrum artifacts frequently,
but not so frequently it gets in the way of work.
•Adaption: If something isn’t working, adjust
course as quickly as possible.
Learn More
•The Scrum Guide

https://www.scrumguides.org/
•Scrum Rituals, Summarized

https://wp.me/p27LsI-3G
•Atlassian Scrum Guide

https://www.atlassian.com/agile/scrum
Scott Vandehey — spaceninja.com — @spaceninja

More Related Content

What's hot

What's hot (20)

Scrum and Devops - Workshop & Handson
Scrum and Devops - Workshop & HandsonScrum and Devops - Workshop & Handson
Scrum and Devops - Workshop & Handson
 
Scrum workshop - September 7, 2012
Scrum workshop - September 7, 2012Scrum workshop - September 7, 2012
Scrum workshop - September 7, 2012
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Scrumban
Scrumban Scrumban
Scrumban
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training Process
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
 
Scrum Framework
Scrum FrameworkScrum Framework
Scrum Framework
 
The Scrum Model
The Scrum ModelThe Scrum Model
The Scrum Model
 
Agile Checklist
Agile ChecklistAgile Checklist
Agile Checklist
 
professional scrum master
professional scrum master professional scrum master
professional scrum master
 
Scrum ppt
Scrum pptScrum ppt
Scrum ppt
 
Introduction into Scrum
Introduction into ScrumIntroduction into Scrum
Introduction into Scrum
 
Introduction to Scrum - Agile Methods
Introduction to Scrum - Agile MethodsIntroduction to Scrum - Agile Methods
Introduction to Scrum - Agile Methods
 
Scrum training
Scrum trainingScrum training
Scrum training
 
Scrum in Practice
Scrum in PracticeScrum in Practice
Scrum in Practice
 
Introduction to scrum
Introduction to scrumIntroduction to scrum
Introduction to scrum
 
Planeación de proyectos ágil con Planning Poker
Planeación de proyectos ágil con Planning PokerPlaneación de proyectos ágil con Planning Poker
Planeación de proyectos ágil con Planning Poker
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Agile scrum
Agile scrumAgile scrum
Agile scrum
 
Scrum 101
Scrum 101 Scrum 101
Scrum 101
 

Similar to Let's Talk About Scrum

Software Development Guide To Accelerate Performance
Software Development Guide To Accelerate PerformanceSoftware Development Guide To Accelerate Performance
Software Development Guide To Accelerate PerformanceZaid Shabbir
 
Agile Scrum Methodology - Introduction
Agile Scrum Methodology - IntroductionAgile Scrum Methodology - Introduction
Agile Scrum Methodology - IntroductionGeetha Madhuri
 
Agile Processes - Scrum
Agile Processes - ScrumAgile Processes - Scrum
Agile Processes - ScrumSoumya De
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptMujeebMohammed18
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptAnuriJoshi
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptGustavoDelaEspriella2
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptNarendraKumar521662
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptMANYAGOEL14
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptssuser436c47
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptssuserf8c57f
 
Agile Processes-Scrum.ppt
 Agile Processes-Scrum.ppt Agile Processes-Scrum.ppt
Agile Processes-Scrum.pptYunusKhan90
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptssuser4f2477
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptgauravarora931329
 
Agile scrum fundamentals
Agile scrum fundamentalsAgile scrum fundamentals
Agile scrum fundamentalsDeniz Gungor
 
Agile – scrum +
Agile – scrum +Agile – scrum +
Agile – scrum +Alon Lahav
 
Agile Scrum Quick Reference Card
Agile Scrum Quick Reference CardAgile Scrum Quick Reference Card
Agile Scrum Quick Reference CardTechcanvass
 
Practicing Agile through Scrum
Practicing Agile through ScrumPracticing Agile through Scrum
Practicing Agile through ScrumNaveen Kumar Singh
 

Similar to Let's Talk About Scrum (20)

Software Development Guide To Accelerate Performance
Software Development Guide To Accelerate PerformanceSoftware Development Guide To Accelerate Performance
Software Development Guide To Accelerate Performance
 
Agile Scrum Methodology - Introduction
Agile Scrum Methodology - IntroductionAgile Scrum Methodology - Introduction
Agile Scrum Methodology - Introduction
 
Agile Processes - Scrum
Agile Processes - ScrumAgile Processes - Scrum
Agile Processes - Scrum
 
Scrum
ScrumScrum
Scrum
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Agile Processes-Scrum.ppt
 Agile Processes-Scrum.ppt Agile Processes-Scrum.ppt
Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Agile scrum fundamentals
Agile scrum fundamentalsAgile scrum fundamentals
Agile scrum fundamentals
 
Agile – scrum +
Agile – scrum +Agile – scrum +
Agile – scrum +
 
Agile Scrum Quick Reference Card
Agile Scrum Quick Reference CardAgile Scrum Quick Reference Card
Agile Scrum Quick Reference Card
 
Agile Methodology
Agile MethodologyAgile Methodology
Agile Methodology
 
Scrum (2)
Scrum (2)Scrum (2)
Scrum (2)
 
Practicing Agile through Scrum
Practicing Agile through ScrumPracticing Agile through Scrum
Practicing Agile through Scrum
 

More from Scott Vandehey

July 2015 Tempest Browser Stats
July 2015 Tempest Browser StatsJuly 2015 Tempest Browser Stats
July 2015 Tempest Browser StatsScott Vandehey
 
Flexbox Will Shock You!
Flexbox Will Shock You!Flexbox Will Shock You!
Flexbox Will Shock You!Scott Vandehey
 
How to Use Sass to Make Your Site More Maintainable
How to Use Sass to Make Your Site More MaintainableHow to Use Sass to Make Your Site More Maintainable
How to Use Sass to Make Your Site More MaintainableScott Vandehey
 
My Favorite Sass Mixins
My Favorite Sass MixinsMy Favorite Sass Mixins
My Favorite Sass MixinsScott Vandehey
 
Tips for Front-End Teams without Tears, Heartache, or Fistfights
Tips for Front-End Teams without Tears, Heartache, or FistfightsTips for Front-End Teams without Tears, Heartache, or Fistfights
Tips for Front-End Teams without Tears, Heartache, or FistfightsScott Vandehey
 

More from Scott Vandehey (6)

What is Modular CSS?
What is Modular CSS?What is Modular CSS?
What is Modular CSS?
 
July 2015 Tempest Browser Stats
July 2015 Tempest Browser StatsJuly 2015 Tempest Browser Stats
July 2015 Tempest Browser Stats
 
Flexbox Will Shock You!
Flexbox Will Shock You!Flexbox Will Shock You!
Flexbox Will Shock You!
 
How to Use Sass to Make Your Site More Maintainable
How to Use Sass to Make Your Site More MaintainableHow to Use Sass to Make Your Site More Maintainable
How to Use Sass to Make Your Site More Maintainable
 
My Favorite Sass Mixins
My Favorite Sass MixinsMy Favorite Sass Mixins
My Favorite Sass Mixins
 
Tips for Front-End Teams without Tears, Heartache, or Fistfights
Tips for Front-End Teams without Tears, Heartache, or FistfightsTips for Front-End Teams without Tears, Heartache, or Fistfights
Tips for Front-End Teams without Tears, Heartache, or Fistfights
 

Recently uploaded

ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDELiveplex
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaborationbruanjhuli
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1DianaGray10
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UbiTrack UK
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureEric D. Schabell
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-pyJamie (Taka) Wang
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7DianaGray10
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopBachir Benyammi
 
Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Commit University
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...DianaGray10
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6DianaGray10
 
UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPathCommunity
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAshyamraj55
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxMatsuo Lab
 

Recently uploaded (20)

ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability Adventure
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-py
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7
 
20150722 - AGV
20150722 - AGV20150722 - AGV
20150722 - AGV
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 Workshop
 
Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6
 
UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation Developers
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptx
 

Let's Talk About Scrum

  • 2. Photo by Quino Al on Unsplash
  • 3. A scrum (short for scrummage) is a method of restarting play in rugby that involves players packing closely together with their heads down and attempting to gain possession of the ball. For other uses, see Scrum (disambiguation).
  • 4. Scrum may refer to: •Scrum (rugby), a method of restarting play in rugby •Scrum (media), an impromptu press conference, often held immediately outside an event •Autozam Scrum, a microvan and pickup truck sold in Japan by Mazda •“Scrum", a song on the album Diabolus in Musica by Slayer •Scrum (software), a variant of the agile methodology used for software development
  • 5. Scrum (software) •The product is built in a series of fixed-length iterations called sprints that give teams a framework for shipping on a regular cadence. •Milestones–i.e., the end of a sprint–come frequently, bringing with them a feeling of tangible progress. •Short iterations reinforce the importance of good estimation and fast feedback from tests.
  • 6. Justin Searls @searls To be clear, apathy isn't a moral failing— it's actually a rational coping mechanism in unhealthy environments. Want an apathetic software team? Pressure them to meet aggressive arbitrary deadlines or exert undue control over how they do their work
  • 7. Scrum Values •Transparency: nothing happens in the dark. The product backlog is visible, estimates are shared, velocity is tracked, definition of done is clear, etc. •Inspection: Inspect Scrum artifacts frequently, but not so frequently it gets in the way of work. •Adaption: If something isn’t working, adjust course as quickly as possible.
  • 8. — meet the — Scrum Team
  • 9. — the — Product Owner — the — Scrum Master — the — Dev Team photo by rawpixel on unsplash
  • 10. Here's the catch: reaching the “performing” stage is impossible if a team's make-up keeps changing! image credit: Atlassian
  • 11. photo by rawpixel on unsplash
  • 12. — the — Product Owner photo by rawpixel on unsplash
  • 13. Product Owner •Champion of their product •One person, not a committee •Focused on understanding business and market requirements, then prioritizing the work to be done by the Dev Team accordingly •Responsible for managing product backlog •Not a project manager!
  • 14. photo by rawpixel on unsplash
  • 15. — the — Dev Team photo by rawpixel on unsplash
  • 16. Development Team •Champions of sustainable development practices •Consists of 3-9 professionals •Responsible for planning the sprint and delivering a potentially releasable increment of “Done” work •Self-organizing: No one (not even the Scrum Master) tells the Dev Team how to work •Cross-functional: Has all competencies needed to do the work without depending on non-team members
  • 17. photo by rawpixel on unsplash
  • 18. — the — Scrum Master photo by rawpixel on unsplash
  • 19. Scrum Master •Champion of process within their team •Coach the team and the business on Scrum & look for ways to fine-tune their process •Resolve impediments for the Dev Team, insulating them from external disruptions when possible •Defend against a common Scrum anti-pattern: changing a sprint's scope after it has begun •Also not a project manager!
  • 20. Scrum Master •What happens when there’s no dedicated Scrum Master? •Avoid conflicts of interest — Product Owners should not act as Scrum Masters •Rotating the Scrum Master role through the Dev Team can inject fresh ideas •Best to worst: Dedicated Scrum Master, Shared Scrum Masters, Engineer Scrum Master, No Scrum Master
  • 21. — the — Scrum Rituals
  • 22. Scrum Rituals •Prescribed events create regularity and minimize the need for meetings not defined in Scrum •All events are time-boxed •Other than the sprint itself, each event is a formal opportunity to inspect and adapt
  • 23. The Sprint A fixed length of work during which a “Done,” useable, and potentially releasable product increment is created.
  • 24. The Sprint •Once started, no changes that would endanger the sprint goal •That includes adding user stories or changing sprint length •Sprint cancellations are traumatic to the Scrum team, and are very uncommon
  • 25. How Long is a Sprint? •Sprint length can range from 1–4 weeks •2 weeks is pretty standard •You can get more done in a longer sprint, 
 but you’re less capable of reacting to changes •Keeping sprint length consistent gives the Dev Team critical feedback on estimation & delivery process, makes forecasts increasingly accurate over time.
  • 26. Product Backlog Grooming The team reviews and estimates user stories in the product backlog
  • 27. Product Backlog Grooming •Duration: 1 hour / week of sprint •Happens: Could be anytime, but often first day of sprint, or alternate Mondays •Attendees: scrum team •Purpose: The Product Owner gets help with the product backlog.
  • 28. What’s a Product Backlog? An ordered list of user stories for everything known to be needed in the product •Single source of requirements for any changes to be made to the product •Product Owner is responsible for the product backlog, including its content, availability, and ordering •A product backlog is never complete
  • 29. What are User Stories? •As a {type of user}, I want {functionality} 
 so that I {receive benefit} •Sketched out by Product Owner •Should describe a problem, not prescribe a solution •Dev Team helps refine •Can this be done? Do we need more information? Should it be broken into smaller stories?
  • 30. How Do We Estimate? •Dev Team plays planning poker to assign story points •Points rate the relative effort of work, not time to complete •Estimated relative to other well-understood work.
 “Is this more or less complicated than that story?” •Abstraction avoids the “Architect can do it in 2 hours, but the intern needs a full week” problem •Estimates will be inaccurate until the team establishes a common baseline after a few sprints
  • 31. Sprint Planning The team determines their sprint capacity and pulls stories from the product backlog
  • 32. Sprint Planning •Duration: 2 hours / week of sprint
 (new teams may need more time) •Happens: first day of the sprint •Attendees: scrum team •Purpose: The Dev Team plans their work with guidance from the Product Owner
  • 33. Sprint Planning •Capacity for the sprint is determined by reviewing velocity •User stories are pulled in order from the top of the product backlog •The team breaks user stories into tasks for the sprint backlog •Define a sprint goal to provide context and guidance to the team
  • 34. What’s a Sprint Backlog? An ordered list of tasks created from user stories accepted into the current sprint •Stories must be estimated and contain clear
 acceptance criteria •Should not change once the sprint starts, because the Dev Team is making a informed commitment to deliver this body of work. •What about bugs and P0 interruptions?
 (they’re going to happen!)
  • 35. What is Velocity? A measure of the amount of work a Scrum team can complete during a single Sprint •Calculated as a rolling average of the story points completed in previous sprints •It takes several sprints before a useful velocity metric can be determined •Velocity is only for planning! Team success should be based on value delivered.
  • 37. Daily Scrum a.k.a. Standup The Dev Team plans their work for the next 24 hours and checks progress towards sprint goal
  • 38. Daily Scrum •Duration: 15 min timeboxed •Happens: every day •Attendees: Dev Team, Scrum Master. Product Owner optional. • If others are present, the Scrum Master ensures that they do not disrupt the meeting. •Purpose: The Dev Team checks their progress toward the sprint goal
  • 39. Daily Scrum •Check progress by: •Answer the three questions •Review the burndown chart •This is a meeting for the Dev Team,
 not a detailed status report for management •Blockers should be escalated to Scrum Master
  • 40. What are the Three Questions? •What did I do yesterday that helped the Dev Team meet the sprint goal? •What will I do today to help the Dev Team meet the sprint goal? •Do I see any impediment that prevents me or the Dev Team from meeting the sprint goal? •This is not “justify your salary” time.
 Answers should be relevant to the sprint goal.
  • 41. What’s a Burndown Chart? Shows the work completed over time compared to an ideal trend line •Reviewing this chart can be a useful tool to see if the Dev Team is on-track to complete their work •If the burndown line extends beyond the trend line, the team may be falling behind their goal •If the burndown line makes steep drops, the team should work on breaking stories into smaller tasks
  • 43. Sprint Review An informal demo of what was achieved by the team to the Product Owner and other stakeholders
  • 44. Sprint Review •Duration: 30 min / week of sprint •Happens: last day of the sprint •Attendees: scrum team, key stakeholders invited by Product Owner •Purpose: Demonstrate work and get feedback
  • 45. Sprint Review •Focus on the product, not the process •Work should be fully demonstrable and meet the team's definition of “Done” to be considered complete and ready to showcase in the review •Celebrate success •Gather feedback, which should channel back into the product backlog
  • 46. Sprint Retrospective A review of what did and didn't go well with actions to make the next sprint better.
  • 47. Sprint Retrospective •Duration: 30 min / week of sprint •Happens: last day of the sprint •Attendees: scrum team (no management!) •Purpose: Review and improve process
  • 48. Sprint Retrospective •Focus on improving process, not the product •Not a time for complaints without action •Reflect on what went well during the sprint so the team can continue to focus on those areas •Find out what's not working and use the time to find creative solutions and develop an action plan
  • 51. Scrum Values •Transparency: nothing happens in the dark. The product backlog is visible, estimates are shared, velocity is tracked, definition of done is clear, etc. •Inspection: Inspect Scrum artifacts frequently, but not so frequently it gets in the way of work. •Adaption: If something isn’t working, adjust course as quickly as possible.
  • 52. Learn More •The Scrum Guide
 https://www.scrumguides.org/ •Scrum Rituals, Summarized
 https://wp.me/p27LsI-3G •Atlassian Scrum Guide
 https://www.atlassian.com/agile/scrum Scott Vandehey — spaceninja.com — @spaceninja