23
SCRUM - Let’s make it simple Knowledge Session

Endouble Whitepaper scrum

Embed Size (px)

Citation preview

Page 1: Endouble Whitepaper scrum

SCRUM - Let’s make it simpleKnowledge Session

Page 2: Endouble Whitepaper scrum

Scrum knowledge session

About this knowledge session

2

» Quick recap of yesterday

» Different roles in Scrum for Endouble

» User Stories

» Putting it to use

Page 3: Endouble Whitepaper scrum

Scrum knowledge session 3

What is Scrum?

Scrum is a software development

framework in which a product is

developed in fixed time periods, in

which an improved version of the

product is released in predefined

iterations.

Quick recap

Page 4: Endouble Whitepaper scrum

Scrum knowledge session 4

Page 5: Endouble Whitepaper scrum

Scrum knowledge session

What’s the big difference?

5

Page 6: Endouble Whitepaper scrum

Scrum knowledge session 6

The Scrum process

Page 7: Endouble Whitepaper scrum

Scrum knowledge session

The pillars of Scrum

7

Page 8: Endouble Whitepaper scrum

Scrum knowledge session 8

Scrum stakeholders

These are the stakeholders within the Scrum

process at Endouble:

- Development Team

- Product Owner

- Scrum Master

- Project Manager

Page 9: Endouble Whitepaper scrum

Scrum knowledge session 9

Product Owner

The Product Owner is the stakeholder in the

Scrum process who shares his vision and wishes

with all the other stakeholders in the Scrum

process. He manages the backlog.

Unless...

Page 10: Endouble Whitepaper scrum

Scrum knowledge session 10

The Project Manager in our Scrum process takes

over communications with developers, manages

the backlog and helps optimise ‘user stories’ and

their priorities.

Project Manager

Page 11: Endouble Whitepaper scrum

Scrum knowledge session 11

The backlog

Page 12: Endouble Whitepaper scrum

Scrum knowledge session 12

What is a user story?

User stories are short, simple

descriptions of a feature told from the

perspective of the person who desires the

new capability, usually a user or

customer of the system.

Page 13: Endouble Whitepaper scrum

Scrum knowledge session 13

What does a proper ‘user story’ look like?

As a ____________ , I want _________ , so that ____________. ________________________ (optional)

As a <type of user>, I want <some goal> so that <some reason>. <limitations & priority are optional>

Page 14: Endouble Whitepaper scrum

Scrum knowledge session

“As an applicant, I would like to be able to generate a CV (Curriculum Vitae) based on my LinkedIn profile,

because I don’t have a proper CV of my own. We (Endouble) are not a LinkedIn-partner. This ticket has the

highest priority.”

I (as a role/user) want to be able to (functionality/action), because (goal/value for the role/user). (optional

limitations)

An example of a proper user story

14

Page 15: Endouble Whitepaper scrum

Scrum knowledge session

But… why should I care?

15

» You know your target audience best

» User stories are easily understandable by all stakeholder

» User stories allow Endouble to suggest solutions based on our own expertise

Page 16: Endouble Whitepaper scrum

Scrum knowledge session

Real life examples (1/2)

16

I, as an applicant, want to be able to quickly identify the

company’s tone-of-voice & online presence.

Page 17: Endouble Whitepaper scrum

Scrum knowledge session

Real life examples (1/2)

17

Page 18: Endouble Whitepaper scrum

Scrum knowledge session

Real life examples (2/2)

18

I, as an applicant, want to read company blogs, so I can learn

more about the company’s culture & activities.

Page 19: Endouble Whitepaper scrum

Scrum knowledge session

Real life examples (2/2)

19

Page 20: Endouble Whitepaper scrum

Scrum knowledge session 20

What defines a good ‘user story’?

» The stories need to be complete

A ‘user story’ should define the target audience, explain the desired result and the reason behind it.

» Conditions / limitations

In case there are limitations as to how the problem might be solved, it is important that they are mentioned

as well.

» Priorities

A user story is only as important as its priority. Always specify the priority.

Page 21: Endouble Whitepaper scrum

Scrum knowledge session 21

Let’s try it out!

Page 22: Endouble Whitepaper scrum

Scrum knowledge session 22

What does a proper ‘user story’ look like?

As a ____________ , I want _________ , so that ____________. ________________________ (optional)

As a <type of user>, I want <some goal> so that <some reason>. <Limitations & priority are optional>

Page 23: Endouble Whitepaper scrum

Scrum knowledge session

» [email protected]

» +31 (0) 20 240 0 240

» www.endouble.nl

Questions? Don’t hesitate to ask!

23