scrum - a short tour

Scrum – A Short TourBy:

Vineet PatniPMP, PMI-ACP, PMI-PBA, SPC, CSP, CSM, CSPO

www.ScaleUpConsultants.com

https://in.linkedin.com/in/patnivineethttps://twitter.com/patnivinhttps://in.linkedin.com/in/patnivineethttps://twitter.com/patnivin

ScaleUp

Vineet PatniFacilitator-Coach-Speaker-Writer

The Agile Manifesto & Principles The Agile Umbrella Scrum Process Scrum Roles Scrum Events Scrum Artifacts

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

Agile Principles

source: http://agilemanifesto.org

Agile Principles…

SatisfyCustomer

HarnessChange

DeliverFrequently

WorkTogether Daily

MotivatedIndividuals

Face-to-FaceConversation

MeasureWorkingSoftware

Sustainedpace

TechnicalExcellence

Keep it simpleSelf

OrganizingTeams

Reflect-Tune-Adjust

The Agile Umbrella

source: http://www.agigante.it/scrum-and-agile-synonyms-and-other-agilemethodologies/

A scrum (short for scrummage) is a method of restarting playin rugby.

The players pick the ball and sprint towards the goal post.

Scrum…

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

The Scrum Process

source: http://www.supraliminalsolutions.com/

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

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.

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.

Scrum Values

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.

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.

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.

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

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.

Scrum Roles

source: https://www.safaribooksonline.com/library/view/the-professional-scrummasters/9781849688024/ch01s04.html

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/

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

Product Owner…

source: https://agilefaq.wordpress.com/2012/08/12/what-does-a-scrum-product-owner-do/

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.

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

Scrum Master…

source: http://illustratedagile.com/2011/12/13/the-scrum-master-performance-review-preparation/

Where is the Project Manager?

Scrum Events

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 !!

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 !!

Sprint Planning

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.

Sprint Planning… “What can be delivered in the Increment resulting from the

upcoming Sprint?“

“How will the work needed to deliver the Increment beachieved?”

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.

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

Sprint Backlog creation…

As a …..,I want ……..

User Story

TASK LIST

Sprint Backlog

Task 1: Code Task 2: Test Task 3: Automate ….. ….

Sprint Planning…

• Product Owner• Development Team• Customers• Management

• To come up with the Sprint Goal• To create the Sprint BacklogPurpose

• At the start of each SprintWhen

Daily Stand-up

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.

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…

Sprint Review

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.

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.

Sprint Review…

• Product Owner• Scrum Master• Development Team• Key, Interested Stakeholders

• To demonstrate completed work• To gather feedback• Refine the Product Backlog

Purpose

• At the end of each SprintWhen

Sprint Review…

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.

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?

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.

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

Retrospective Process

1. Set the stage

2. Gather Data

3. Generate Insights

4. Decide what to do

5. Close the Retrospective

Retrospective Process

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.

• 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…

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

Product Backlog

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

Product Backlog… Product Owner is accountable for the PB and any updates to

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.

Product Backlog……

A Product Backlog must be D.E.E.P.

Sample Product Backlog

Sample Product Backlog…

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.

Product Backlog Refinement

Sprint Backlog

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.

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.

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.

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.

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.

Product Increment……

source: http://www.romanpichler.com/blog/the-definition-of-ready/

So, Are we Done?

Are we “Done”?

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.

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

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.

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”

Definition of Done (DoD)… Example

The Scrum Framework

by: Vineet Patni

Please reach out to us with feedback at:Vineet@ScaleUpConsultants.com

Contact@ScaleUpConsultants.com

PMP, PMI-ACP, PMI-PBA, Agile (Scrum, Lean, Kanban, SAFe, DAD)

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

We are Done!

scrum - a short tour

Software

agile tour 2011 ralph jocham - scrum primer

tour - short landscape

agile tour 2010 - scrum turning scum - ignoring the false...

adventure short course - $250 flight attending short course...

scrum santhosh srinivasan. outline what is scrum what is...

the future present of scrum (agile tour dublin 2016)

a short tour of spatial platforms

a short tour of bad graphs

learn scrum in 6 steps - axosoftdaily scrum format:...

13 cities in eastern europe: a short tour

scrum –a tester’s perspective - agile...

st andrews, a short walking tour. · st andrews, a short...

tour of folksonomies delicious short

agile tour montréal 2010 - the lean within scrum par joe...

engineering long-lasting software: an agile · 1.10 guided...

csc301...2016/10/25 · scrum, detailed view of an agile...

introduction to scrum at agile tour beirut 2015

a short tour of linux history-[chetan]-

agile tour...

passer de scrum à scrumban - agile tour lausanne 2014