P I E R R E E . N E I S - S E N I O R A G I L E C O A C H A G I L E 2

S C R U M I N A B U S I N E S S O R I E N T E D C O N T E X T

F E AT U R E S & B U S I N E S S P R O C E S S E S

1P I E R R E E . N E I S - S E N I O R S C R U M C O A C H

TA B L E O F C O N T E N T

2

Composition of a Scrum Team

0 4

PA G E S 6

What means Scrum?

0 3

PA G E S 5

Your hard work will pay off

0 2

PA G E S 4

Business in Scrum

0 1

PA G E S 3

Building the right thing: purpose of Product Owner’s job

0 5

PA G E S 7

Minimal Toolbox to get the job done

0 9

PA G E S 1 1 - 1 4

Role of a Process Owner

0 8

PA G E S 1 0

The challenge for the Process Owner

0 7

PA G E S 9

Product Roadmap and development strategy

0 6

PA G E S 8

S A P B U S I N E S S I N S C R U M

End-to-end process • design and refine the process aligned with Release Roadmap

Collaboration• enhance Product Owner’s vision with Process Owners/Users • define Personae and create specific User stories and Themes • work as a team member of a cross-functional team

Knowledge • Interact with the Business Process community of practice (aka Chapter) to share, learn and improve standards

Build • set up the standard process as a hypothesis

Measure • set up a Definition-of-Done (DoD) for the E2E process • collect customer’s/user’s improvement (Sprint Review) and update • run User Testing workshops to test the hypothesis • Improve the measures

Visible metrics • Set metrics and capture mechanisms for both Customer and Delivery Teams • Display metrics so that all the teams share the same wall • Make it highly visible in the Communication Tool (Jira, Confluence)

Communication & collaboration

• Use intra-team, web-based collaboration (Jira, Confluence)

Scrum Team Rooms • Secure Scrum Team Rooms for each team; one room per Work stream • Group Work Stream Rooms in a common location/building • Use significant wall-space for creative boards and facilitate display of visible metrics • Install conference phones, video conference, whiteboards

Customer Lab • Recruit and schedule customers for regular testing • Use trained facilitators to conduct interviews (Training or Scrum Masters) • Set up a customer lab with recording equipment

3

A. Practices

B. Processes

C. Tools

D. Infrastructure

Y O U R H A R D W O R K W I L L PAY O F F

4T H E A G I L E M A N I F E S T O

Satisfy customer through early & continuous delivery

Agile processes harness change

Deliver working software frequently.

Business people and developers must work together

Build projects around motivated individuals.

Face-to-face conversation

Working software is the primary measure of progress

Sponsors, developers, and users should be able to maintain a constant pace

Continuous attention to technical excellence and good design

Simplicity--the art of maximizing the amount of work not done--is essential.

Self-organizing teams

At regular intervals, the team reflects how to become more effective

« We are losing the relay race », the old way on doing project is called waterfall. Instead of waste time in handovers, a empirical and holistic approach produces more value in less time for the customer as a team working together reaching a shared goal

W H AT M E A N S S C R U M ?

5

R E A D Y D O N E

C O M P O S I T I O N O F A S C R U M T E A M

B U I L D T H E R I G H T T H I N G B U I L D T H E T H I N G R I G H T

B U I L D I T FA S T

P R O D U C T O W N E R

D E V T E A M

S C R U M M A S T E R

P R O C E S S O W N E R

D E V E L O P E R

T E S T E R

D E L I V E RY M A N A G E R

6

The Scrum Team is composed by all the necessary skills to transform customer’s vision into great software. Project Management skills are distributed within the team: - Product Owner is

responsible for Product Development

- Scrum Master is responsible for development process, coordination and capacity

- Delivery Team is responsible to build it and for quality

B U I L D I N G T H E R I G H T T H I N G : P U R P O S E O F P R O D U C T O W N E R ’ S J O B

I N C H A R G E T O D E L I V E R T H E S O L U T I O N

T R A N S L AT E C U S T O M E R ’ S V I S I O N

W O R K W I T H U S E R S & C U S T O M E R S

C R E AT E , M A I N TA I N , R E F I N E T H E P R O D U C T

B A C K L O G

FEAT

URE

S FO

R U

SERS

END

-TO

-EN

D P

ROC

ESS

FOR

CU

STO

MER

USE

R ST

ORI

ES

BUSI

NES

S PR

OC

ESS

BUSI

NES

S PR

IORI

TIES

ROA

DM

AP

7

P R O D U C T R O A D M A P A N D D E V E L O P M E N T S T R AT E G Y

• Sprints delivers PSI i.e. features

• Releases delivers End-to-end processes incl. these features

• focus is given to involve both customer and user since the beginning of the solution development.

• Deliver standards from the easiest but most visible to the hardest.

• Each release should be actionnable so that the users and customer can start a work around of the solution and provide feedback

• Think about the integration of E2E processes.

