19
HOW TO BUILD AN AGILE ORGANISATION BASIC PRINCIPLES 1

How to build an agile organisation

Embed Size (px)

Citation preview

Page 1: How to build an agile organisation

H O W T O B U I L D A N A G I L E O R G A N I S AT I O NB A S I C P R I N C I P L E S

1

Page 2: How to build an agile organisation

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 O R G . P R I N C I P L E S & G O V E R N A N C E M O D E L

S Y S T E M I C O R G A R C H I T E C T U R E : 3 L I N E S O F D E F E N C E

2

Page 3: How to build an agile organisation

3 N D L I N E

O F

D E F E N C E

2 N D L I N E

O F

D E F E N C E

1ST LINE

OF

DEFENCE

P U R P O S E O F A N E F F E C T I V E M A N A G E M E N T - P H A S E 1

3

TEAM

MANAGEMENT

QA, RISK, FINANCE,…

AUDIT

GOVERNANCE

L I N E S O F D E F E N C E A R E

P R O T E C T I N G T H E I N N E R

C I R C L E F R O M O U T S I D E .

T H E Y A R E N O T M I C R O -

M A N A G I N G T H E I N N E R

C I R C L E S .

E X A M P L E

Page 4: How to build an agile organisation

3 R D L I N E

O F

D E F E N C E

2 N D L I N E

O F

D E F E N C E

1ST LINE

OF

DEFENCE

A D A P T I N G T O H Y B R I S B I L L I N G O R G A N I S AT I O N

4

SCRUM TEAMS

WORKFLOW MANAGEMENT (PROJECT, PRODUCT), CUSTOMER, USERS

QA, RISK, FINANCE,…

AUDIT

CORPORATE GOVERNANCE

P R I N C I P L E

A G I L E M E A N S C L O S E

C O L L A B O R AT I O N B E T W E E N

C U S T O M E R A N D T E A M S . N O W

W H AT H A P P E N S I F T H E

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

3 R D L I N E ?

Page 5: How to build an agile organisation

S T R U C T U R E

C H I E F P R O D U C T O W N E R , S C R U M C O A C H , A G I L E P M O ,

S O L U T I O N A R C H I T E C T, T E S T L E A D , B U S I N E S S

( C U S T O M E R )

5

1 S T L I N E O F D E F E N C E

2 D L I N E O F D E F E N C E

3 R D L I N E O F D E F E N C E

W O R K S T R E A M L E A D E R S H I P T E A M :

- P R O D U C T L I N E M A N A G E R S

- P R O G R A M M A N A G E M E N T

- S U B J E C T M AT T E R E X P E RT S

- C O N T R O L L I N G

- E T C …

CUSTOMER

CUSTOMER

CUSTOMER

CUST

OMER

CUST

OMER

CUSTOMER CUSTOMERCUSTOMER

C P O

T E A M

P O

S M

T E A M

P O

S M

T E A M

P O S M

P O

S MT E A M

T E A M

P O

S M

T E A M

T E A M

T E A MP O

S M

P O S M

P O

S M

Yellow circle are the agile teams. They are self managed and free to synchronise themselves.

Scrum Masters (SM) and Product Owners (PO) are the only with the ability to pass the line of defence: SM as voice of the team, PO as voice of the customer. Other stakeholders can pass the line only on team´s special request.

In the transition phase or the learning stage, the customer is on the 2nd line. By gaining maturity, the customer can move to first line. In particular organisations like digital when high interactivity is requested, customer will be set in 2nd line.

Page 6: How to build an agile organisation

W H O ? W H AT ? W H E N ?

6

1 S T L I N E O F D E F E N C E

2 D L I N E O F D E F E N C E

3 R D L I N E O F D E F E N C E

CUSTOMER

CUSTOMER

CUSTOMER

CUST

OMER

CUST

OMER

CUSTOMER CUSTOMERCUSTOMER

C P O

T E A M

P O

S M

T E A M

P O

S M

T E A M

P O S M

P O

S MT E A M

T E A M

P O

S M

T E A M

T E A M

T E A MP O

S M

P O S M

P O

S M

L E V E L 1 ( TA C T I C A L ) : • M E E T S D A I LY AT T E A M L E V E L F O R S TAT U S

• B I - W E E K LY F O R D E M O & C H A N G E

• W O R K S O N S P R I N T B A C K L O G

L E V E L 2 ( S T R AT E G I C A L ) : • M E E T S W E E K LY AT T E A M L E V E L F O R S TAT U S

• B I - W E E K LY F O R D E M O & C H A N G E

