17
SCRUM User Role Modeling

Scrum user role modeling

Embed Size (px)

Citation preview

Page 1: Scrum user role modeling

SCRUMUser Role Modeling

Page 2: Scrum user role modeling

In order to prevent that every description of a

User Story start with “As a user, I want to …”

we use User Role Modeling techniques.

Even with simple applications there is no such

thing as ‘the user’.

Page 3: Scrum user role modeling

Users with identical rights may approach an

application in different ways.

Page 4: Scrum user role modeling

Who is the user?

Flickr user Ville Miettinen

Page 5: Scrum user role modeling

Mike Cohn dedicates a chapter in his

book “User Stories Applied” to

determining and defining users.

He provides a simple process that can be conducted within

approximately an hour with the participation of the

complete team.

Page 6: Scrum user role modeling

It has significant advantages to pay attention

to user determination.

Both the direct and the indirect results add, in

our opinion, so much value that we decided to

conduct ‘User Role Modeling’ in the proposal

stage, by default.

Page 7: Scrum user role modeling

The advantages

Flickr user Parker Knight

Page 8: Scrum user role modeling

Because every team member is allowed

to give unlimited input, a large variety of

possible users will be the initial outcome.

Page 9: Scrum user role modeling

Because the complete team participates in

the exercise, they get a better impression of

what the application could offer in terms of

functionality.

Page 10: Scrum user role modeling

The result

Flickr user Infusionsoft

Page 11: Scrum user role modeling

Aside from being able to create a user

structure including read, write and delete

rights, the insight in the required functionality

has increased.

Page 12: Scrum user role modeling

This allows for a better transformation from

an initial project description into Stories and

presenting these Stories in the right order.

Page 13: Scrum user role modeling

In our proposals, we try to represent the

result of this exercise. It obviously means our

proposals hold a description of the users as

we see them.

Page 14: Scrum user role modeling

But the result is also visible in the Stories

that better reflect the goal of the application,

because the team thought of the users and

their needs.

Page 15: Scrum user role modeling

READ MORE

DOWNLOAD THE FULL WHITE PAPER

Page 16: Scrum user role modeling

Maxcode Deliver your next finance or ehealth application.

Maxcode is an IT service company building tailor made applications for the European market. We focus on financial and healthcare industries. Maxcode is located in The Netherlands with offices in Romania, and the Republic of Moldova. We are a modern company and a reliable partner for our customers and employees.

Koninginnegracht 19 2514 AB Den Haag / The Hague The Netherlands [email protected]

Page 17: Scrum user role modeling

Disclaimer

The materials in this document may contain inaccuracies or typographical errors. Maxcode does not warrant the accuracy, reliability or completeness of the materials, advices, opinions, statements or any other information displayed or distributed in this document. All information in this document is provided “as is” and “as available”, and shall not be binding nor shall it be construed as constituting any obligation, representation or warranty on the part of Maxcode. You acknowledge that any reliance on any information in this document shall be at your sole risk. Maxcode mentions others, their products and ideas as a convenience to you. Those others, products and ideas are not under the control of Maxcode. Accordingly, Maxcode makes no representation or warranty in relation to others, their products, or ideas, other than simply listing them as relevant for your consideration. By listing them, Maxcode is not endorsing or recommending them to you.