Scrum?

Agenda themalunch

12:15 Sprint 0

• Waarom deze themalunch

• Bespreken rol- en

taakverdeling

• Bespreken backlog

• Vaststellen DoD

12:30 Sprint 1

12:50 Sprint 2

13:10 Sprint 3

13:30 Evaluatie

• What’s next?

Per Sprint (20 minuten)

• Sprint backlog vaststellen (2

minuut)

• Sprint backlog afwerken (16

minuten)

• Retrospective (2 minuut)

Scrum history

1986 ‘The New New Product Development Game’ by Takeuchi and Nonaka

1993 First Scrum project at Easel Corporation

1995 ‘SCRUM Software Development Process by Sutherland and Schwaber

2001 Agile Manifesto

2001 First book about Scrum by Schwaber and Beedle

ScrumTeam commitment

“Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.”

Waterfall

Royce (1970) identified 5 things to reduces risk in waterfall projects:1. Program Design Comes First2. Document the Design3. Do It Twice: “build it once, throw it away, and then

build the real thing”4. Plan, Control, and Monitor Testing5. Involve the Customer

Incremental

Iterative

Incremental & Iterative

Scrum in one slide

Scrum in one slide

Team is committed to the

sprint goal. Stakeholders

may observe and create

input as long as it does not

influences the sprint goal

They are self-organizing.

Development Teams are cross-functional

Individual Development Team members

may have specialized skills and areas of

focus, but accountability belongs to the

Development Team as a whole.

Scrum in one slideSprints are always the

same length. By working on

tasks and keeping progress

the team burns up or down

hours.

Scrum in one slide

Once the team gets a business goal, it:

• Figures out how to do the work

• Does the work

• Identifies what's getting in its way

• Takes responsibility to resolve all the

difficulties within its scope

• Works with other parts of the

organization to resolve concerns

outside their controlScrum Master:

Coaching the Development

Team

Removing impediments

Facilitating Scrum events as

requested or needed

Scrum in one slide

Product backlog is a list of

features prioritized from

high to low and from clear

to fuzzy. Team works on

the tasks high prio, clear

and (technical) risky tasks

first.

“Express value, defer

decisions”

Product Owner is the sole person

responsible for managing the Product

Backlog.

• Clearly expressing Product Backlog

items;

• Ordering the items;

• Ensuring that the Product Backlog is

visible, transparent, and clear to all, and

shows what the Scrum Team will work on

next;

• Ensuring the Development Team

understands items in the Product Backlog

to the level needed.

Scrum in one slide

Sprint planning is meant to

let the team discover what

to build, why to build it and

a task is really about. The

result is a sprint backlog

with tasks (and possibly

subtasks)

Scrum in one slide

The team keeps a daily

track of progress in an

always visible and up to

date planning board.

Scrum in one slideScrum doesn’t tell you what

“done” means, only to

define it and inspect and

adapt on a regular basis.

Scrum in one slideWhat went well?

What went wrong?

How can we measure and

improve our process?

Scrum values

Focus

Because we focus on only a

few things at a time, we

work well together and

produce excellent work.

We deliver valuable items

sooner.

Work together

Eye for quality

Scrum values

Courage

Because we work as a team,

we feel supported and

have more resources at

our disposal. This gives us

the courage to undertake

greater challenges.

Courage

Scrum values

Openness

As we work together, we

express how we're doing,

what's in our way, and our

concerns so they can be

addressed.

Give and receive feedback

Scrum values

Commitment

Because we have great

control over our own

destiny, we are more

committed to success.

Commitment

Scrum values

Respect

As we work together, sharing

successes and failures, we

come to respect each other

and to help each other

become worthy of respect.

Respect

Scrum “by the book”

Scrum at OOSE

When/why/where to use

ScrumProjects with:

• Big risks

• Requirements not clear

• Requirements change

• Cross functional members

• High customer involvement

• Tasks small enough to be performed in a rather small timebox

• Team commitment: full-time

Scrum principles have their origin outside software development but is mainly targeted for delivering software. However, succesful “ports” of Scrum are available, like eduScrum (scrum@school).

Waterfall:• Fear to go the next phase• Analysis Paralysis• Time wasted on junk• Projects take to long• Not time for testing

Waterfall:• Change gets more and

more expensive• Customers don’t get what

they want

Scrum results

Managed uncertainty

Flexible scope

Faster delivery

Higher quality

Eliminated Waste

Increased Visibility

eduScrum

(scrum@school)Scrum can be applied to teaching

• Teacher/lecturer as Product Owner, determining the product backlog

• Students working in teams of 4 members including 1 eduScrum Master

• Divide your course in timeboxes with clear goals and quality requirements. Students have to find out themselves what tasks to do to reach the goal.

• Sprint goal can be an product(increment), assignment, case study or test

• https://www.leraar24.nl/video/6089#tab=0

Research proposal submitted for “FT onderzoekt”

Possible pilot in OOSE• 4 sprints of 2 weeks• Student driven learning

instead of teacher driven• Better prepared for project• Integrated Professional Skills

TrustAutonomyHappinessPersonal DevelopmentBroad SkilledCross-team Collaboration

“Scrum is a process framework that has been used to manage complex product development since the early 1990s. A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.”

Role of teacher: Building

trust

Tools

Flaps

• Physical scrum board with sticky notes

• Excel sheet for burndowns

Trello

• Digital scrum board with digital sticky notes

• Excel sheet for burndowns

JIRA

• Digital scrum board with digital sticky notes and automatic reporting and burndowns

In random order

Easy to maintainOnly available for team in the roomNo reporting

Easy to maintainAvailable for every member anywhereNo sense of sprintsNo reporting (Chrome plugin available)No burndowns (Chrome plugin available)No estimation (Chrome plugin available)

Steep learningcurveExpensive or need community license (OOSE)Sprints, reporting, estimation and burndownsIntegrates with wiki and version control (traceability)