Presenter: Nhi

1 common understanding of some

Scrum building blocks

2 What is core values of Scrum?

“Scrum is a framework for developing complex products and systems. It is grounded in empirical process control theory. Scrum employs an iterative, incremental approach to optimize predictability and control

risks.”

--Ken Schewaber--

Complex product

Iterative, incremental approach

Scrum

framework

Empirical process control

theory

Complex product

Iterative, incremental approach

Scrum framework

Empirical process control theory

Agenda

Iterative, incremental

approach

Empirical process control

theory

Meetings: Daily, S.Review, Retrospective,… Product backlog – Product Grooming …

… … …

Image from: http://www.brookes.ac.uk/student/services/isas/blogs.html

Roles

Scrum Master

Product Owner

Scrum Team

Events

SprintSprint

PlanningDaily Scrum

Sprint ReviewSprint

RetrospectiveSprint

Grooming

Artifacts

Product Backlog

Sprint Backlog

Increment

Time-box

Events Time-boxed (maximum time)

Sprint 4 weeks

Sprint planning 8 hours

Daily meeting 15 min (fixed)

Sprint Review 4 hours

Sprint Retrospective 3 hours

Grooming 16 hours

Event time is proportional to Sprint time

No need for meetings not defined in Scrum

Limit overhead for communication: < 20%

When does a sprint end ?

Product

backlog• Includes: all items to be made– Features, functions, requirements– Enhancements– Fixes

• Important properties– Description– Order– Estimate

“As a student, I want to view my grades online

so that I do have to travel all the way long to

school to know it ”

INVESTI – IndependentN – NegotiableV – ValuableE – EstimableS – SmallT – Testable

From http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/

Product backlog

• Single source of requirements• A copy of the truth

Product Owner

Internal Stakehol

der

External Stakehol

der

Scrum MasterDevelop

ment Team

Product Backlog

• Notes:– Bugs from dev team

testing is within sprint backlog

– Bugs from ProductOwner/Users are in the Product Backlog

PB

I –

levels

of

deta

ils

Backlog refinement - Grooming

• Includes:– Filling the Product Backlog– Prioritizing PBI’s– Adding acceptance criteria– Splitting up large items

• Less than 10% of sprint time

Estimation

Estimation

not individuals

Work is assigned to an entire team … … not

individuals

Estimation

Not measure in time, but Effort

Planning poker

http://scrumtrainingseries.com/BacklogRefinementMeeting/

BacklogRefinementMeeting.htm

36/127

http://scrumtrainingseries.com/BacklogRefinementMeeting/

BacklogRefinementMeeting.htm

36/127

Definition of Done

DoD is a checklist of valuable activities required to produce software• Unit tests passs and coverage met standard (85%)• Code is reviewed (or pair programmed)• Code standards are met• Continues integration implemented (auto build, deployment and testing)• Code is refactored• Non-functinoal tests pass (scalability, reliability, security, etc.)• Document is completed

Spring Planning Meeting

Sprint Planning

Meeting

Product Backlog

Team Capabilities

Business Conditions

Technology

Current Product

Sprint Backlog

Produ

ct O

wner

Scrum

Tea

m

Man

agem

ent

Custo

mer

s

Sprint Goal

Parts of Sprint Planning Meeting

• 1st Part: What will be done?– Select Product Backlog items– Determining the Sprint Goal. – Participants: Product Owner, Scrum Master, Scrum Team

• 2nd Part: How will chosen work get done?– Participants: Scrum Master, Scrum Team– Creating Sprint Backlog

52/121

http://scrumtrainingseries.com/SprintPlanningMeeting/

SprintPlanningMeeting.htm

Scrum Team

• Self-organize

• Cross-function

Summary Part 1

Iterative, incremental

approach

Empirical process control theory

Time-box events Product backlog Product GroomingEstimation : 2 principles, planning poker Definition of DONE, technical debtScrum team: cross-.., self-..

…

Empirical= knowledge comes from

experience and making decisions based on what is

known

Empirical = Inspect & Adjust

Exp: Temperature control system for a room– What input parameter do you need?

Empirical

How does “Empirical ” expose in Scrum ?

3 Scrum pillars - Transparent

Transparent = Vision

You act on what you perceive

Transparent in Scrum

How does Scrum create transparency?

“Scrum is a framework for developing complex products and systems. It is grounded in empirical process control theory. Scrum employs an iterative, incremental approach to optimize predictability and

control risks.” --Ken Schewaber--

Summary

Iterative, incremental

approach

Empirical process control theory

Time-box events Product backlog Product GroomingEstimation : 2 principles, planning poker Definition of DONE, technical debtScrum team: cross-.., self-..

Empirical = inspect and adaptTransparent is all Scrum founded on

• http://www.scrum.org• http://scrumtrainingseries.com/• http://qualityswdev.com/2010/02/2

4/how-transparent-is-scrum/• … (and a lot more)

&Thank you