• Done means ready to deploy and fit to RUN.

• Release phase is deliver standard and collect change and start custom

1 E 2 E P R O C E S S M O R E E 2 E P R O C E S S E S

M O R E E 2 E P R O C E S S E S

M O R E E 2 E P R O C E S S E S

M O R E E 2 E P R O C E S S E S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

FEAT

URE

S

S P R I N T

R E L E A S E

<S

PR

INT

>< R E L E A S E >

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

<S

PR

INT

>

< R E L E A S E > < R E L E A S E > < R E L E A S E > < R E L E A S E >

T I M E

PR

OD

UC

T B

AC

KL

OG

8Like for product increments, processes have to be delivered incrementally!

T H E C H A L L E N G E F O R T H E P R O C E S S O W N E R

• identify the User in a E2E process and create the US

• update the product roadmap with the Product Owner

• identify the User/Customer for E2E process

• define the persona aka User Role • collect User Stories from the Users • update the Product Backlog with

the Product Owner • ensure or write the tests cases • ensure that the E2E process is

INVEST (independent, negotiable, valuable, estimable, sized to fit, testable)

• ensure the integration of E2E processes in a single process

• update the process

• E2E is part of Release DoD • create the definition of done

(DoD) of the E2E process and work with the Product Owner to update the Release DoD accordingly

• E2E has to be drawn and visible to all stakeholders

• make the process visible from all stakeholders

• use visual management and facilitation techniques to enhance the product backlog

The end-to-end (E2E) process is the outcome and not the input of a the development process

9

build

measure learn

working software

R O L E O F A P R O C E S S O W N E R

10

• aka member of the Scrum Team

• as a team member, the process owner is self managed and cross-functional.

D E V E L O P

• Works with the Product Owner

• Acceptance Test Driven Development (wikipedia)

• Think Test automation2

• perform acceptance test and/or facilitate user acceptance test workshop aka Bootcamp

T E S TC O L L A B O R AT E

• as a team mate, the Process Owner helps the team to reach the Sprint Goal also for works that are outside his/her comfort zone

C O - W O R K

• not an authority

• all team members have the same hierarchical level within the Scrum team, that’s the rule of the Scrum Game

E Q U A L

M I N I M A L T O O L B O X T O G E T T H E J O B D O N E

11

B P M M AT U R I T Y P R O C E S S I M PA C T M A P P I N G AT T D O R B D D

B P M M AT U R I T Y P R O C E S S

SO

UR

CE

: B

PM

PR

OJE

CT

AS

SE

SS

ME

NT

12

The BPM Maturity Process insures that all the necessary points are covered to provide sustainable business processes. Maturity is a holistic approach and learning emerges from sprint to sprints.

I M PA C T M A P P I N G

1. discover real goals 2. define good

measurements 3. plan your first

milestone (ask: « if we can achieve the key targets for metrics with a completely different scope than planned, have we succeed? » If the answer is « No » go back to start: you don’t have the right metrics.)

4. draw the map skeleton 5. find alternatives 6. identify key priorities 7. earn or learn 8. measure progress

periodically against key milestone metrics

SO

UR

CE

: G

OJK

O A

DZ

IC

13

Impact Mapping is an agile framework to enable the proper setting up of business processes by shifting the customer into the core of the discussion. IM principles are…

A C C E P TA N C E T E S T D R I V E N D E V E L O P M E N T - AT D D

Acceptance criteria are a description of what would be checked by a test.

Given a requirement such as “As a user, I want to check out a book from the library”, an acceptance criterion might be “Verify the book is marked as checked out."

An acceptance test for this requirement gives the details so that the test can be run with the same effect each time.

Test format[edit]Acceptance tests usually follow this form:[1]

Given (setup)A specified state of a systemWhen (trigger)An action or event occursThen (verification)The state of the system has changed or an output has been producedFor the example requirement, the steps could be listed as:Given:Book that has not been checked outUser who is registered on the systemWhen:User checks out a bookThen:Book is marked as checked out

14

Think to automatise these tests!

Agile, in extension Scrum, is about planning and not following blindly a plan

15

C O A C H | T R A I N E R

• Pierre E. Neis

• Senior Lean Agile Coach Product Development & Operational Excellence: Finance, Government, E-commerce, Global Structures, Offshore.

• Specialist in Organisational Development and Agile Deployment

• Scrum Coach & Trainer, Lean Kanban Coach

• References: SAP UK, AXA Global, Kingfisher Global, GDF Suez, atHome Group, Touring Assurances, Euroclear, ERDF, Capgemini, Cloudwatt, CNRS, LaPoste Innovation, rueducommerce.com , Invivo, LesFurets.com, BCG Digital Ventures,

• Offices: Luxembourg, Paris, London, Brussels, Geneva, Beirut, Heidelberg

• Mob. +49 (0)160 998 724 49

• pierre.neis@agilesqr.com

• @elpedromajor

16thanks !