• W O R K S O N P R O D U C T B A C K L O G

L E V E L 3 ( S T R AT E G I C A L ) : • M E E T S M O N T H LY AT P R O G R A M L E V E L F O R S TAT U S , B U D G E T & C H A N G E

• W O R K S O N P R O D U C T R O A D M A P

Page 7: How to build an agile organisation

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

M E E T I N G P R I N C I P L E S

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

7

Page 8: How to build an agile organisation

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

R O L E S & R E S P O N S I B I L I T Y M AT R I X

8

R E S P O N S I B L E O N LY S C R U M

R O L E S

A C C O U N TA B L E O N LY S C R U M

R O L E S

C O N S U LT E D O N LY O N -D E M A N D

I N F O R M E D O N LY B O A R D S , J I R A ,

W I K I

Page 9: How to build an agile organisation

M E A N I N G S

R E S P O N S I B L E : H AV I N G A N O B L I G AT I O N T O D O S O M E T H I N G , O R H AV I N G C O N T R O L O V E R O R C A R E F O R S O M E O N E , A S PA R T O F O N E ' S J O B O R R O L E .

"the cabinet minister responsible for Education" synonyms: in charge of, in control of, at the helm of, accountable for, liable for, charged with; In Scrum: responsible people are committed to do the job ex. Development Team is responsible to transform requirements in « potential shippable increments » in the expected quality.

A C C O U N TA B L E : R E Q U I R E D O R E X P E C T E D T O J U S T I F Y A C T I O N S O R D E C I S I O N S ; R E S P O N S I B L E .

"ministers are accountable to Parliament » In Scrum: accountable are the people

T O C O N S U LT

1 seek information or advice from (someone, especially an expert or professional)."if you consult a solicitor, making a will is a simple procedure"

2 synonyms: 3 ask, seek advice/information from, take counsel from, call on/upon/in, turn to, have recourse to; informalpick

someone's brains "if you consult a solicitor, making a will is a simple procedure" In Scrum: people having a particular knowledge to share with the team to increase their knowledge

I N F O R M E D

having or showing knowledge of a subject or situation. "an informed readership » In Scrum: everybody caring about the outcomes. As transparency is key, there should not be specific requests. If not, ask yourself and improve your communication.

9

Page 10: How to build an agile organisation

1 S T L I N E M E E T I N G S

10

1 S T L I N E 2 N D L I N E 3 R D L I N E

D A I LY S TA N D - U P S A

R E F I N E M E N T A C(On-Demand) C(On-Demand)

S P R I N T P L A N N I N G A C(On-Demand) C(On-Demand)

S P R I N T R E V I E W A A I

R E T R O S P E C T I V E A

A: ActiveC: ConsultedI: Informed

P R O G R E S S I S M A D E AVA I L A B L E

F O R A L L L I N E S O N B O T H J I R A &

W I K I

Page 11: How to build an agile organisation

1 S T L I N E S C R U M P R O C E S S

11

PRODUCT OWNER TRANSLATES VISION IN BACKLOG ITEMS

SPRINT PLANNING SESSION WITH DEV TEAM

DEV TEAM SPRINTS & MEETS DAILY

DEV TEAM, PO & STAKEHOLDERS MEETS TO REVIEW THE POTENTIALLY SHIPPABLE INCREMENT

REFINEMENT SESSION WITH DEV TEAM

C O M M U N I C AT I O N

DEV TEAM RETROSPECTS ON LESSONS LEARNED AND NEW IMPROVEMENTS

PRODUCT OWNER TRANSLATES IMPROVEMENT WITH DEV TEAM IN BACKLOG ITEMS

USER STORIES ARE ESTIMATED IN STORY POINTS

E S T I M AT I O N O R P L A N N I N G

P O K E R E I T H E R I N R E F I N E M E N T

O R I N S P R I N T P L A N N I N G

Page 12: How to build an agile organisation

2 N D L I N E M E E T I N G S

12

1 S T L I N E 2 N D L I N E 3 R D L I N E

S C R U M - O F -S C R U M S I A I

G R O O M I N G C(On-Demand) A I

R O A D M A P U P D AT E I A C(On-Demand)

A: ActiveC: ConsultedI: Informed

T E A M 8 O F 2 N D L I N E I S

C O M P O S E D B Y A L L T H E

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

Page 13: How to build an agile organisation

2 N D L I N E S C R U M P R O C E S S

13

VISION BUILT WITH CUSTOMER AND PRODUCT OWNER

CHIEF PRODUCT OWNER TRANSLATES VISION IN BACKLOG ITEMS

