Scrum

Nothing endures but change (Heraclitus)

Tuesday, 1 October 13

Why do we do Scrum?
Tuesday, 1 October 13

No, seriously, why?

Standup and close your eyes

Tuesday, 1 October 13

Standup and close your eyes

Delivered late on several occasions Disappointed to your customers Spent over the budget Received changing requirements Experienced team changes Developed features that nobody uses ...

Tuesday, 1 October 13

What were we using in the past?

Waterfall Its great strength is that it is supremely logical: think before you build, write it all down, follow a plan, and keep everything as organized as possible.

Tuesday, 1 October 13

Waterfalls weakness
Tuesday, 1 October 13

Waterfalls weakness
Tuesday, 1 October 13

Humans are not machines

Tuesday, 1 October 13

What is Scrum?
Tuesday, 1 October 13

Frequent Inspection Direct Experience Adjustment & Adaptation

Inspect and Adapt

Tuesday, 1 October 13

Endless cycle

Tuesday, 1 October 13

Scrum values
Focus Visibility Respect Commitment Courage

Tuesday, 1 October 13

Focus activity
Goal 1 2 3 ... 26 a b c ... z I II III ... XXVI Raise your hand when you nish!

Two groups
Group A:
Columns: - 1, 2, 3... 26 - a, b, c... z - I, II, III... XXVI

Group B:
Rows: - 1, a, I - 2, b, II - ... - 26, z, XXVI

Time: 2 min

Tuesday, 1 October 13

Tuesday, 1 October 13

Scrum Roles
Tuesday, 1 October 13

Who is who

Product Owner
Tuesday, 1 October 13

Owner of the project vision Represents the customer

Dene features (according to vision) Prioritize features (according to ROI) Pick release dates Give feedback Manage stakeholders Accept or reject results

Product Owner
Tuesday, 1 October 13

Owner of the project vision Represents the customer

The Team
Tuesday, 1 October 13

Small (59 people) Colocated - Cross-functional Self-organized - Full-time

Dene tasks Estimate effort Develop product Ensure quality Evolve processes

The Team
Tuesday, 1 October 13

Small (59 people) Colocated - Cross-functional Self-organized - Full-time

Scrum Master
Tuesday, 1 October 13

Servant leader, team protector, troubleshooter, Scrum guide...

Remove impediments Prevent interruptions Facilitate the team Support the process Manage management

Scrum Master
Tuesday, 1 October 13

Servant leader, team protector, troubleshooter, Scrum guide...

Lets scrum it!

4 Teams 1 Product Owner 3 Team members Goal: Try to reproduce a drawing

Tuesday, 1 October 13

A&B can: - Speak as much as they want cant: - Write - Touch - Point - Draw C&D can: - Write as much as they want cant: - Speak - Touch - Point - Draw

Tuesday, 1 October 13

Auxiliary Energy

SOLAR COLLECTOR Primary Circuit

Secondary Circuit

ACS
ACCUMULATOR

Tuesday, 1 October 13

Retrospective & Conclusions

Tuesday, 1 October 13

Scrum artifacts
Tuesday, 1 October 13

As a user I want something so that benet As a who I want what so that why

User Story
Tuesday, 1 October 13

Product Backlog Item...

As a user I want something so that benet As a who I want what so that why where is the how? User Story
Tuesday, 1 October 13

Product Backlog Item...

INVEST
Independent
The user story should be self-contained, in a way that there is no inherent dependency on another user story

Negotiable
User stories, up until they are part of an iteration, can always be changed and rewritten

Valuable
A user story must deliver value to the end user

Estimable
You must always be able to estimate the size of a user story

Sized appropriately or Small

User stories should not be so big as to become impossible to plan/task/prioritize with a certain level of certainty

Testable
The user story or its related description must provide the necessary information to make test development possible

Tuesday, 1 October 13

Product Backlog
Tuesday, 1 October 13

Sprint backlog
Tuesday, 1 October 13

Denition of Done
Tuesday, 1 October 13

DONE DONE

Burndown chart
Tuesday, 1 October 13

Are we doing well?

Scrum meetings
Tuesday, 1 October 13

Sprint planning
Tuesday, 1 October 13

team capacity + product backlog + current product + business + technologies = GOAL

Daily Scrum
Tuesday, 1 October 13

Commitment and accountability Say what you do, do what you say Whole world is invited

Sprint review
Tuesday, 1 October 13

Satisfy Product Owner Get feedback on product

Sprint retrospective
Tuesday, 1 October 13

Evolve the process Reect on process and product Whole team participates

The airplane factory

Tuesday, 1 October 13

Basic description
Teams with 4-7 people (each team will represent a factory) We will build paper airplanes Iterations and re-planning of 2 minutes each
Unconditional respect of time!

Estimation before each sprint

Tuesday, 1 October 13

Rules
One fold per person and pass it on Must be a plane (wings) Must have a blunt tip Must have 6 windows Must y 3 meters 1/4 piece A4 paper per plane Test only on test strip Only tested/passed planes count WIP must be discarded at the end of the sprint

Tuesday, 1 October 13

Retrospective
Did you get what the client wanted in the beginning? Would a prototype have helped? Did the estimates get better as we better understand the requirements? Was the concept of inspect/ adapt useful? Was it useful to remove impediments? And changing the scope?

Tuesday, 1 October 13

Q&A

Tuesday, 1 October 13

References
Beck et al. Agile manifesto. http://agilemanifesto.org/ Cohn. Succeeding with Agile. http://www.succeedingwithagile.com/ Schwaber & Sutherland. Scrum Guide. https://www.scrum.org/Scrum-Guides Appelo. The Zen of Scrum. http://www.slideshare.net/jurgenappelo/the-zenof-scrum-10 Buenosvinos. Scrum al detalle. http://www.slideshare.net/carlosbuenosvinos/ scrum-al-detalle-revision-prctica-y-perversiones-humanas Beneeld & Deemer. Scrum Primer. http://scrumprimer.org/ Yip. Its not just standing up. http://martinfowler.com/articles/ itsNotJustStandingUp.html Dupuy. The Short Short Story. http://www.scrumalliance.org/community/ articles/2011/2011-june/the-short-short-story

Tuesday, 1 October 13