introduction to agile/scrumscrum.clearlytech.com/introtoagilescrum.pdf · • scrum is an agile...
TRANSCRIPT
Introduction to Agile/Scrumprepared by Will Koffel
credits to:Mike Cohn @ MountainGoat Software
Rob Sherman @ theagilemindset.org
• Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
• It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
• The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
• Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
Scrum in 100 words
Where Did Agile Come From?
Lean Principles (manufacturing, Toyota)Eliminate wasteAmplify learningDecide as late as possible, Deliver as fast as possibleEmpower the team, Build in integrity
Incremental/Iterative/Adaptive software practices (1950s-70s)“The New New Product Development Game” by Hirotaka Takeuchi and Ikujiro Nonaka (HBR, 1986)
The dreaded “waterfall”
Today is thedumbest day
of our whole project.
Always defer decisions you can defer, because you
learn more every day
Scrum vs Traditional PM
Three Roads Diverged
Agile Manifesto
Individuals and Interactions
Working Software
Customer collaboration
Responding to change
over processes and tools
over comprehensive documentation
over contract negotiation
over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Agile Values
• respect for the worth of every person• truth in every communication• transparency of all data, actions, and decisions• trust that each person will support the team• commitment to the team and to the team’s goals
Scrum Mechanism
Wishlist
ProductBacklog
Sprint Backlog
Planning
Daily Scrum
Sprint(n working days)
SprintRetrospective
Sprint Review
PotentiallyShippable Incrementof product
time
Scrum Framework
•Product owner•ScrumMaster•Team
Roles
•Sprint planning•Sprint review•Sprint retrospective•Daily scrum meeting
Ceremonies
•Product backlog•Sprint backlog•Burndown charts
Artifacts
Scrum RolesProduct Owner
Business Value Driver, Voice of the CustomerVision KeeperUltimately Responsible for Acceptance
Scrum MasterKeeper of the ProcessImpediment RemoverTeam Champion / Heat Shield
TeamCross-functional (able to do many jobs)Self-organizing (no fixed jobs/titles)Self-managing (no boss micro-managing)
Scrum Ceremonies
Daily ScrumWhat did you do yesterday?
What will you do today?
What’s stopping you?
Sprint PlanningBacklog GroomingSprint Review/Retro
Scrum Artifacts
Product BacklogSprint BacklogBurndown and ReportsShippable Increment of Product
User Stories
Expression of business value (not requirements)
Describe what should be done, not how to do it.
Brief, meant to be fodder for discussion
Decorated w/details from whole team
Decorated w/acceptance-criteria, what is “done”?
As a <role>, I want <feature, function>, so that <value>.
User Stories
INVEST criteria for writing storiesI - IndependentN - NegotiableV - ValuableE - EstimableS - SmallT - Testable