ROADMAP UPDATE SESSION WITH PO TEAM PO TEAM SPRINTS & MEETS

WEEKLY AT SCRUM-OF-SCRUMS

ROADMAP UPDATE ACCORDING SPRINT OUTCOMES

REFINEMENT SESSION WITH PO TEAM

C O M M U N I C AT I O N

PO TEAM RETROSPECTS ON LESSONS LEARNED AND NEW IMPROVEMENTS

Page 14: How to build an agile organisation

3 R D L I N E M E E T I N G S

14

1 S T L I N E 2 N D L I N E 3 R D L I N E

R E L E A S E M E E T I N G I C(On-Demand) A

P R O G R A M S T E E R C O I C(On-Demand) A

P O R T F O L I O M E E T I N G I I A

A: ActiveC: ConsultedI: Informed

C H I E F P R O D U C T O W N E R ( C P O ) I S AT T E N D I N G 3 R D

L E V E L O F M E E T I N G S

Page 15: How to build an agile organisation

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

G O V E R N A N C E & C O M M U N I C AT I O N M O D E L

15

Page 16: How to build an agile organisation

M E E T I N G S S C H E D U L E

16

DAILY MEETINGS • DAILY STAND UP

• Attendees: Scrum Team (Development Team, Scrum Master, Product Owner)

• Moderation: Scrum Master • Purpose: status meeting, highlight impediments • Duration: 15 minutes • When: each day, same time, same location

WEEKLY MEETINGS • REFINEMENT MEETINGS

• Attendees: Scrum Team (Development Team, Scrum Master, Product Owner), + all the necessary people to respond to team issues

• Moderation: Scrum Master • Purpose: feinement both Sprint and Product Backlog in

Development perspective, Planning Poker (effort estimation), collaborative solution focused meeting

• Duration: 45 minutes • When: once a week

• SCRUM-OF-SCRUMS • Attendees: Product Owners, Management &

Customers (passive) • Moderation: Chief Product Owner • Purpose: status meeting on development, identify and

respond on overlaps and hints • Duration: 45 minutes • When: once a week, same day, same place

• GROOMING MEETING • Attendees: Product Owners, Management &

Customers (active) • Moderation: Chief Product Owner

• Purpose: status meeting on development, identify and respond on overlaps and hints

• Duration: 45 minutes • When: once a week if necessary

• MEET THE ARCHITECT • Attendees: Scrum Team (Development Team, Scrum

Master, Product Owner if necessary) • Moderation: Scrum Master • Purpose: Architect meets the team regarding

improving architecture • Duration: 45 minutes • When: once a week if necessary

• MEET THE PROCESS OWNER • Attendees: Scrum Team (Development Team, Scrum

Master, Product Owner if necessary) • Moderation: Scrum Master • Purpose: Process Owner meets the team regarding

improving processes and/or mitigating impacts • Duration: 45 minutes • When: once a week if necessary

BI-WEEKLY MEETINGS • SPRINT REVIEW

• Attendees: Management & Customers (active), Scrum Team

• Moderation: Product Owner

• Purpose: show and tell of sprint outcomes, inspect/adapt from the stakeholders

• Duration: 45 minutes • When: at the end of the Sprint

• SPRINT RETROSPECTIVE • Attendees: Scrum Team • Moderation: Scrum Master • Purpose: inspect/adapt from the development process, • Duration: 45 minutes • When: after Sprint Review

• ROADMAP UPDATE • Attendees: Management, Customer, Users • Moderation: Product Owner • Purpose: Update the roadmap according to Sprint

outcomes • Duration: 45 minutes • When: after Sprint Review

MONTHLY MEETINGS • RELEASE MEETING

• Attendees: Management & Customers (active), PO Team

• Moderation: Chief Product Owner • Purpose: show and tell of sprint outcomes, inspect/

adapt from the stakeholders • Duration: 45 minutes • When: at the end of the Release

Page 17: How to build an agile organisation

17

ReleaseP R I O R I T I S E D

P R O D U C T B A C K L O G

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

ES

TIM

AT

ION

R E L E A S E P L A N R E L E A S E P L A N - U P D AT E

V 0 . 1 V 0 . 2 V 0 . 3 V X

TA C T I C A L O R G

S TAT E G I C A L O R G

Page 18: How to build an agile organisation

R E C O M M E N D AT I O N

• all teams have the same sprint length • starting the same day • ending the same day

18

Page 19: How to build an agile organisation

W W W. A G I L E S Q R . C O M

« there is only one way to be agile »

19