Scrum - A Short Tour
Click here to load reader
-
Upload
vineet-patni -
Category
Software
-
view
1.834 -
download
0
Transcript of Scrum - A Short Tour
![Page 1: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/1.jpg)
Scrum – A Short TourBy:
Vineet PatniPMP, PMI-ACP, PMI-PBA, SPC, CSP, CSM, CSPO
www.ScaleUpConsultants.com
![Page 2: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/2.jpg)
https://in.linkedin.com/in/patnivineethttps://twitter.com/patnivinhttps://in.linkedin.com/in/patnivineethttps://twitter.com/patnivin
ScaleUp
www.ScaleUpConsultants.com
Vineet PatniFacilitator-Coach-Speaker-Writer
Vineet PatniFacilitator-Coach-Speaker-Writer
![Page 3: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/3.jpg)
© 2014, Scale Up Pvt. Ltd. 3 3
The Agile Manifesto & Principles The Agile Umbrella Scrum Process Scrum Roles Scrum Events Scrum Artifacts
Scrum
![Page 4: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/4.jpg)
© 2015, Scale Up Pvt. Ltd. 44
The Agile Manifesto
in February , 2001• Kent Beck• Mike Beedle• Arie van
Bennekum• Alistair Cockburn• Ward
Cunningham• Martin Fowler• James Grenning• Jim Highsmith• Andrew Hunt• Ron Jeffries• Jon Kern• Brian Marick• Robert C. Martin• Steve Mellor• Ken Schwaber• Jeff Sutherland• Dave Thomas
source: www.agilemanifesto.orgsource: http://agilemanifesto.org
![Page 5: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/5.jpg)
© 2015, Scale Up Pvt. Ltd. 55
Agile Principles
source: http://agilemanifesto.org
![Page 6: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/6.jpg)
© 2015, Scale Up Pvt. Ltd. 66
Agile Principles…
SatisfyCustomer
HarnessChange
DeliverFrequently
WorkTogether Daily
MotivatedIndividuals
Face-to-FaceConversation
MeasureWorkingSoftware
Sustainedpace
TechnicalExcellence
Keep it simpleSelf
OrganizingTeams
Reflect-Tune-Adjust
![Page 7: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/7.jpg)
© 2015, Scale Up Pvt. Ltd. 77
The Agile Umbrella
source: http://www.agigante.it/scrum-and-agile-synonyms-and-other-agilemethodologies/
![Page 8: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/8.jpg)
© 2014, ScaleUp Training and Consulting 8
Scrum
![Page 9: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/9.jpg)
© 2015, Scale Up Pvt. Ltd. 99
A scrum (short for scrummage) is a method of restarting playin rugby.
The players pick the ball and sprint towards the goal post.
Scrum…
![Page 10: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/10.jpg)
© 2015, Scale Up Pvt. Ltd. 1010
What is Scrum?
A process framework for developingcomplex software products Lightweight Simple to understand Difficult to master
Scrum’s NOT a process or atechnique for building products
![Page 11: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/11.jpg)
© 2015, Scale Up Pvt. Ltd. 1111
The Scrum Process
source: http://www.supraliminalsolutions.com/
![Page 12: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/12.jpg)
© 2015, Scale Up Pvt. Ltd. 1212
Scrum – Key Characteristics
One of the Agile methodologies Requirements are captured as items in a
list of “product backlog” Product progresses in a series of month-
long “sprints” No specific engineering practices
prescribed Self-organizing teams
![Page 13: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/13.jpg)
© 2015, Scale Up Pvt. Ltd. 1313
The Scrum Theory
Empirical process control theory Knowledge comes from experience
and observation, and makingdecisions based on what is known.
An iterative, incremental approach tooptimize predictability and control risk.
![Page 14: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/14.jpg)
© 2015, Scale Up Pvt. Ltd. 1414
3 Pillars of Scrum
Transparency:Giving visibility to thesignificant aspects of theprocess to those responsiblefor the outcome.
Adaptation:Adjusting a process as soon aspossible to minimize anyfurther deviation or issues.
Inspection:Timely checks on the progresstoward a Sprint Goal to detectundesirable variances.
![Page 15: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/15.jpg)
© 2015, Scale Up Pvt. Ltd. 1515
Scrum Values
![Page 16: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/16.jpg)
© 2015, Scale Up Pvt. Ltd. 1616
Scrum provides a common vocabulary
Product Backlog:All work to be performed in the foreseeable future, both well-defined and
requiring further definition.
Sprint:A period of 30 days of less where a set of work will be performed to create a
deliverable.
Sprint Backlog:That work that is well enough defined that it can be worked on with relatively
little change over a period of 30 days or less and will result in a tangible,incremental deliverable.
Daily Scrum:A daily meeting at which progress and impediments to progress is reviewed.
Scrum provides a common language for the common sense way oforganizing, performing, and managing work.
![Page 17: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/17.jpg)
© 2015, Scale Up Pvt. Ltd. 1717
What’s all in Scrum…
The Scrum Process Scrum Roles Scrum Events Scrum Artifacts
It’s all in a “Sprint” Sprint is the heart of Scrum. Time-box of one month or less.Work is done during a Sprint, , andProduct Increment is created. Constant duration brings in developmentcadence.
![Page 18: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/18.jpg)
© 2015, Scale Up Pvt. Ltd. 1818
Sprint
Time-box of one month or less, during which..
The product is designed, coded and tested,and..
A “Done”, useable, and potentially releasableProduct Increment is created.
Sprints are of consistent duration during aDevelopment effort, and placed back-to-back.
![Page 19: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/19.jpg)
© 2015, Scale Up Pvt. Ltd. 1919
During a Sprint…No changes are made that would endanger
the Sprint Goal.
Scope may be clarified and re-negotiatedbetween the Product Owner andDevelopment Team.
Plan sprint durations around how long you cancommit to keeping change out of the sprint
![Page 20: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/20.jpg)
© 2015, Scale Up Pvt. Ltd. 2020
Cancelling A Sprint…
Sprint can be cancelled before the Sprinttime-box is over if the Sprint Goal becomesobsolete.
Only the Product Owner has the authorityto cancel the Sprint.
![Page 21: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/21.jpg)
© 2015, Scale Up Pvt. Ltd. 212121
Scrum Roles
![Page 22: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/22.jpg)
© 2015, Scale Up Pvt. Ltd. 2222
Scrum Roles
source: https://www.safaribooksonline.com/library/view/the-professional-scrummasters/9781849688024/ch01s04.html
![Page 23: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/23.jpg)
© 2015, Scale Up Pvt. Ltd. 2323
Scrum Roles...
source: https://hoangluongsjsu.wordpress.com/2014/09/21/the-agile-team-and-what-is-a-backlog-what-are-they-for-and-why-are-they-important/
![Page 24: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/24.jpg)
© 2015, Scale Up Pvt. Ltd. 2424
Product Owner
Responsible for maximizing the ROI - value of the product Customer Representative – Final authority
representing the customer's interest Manages theProduct Backlog (prioritization and clarifyingrequirements)
.. is a sole person, not a group or committee Accepts or rejects deliverables created by the team Must be "available" to the team at any time Facilitates the Sprint review meeting Must resist the temptation to “manage” the team
or the team’s work Must not try to add more work while the Sprint is in
progress. Balance the interests of all stakeholders
![Page 25: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/25.jpg)
© 2015, Scale Up Pvt. Ltd. 2525
Product Owner…
source: https://agilefaq.wordpress.com/2012/08/12/what-does-a-scrum-product-owner-do/
![Page 26: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/26.jpg)
© 2015, Scale Up Pvt. Ltd. 2626
Development Team
Responsible for delivering apotentially shippable
increment of working software
Anyone working on sprinttasks toward the sprint goal.
Self-organized Cross-functional Defines practices 5 to 9 persons Membership should be full-
time and change onlybetween sprints.
![Page 27: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/27.jpg)
© 2015, Scale Up Pvt. Ltd. 2727
Scrum Master
Responsible for in Scrum adoption andensures Scrum is understood and enacted Management Representative Team facilitator Inculcates Scrum values within team Coach Servant Leader Monitoring & Tracking Reporting & Communication Removes impediments Resolves conflicts Shields the team Team motivator
![Page 28: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/28.jpg)
© 2015, Scale Up Pvt. Ltd. 2828
Scrum Master…
source: http://illustratedagile.com/2011/12/13/the-scrum-master-performance-review-preparation/
![Page 29: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/29.jpg)
© 2015, Scale Up Pvt. Ltd. 2929
Where is the Project Manager?
![Page 30: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/30.jpg)
© 2015, Scale Up Pvt. Ltd. 303030
Scrum Events
![Page 31: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/31.jpg)
© 2015, Scale Up Pvt. Ltd. 3131
Scrum Events…
Sprint Planning• How much of the Product Backlog?• What can be done this Sprint?• How will the chosen work get done?
Daily Stand-up• 15-minute time-boxed event.. to plan for next
24 hours• Every team member - “What did I do?”, “What
do I plan to do?” and “Where I am stuck?”
!! Sprint Goal !!
!! Commitment,focus !!
![Page 32: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/32.jpg)
© 2015, Scale Up Pvt. Ltd. 3232
Scrum Events…
Sprint Review• Four-hour time-boxed meeting at the end of the
Sprint• Inspect the Increment and adapt the Product Backlog• The Scrum Team and stakeholders collaborate about
what was done in the Sprint
Sprint Retrospective• Two-hour time-boxed meeting after the Sprint Review• Reflect on last Sprint with regards to people,
relationships, process, and tools• Create Action plan for potential improvements
!! Demo !!
!! Looking back !!
![Page 33: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/33.jpg)
© 2015, Scale Up Pvt. Ltd. 333333
Sprint Planning
![Page 34: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/34.jpg)
© 2015, Scale Up Pvt. Ltd. 3434
Sprint Planning The work to be performed in the Sprint is planned at the Sprint
Planning. This plan is created by the collaborative work of the entire Scrum
Team. The Scrum Master facilitates the Sprint Planning meeting and
keeps it time-boxed.
![Page 35: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/35.jpg)
© 2015, Scale Up Pvt. Ltd. 3535
Sprint Planning… “What can be delivered in the Increment resulting from the
upcoming Sprint?“
“How will the work needed to deliver the Increment beachieved?”
![Page 36: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/36.jpg)
© 2015, Scale Up Pvt. Ltd. 3636
Sprint GoalA short statement of what the work will be focused
on during the sprint
The objective set for the Sprint, created during theSprint Planning meeting.
Provides guidance and flexibility to theDevelopment Team.
![Page 37: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/37.jpg)
© 2015, Scale Up Pvt. Ltd. 3737
From Sprint Goal to Sprint BacklogScrum team takes the Sprint Goal and decides what
tasks are necessary
Team self-organizes around how they’ll meet theSprint Goal
Manager doesn’t assign tasks to individuals
Sprint Backlog is created
![Page 38: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/38.jpg)
© 2015, Scale Up Pvt. Ltd. 3838
Sprint Backlog creation…
As a …..,I want ……..
User Story
TASK LIST
Sprint Backlog
Task 1: Code Task 2: Test Task 3: Automate ….. ….
![Page 39: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/39.jpg)
© 2015, Scale Up Pvt. Ltd. 3939
Sprint Planning…
• Product Owner• Development Team• Customers• Management
Who
• To come up with the Sprint Goal• To create the Sprint BacklogPurpose
• At the start of each SprintWhen
![Page 40: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/40.jpg)
© 2015, Scale Up Pvt. Ltd. 404040
Daily Stand-up
![Page 41: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/41.jpg)
© 2015, Scale Up Pvt. Ltd. 4141
Daily Stand-upThe Daily Scrums are short and crisp team meetings.
Maximum 15 minutes.
These happen at the same time, same place each day.
These are not status sessions for the manager / ScrumMaster.
Not for problem solving.
They are team members’ commitments in front of theteam.
![Page 42: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/42.jpg)
© 2015, Scale Up Pvt. Ltd. 4242
What did I do yesterday (last 24 hours)?
What will I do today (next 24 hours)?
What’s blocking my way (impediments)?
Each participant answers 3 questions
Are “we” on the right track to achieve our Sprint Goalduring this Sprint? If yes, Great! If no, what is holding us back?
Daily Stand-up…
![Page 43: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/43.jpg)
© 2015, Scale Up Pvt. Ltd. 434343
Sprint Review
![Page 44: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/44.jpg)
© 2015, Scale Up Pvt. Ltd. 4444
Sprint ReviewHeld at the end of the Sprint to inspect the Product
Increment and adapt the Product Backlog ifneeded.
The Product Owner facilitates the Sprint Review.
Attendees include the Scrum Team and keystakeholders invited by the Product Owner.
![Page 45: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/45.jpg)
© 2015, Scale Up Pvt. Ltd. 4545
Sprint Review…The Development Team demonstrates the work
that it has “Done” and answers questions about theIncrement.
The entire group collaborates on what to do next,so that the Sprint Review provides valuable input tosubsequent Sprint Planning.
The result of the Sprint Review is a revised andrefined Product Backlog that defines the probableProduct Backlog items for the next Sprint.
![Page 46: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/46.jpg)
© 2015, Scale Up Pvt. Ltd. 4646
Sprint Review…
• Product Owner• Scrum Master• Development Team• Key, Interested Stakeholders
Who
• To demonstrate completed work• To gather feedback• Refine the Product Backlog
Purpose
• At the end of each SprintWhen
![Page 47: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/47.jpg)
© 2015, Scale Up Pvt. Ltd. 4747
Sprint Review…
![Page 48: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/48.jpg)
© 2015, Scale Up Pvt. Ltd. 484848
Sprint Retrospective
![Page 49: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/49.jpg)
© 2015, Scale Up Pvt. Ltd. 4949
Sprint Retrospective
“A ritual held at the end of a project to learn fromexperience and to plan changes for the next effort".
Retrospectives are regular reviews of the team, bythe team, to discuss how they are working.
Focus is on the process, not the product.
![Page 50: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/50.jpg)
© 2015, Scale Up Pvt. Ltd. 5050
Sprint Retrospective…
A meeting where a team looks back on a past periodof work so that they can learn from their experienceand apply this learning to current / future projects.
What works (clear wins)?
What doesn’t work so well?
What do we need to start doing?
![Page 51: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/51.jpg)
© 2015, Scale Up Pvt. Ltd. 5151
A Retrospective is NOT…
A Retrospective is not a Post-Mortem: Aim to useRetrospectives regularly during the life of theproject rather than after catastrophic failure.
A Retrospective is not a Witch-Hunt: Retrospectivesare not about apportioning blame.
![Page 52: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/52.jpg)
© 2015, Scale Up Pvt. Ltd. 5252
Prime Directive
"Regardless of what we discover, we understandand truly believe that everyone did the bestjob they could, given what they knew at thetime, their skills and abilities, the resources
available, and the situation at hand.“
- Norm Kerth, Project Retrospectives: AHandbook for Team Reviews
![Page 53: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/53.jpg)
© 2015, Scale Up Pvt. Ltd. 5353
Retrospective Process
1. Set the stage
2. Gather Data
3. Generate Insights
4. Decide what to do
5. Close the Retrospective
Retrospective Process
![Page 54: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/54.jpg)
© 2015, Scale Up Pvt. Ltd. 5454
Retrospective Process1. Set the stage: Get everyone to speak. Agree on
rules. Use a safety exercise.2. Gather data: Feelings are legitimate data!3. Generate insights: “Why?” Begin discussing how to
do things differently.4. Decide what to do: Commit to one to two action
items or experiments.5. Close the retrospective: Review the retrospective
itself. Capture info. Thank all.
![Page 55: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/55.jpg)
© 2015, Scale Up Pvt. Ltd. 5555
• End of Iteration, Release or ProjectWhen
• For the team, by the team• Not for any individual team memberWho
• Inspect and Adapt ..• The process, not about the product.What
Sprint Retrospective…
![Page 56: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/56.jpg)
© 2015, Scale Up Pvt. Ltd. 565656
Scrum Artifacts
![Page 57: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/57.jpg)
© 2015, Scale Up Pvt. Ltd. 5757
Scrum Artifacts
• Single Source of all product requirements• Ordered list• Product Owner’s responsibility• Evolves over time, never complete
Product Backlog
• Sub-set of top priority PBIs• A Plan for delivering the product Increment
and realizing the Sprint Goal• Only the Sprint Team can change it
Sprint Backlog
• Sum of all the Product Backlog Items (PBIs)completed during a Sprint
• Must meet the “Done” criteria• Minimum shippable product
Product Increment
![Page 58: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/58.jpg)
© 2015, Scale Up Pvt. Ltd. 585858
Product Backlog
![Page 59: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/59.jpg)
© 2015, Scale Up Pvt. Ltd. 5959
Product BacklogAn ordered list of everything that might be needed in
the product
The single source of all product requirements (allfeatures, bugs, enhancements, non-functionalrequirements, etc.)
The objective of creating a Product Backlog is toexpand the product vision, through an evolutionaryrequirements definition process, into a productfeature list
![Page 60: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/60.jpg)
© 2015, Scale Up Pvt. Ltd. 6060
Product Backlog… Product Owner is accountable for the PB and any updates to
it.
Ordered based on risk, business value, dependencies, dateneeded, etc.
A Product Backlog is never complete, and evolvescontinuously.
The Product Backlog is dynamic, living artifact; and exists aslong as a product exists.
All Product Backlog Item (PBI) must have a value and a sizeestimate.
![Page 61: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/61.jpg)
© 2015, Scale Up Pvt. Ltd. 6161
Product Backlog……
A Product Backlog must be D.E.E.P.
![Page 62: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/62.jpg)
© 2015, Scale Up Pvt. Ltd. 6262
Sample Product Backlog
![Page 63: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/63.jpg)
© 2015, Scale Up Pvt. Ltd. 6363
Sample Product Backlog…
![Page 64: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/64.jpg)
© 2015, Scale Up Pvt. Ltd. 6464
Product Backlog Refinement
Product Backlog refinement is the act ofadding detail, estimates, and order to
items in the Product Backlog.This is an ongoing process.
Higher ordered Product Backlog itemsare usually clearer and more detailedthan lower ordered ones.
Product Backlog items that can be“Done” by the Development Teamwithin one Sprint are deemed “Ready”for selection in a Sprint Planning.
![Page 65: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/65.jpg)
© 2015, Scale Up Pvt. Ltd. 6565
Product Backlog Refinement
![Page 66: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/66.jpg)
© 2015, Scale Up Pvt. Ltd. 666666
Sprint Backlog
![Page 67: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/67.jpg)
© 2015, Scale Up Pvt. Ltd. 6767
Sprint BacklogA set of the Product Backlog items selected for the
Sprint, accompanied a plan for delivering theproduct Increment and realizing the Sprint Goal.
Serve’s as the Development Team’s forecast aboutwhat functionality will be in the next Sprint.
It’s a highly visible view of the work beingundertaken and may only be updated by thedevelopment team.
![Page 68: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/68.jpg)
© 2015, Scale Up Pvt. Ltd. 6868
Sprint Backlog…
The Sprint Backlog emerges during theSprint.
This emergence occurs as the DevelopmentTeam works through the plan and learnsmore about the work needed to achieve theSprint Goal.
![Page 69: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/69.jpg)
© 2015, Scale Up Pvt. Ltd. 6969
Sprint Backlog…Only the Development Team can change its Sprint
Backlog during a Sprint.
As new work is required, the Development Teamadds it to the Sprint Backlog. As work is performed or completed, the
estimated remaining work is updated. Task estimates are updated whenever there’s
new informationWhen elements of the plan are deemed
unnecessary, they are removed.
![Page 70: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/70.jpg)
© 2015, Scale Up Pvt. Ltd. 707070
Product Increment
![Page 71: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/71.jpg)
© 2015, Scale Up Pvt. Ltd. 7171
Product Increment
The Product Incrementis the sum of all the
Product Backlog itemscompleted during a
Sprint and the value ofthe increments of all
previous Sprints.
![Page 72: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/72.jpg)
© 2015, Scale Up Pvt. Ltd. 7272
Product Increment… Each Product Increment is additive to all prior Increments and
thoroughly tested, ensuring that all Increments work together.
At the end of a Sprint, the new Increment must be “Done,” which meansit must be in useable condition and meet the Scrum Team’s definition of“Done.”
It must be in useable conditionregardless of whether the ProductOwner decides to actually release it.
![Page 73: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/73.jpg)
© 2015, Scale Up Pvt. Ltd. 7373
Product Increment……
source: http://www.romanpichler.com/blog/the-definition-of-ready/
![Page 74: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/74.jpg)
© 2015, Scale Up Pvt. Ltd. 747474
So, Are we Done?
![Page 75: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/75.jpg)
© 2015, Scale Up Pvt. Ltd. 7575
Are we “Done”?
![Page 76: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/76.jpg)
© 2015, Scale Up Pvt. Ltd. 7676
Definition of Ready
The team makes explicit and visiblethe criteria that a user story must meetprior to being accepted into theupcoming iteration.
The team works with the PO to agreeon what defines a “ready” state of abacklog item.
![Page 77: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/77.jpg)
© 2015, Scale Up Pvt. Ltd. 7777
Definition of Ready… Example
Story defined and written Story traceable to source document (where appropriate) Acceptance criteria defined Dependencies identified Size estimated by delivery team User experience included (where appropriate) Performance criteria identified (where appropriate) Person who will accept the user story is identified Team has a good idea about how to demo the user story
![Page 78: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/78.jpg)
© 2015, Scale Up Pvt. Ltd. 7878
Definition of Done (DoD)
The definition of “Done” for the ScrumTeam is used to assess when work iscomplete on the product Increment.
A shared understanding of what itmeans for work to be complete toensure transparency.
The team should collectively createthe definition of done for the itemsbefore they begin work on them.
![Page 79: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/79.jpg)
© 2015, Scale Up Pvt. Ltd. 7979
Definition of Done (DoD)
Done means “Done” if…
It has been tested and has passed user acceptance orclient approval
It has passed an in-house iteration review It is “shippable” or “deliverable”
![Page 80: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/80.jpg)
© 2015, Scale Up Pvt. Ltd. 8080
Definition of Done (DoD)… Example
![Page 81: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/81.jpg)
© 2015, Scale Up Pvt. Ltd. 8181
![Page 82: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/82.jpg)
© 2015, Scale Up Pvt. Ltd. 8282
The Scrum Framework
by: Vineet Patni
![Page 83: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/83.jpg)
© 2015, Scale Up Pvt. Ltd. 83838383
Please reach out to us with feedback at:[email protected]
PMP, PMI-ACP, PMI-PBA, Agile (Scrum, Lean, Kanban, SAFe, DAD)
www.ScaleUpConsultants.com
https://www.linkedin.com/company/scale-up
https://twitter.com/ScaleUpPune
https://www.facebook.com/ScaleUpConsultants
https://plus.google.com/117837859519308773805/posts
https://www.youtube.com/channel/UCoCca2D-Wyof3fbS6vIdjRg/playlists
![Page 84: Scrum - A Short Tour](https://reader038.fdocuments.in/reader038/viewer/2022102322/586ff9041a28ab92198b782f/html5/thumbnails/84.jpg)
© 2015, Scale Up Pvt. Ltd. 84848484
We are Done!