Scrum in Real Life

Eyal GolanTech Lead & Scrum Master @ eBay

Agenda

• About me• Team structure• Sprint structure• Discussion and examples

About Me

• Over 10 years development• Tech Lead & Scrum Master• Agile enthusiastic• Test addict

– TDD

• Software craftsmanship wave– Clean coder

Team Structure

• 6 Developers (PD)• 2 QE

– QA– QE

• PM

Sprint Structure

• 3 Weeks• 2 Planning days• 13 Development days• Start on Tuesday• Finish on Monday

Sprint Structure

Are we on track?

We’re on track

1 st Sprint

We’re on track

31 st Sprint

We’re on track

Vague Requirements

Time consuming planning

Changing requirements

Poor quality User story is not finished

Many opinions

User Story Smell

Vague Requirements

Test case review

Design review

Planning

Jira comments

email

Vague Requirements

Large User Story

Many decision branches

Touches many components

Easily divided User story is not finished

Lots of tasks

User Story Smell

Large User Story

Define better DoD

Work in parallelPlanning

Split the user story

Large User Story

Communication

Pre planning

Retrospective

Test case review

Planning

Jira

Daily

Communication

Demo

Understanding What We’re Doing

The Team

The Foundations

In order to be agile,

one must have

quality code

Pair programmingFeature code overview

Clean code

Code reviewDesign review

TDD

Quality Code

Refactoring

Fertilize and invest in quality

You can create a garden

Software is like gardening…

TEAM

Collective

Ownership

ATDDRelease hand-off

Release notes

Automation

Test case review

Continuous integration

SONAR (quality metrics)

Mock services

Agile vs. Waterfall

SKUBI

Q&A

Connect

• Blog– http://eyalgo.com/

• Twitter– @eyalgo_egolan– https://twitter.com/eyalgo_egolan

• LinkedIn– https://www.linkedin.com/in/egolan74