The document outlines principles for building agile organizations, highlighting the importance of collaboration between customers and teams. It describes a three-line defense framework for management, emphasizing self-managed agile teams and the roles of scrum masters and product owners. Additionally, it presents a meeting schedule with defined purposes for daily, weekly, bi-weekly, and monthly meetings to ensure effective communication and governance.

1. 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 N
B A S I C P R I N C I P L E S
1

2. 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

3. 3ND LIN E
OF
DEFEN CE
2 ND L INE
O F
DEFENCE
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
LINES OF DEFENCE ARE
PROTEC TING THE INNER
CIRCLE FROM OUTSIDE.
THEY AR E NOT MICRO-
MANAGING T HE INNER
CIRCLES.
E X A M P L E

4. 3RD LINE
OF
DEFEN CE
2 ND L INE
OF
DEFENCE
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 ?

5. S T R U C T U R E
CHIEF PRODUCT O WNER, S CRUM COACH, AGI LE PMO ,
SOLUTION AR CHIT E CT, T EST LE AD, BUSINESS
( CUST OME R)
5
1ST LINE OF DEFENCE
2D LINE OF DEFENCE
3RD LINE OF DEFENCE
WORKSTREAM LEADE RS HIP TE AM:
- PRODUCT LI NE M AN AG E RS
- PROGRAM M AN AG E ME NT
- SUBJECT MATTE R E X PE RTS
- CONTROLLING
- ETC…
CUSTOMER
CUSTOMER
CUSTOMER
CUSTOMER
CUSTOMER
CUSTOMER CUSTOMER
CUSTOMER
C PO
TEAM
PO
SM
TEAM
PO
SM
TEAM
PO SM
PO
SM
TEAM
TEAM
PO
SM
TEAM
TEAM
TEAM
PO
SM
PO SM
PO
SM
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.

6. W H O ? W H AT ? W H E N ?
6
1ST LINE OF DEFENCE
2D LINE OF DEFENCE
3RD LINE OF DEFENCE
CUSTOMER
CUSTOMER
CUSTOMER
CUSTOMER
CUSTOMER
CUSTOMER CUSTOMER
CUSTOMER
C PO
TEAM
PO
SM
TEAM
PO
SM
TEAM
PO SM
PO
SM
TEAM
TEAM
PO
SM
TEAM
TEAM
TEAM
PO
SM
PO SM
PO
SM
LEVEL 1 (TACTICAL):
• MEETS DAILY AT T EAM LE VE L FOR S TATUS
• BI-WEEKLY FOR DEMO & CHANGE
• WORKS ON SPRI NT BACK LOG
LEVEL 2 (STRATEG ICAL):
• MEETS WEEKLY AT T E AM LE VE L FOR STATUS
• BI-WEEKLY FOR DEMO & CHANGE
• WORKS ON PRO DUCT BACK LOG
LEVEL 3 (STRATEG ICAL):
• MEETS MONTHLY AT PROG RAM LE VE L FOR STATUS, BUDGET & CHANGE
• WORKS ON PRO DUCT ROADM AP

7. 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

8. 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

9. 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

10. 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: Active
C: Consulted
I: 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

11. 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
COMMUNICATI ON
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
EST IMATION OR PLANNING
P OKER EITHER IN REFINEMENT
OR IN SPRINT PLANNING

12. 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: Active
C: Consulted
I: 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

13. 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
COMMUNICATI ON
PO TEAM RETROSPECTS ON
LESSONS LEARNED AND
NEW IMPROVEMENTS

14. 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: Active
C: Consulted
I: 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

15. 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

16. 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

17. 17
Release
PRIO RITISED
PRODUCT BA CKLOG
ESTIMATION
ESTIMATION
ESTIMATION
ESTIMATION
ESTIMATION
ESTIMATION
ESTIMATION
ESTIMATION
ESTIMATION
ESTIMATION
RELEASEP LAN RE LE A SE PL A N - UP DATE
V0.1 V 0.2 V 0.3 VX
TA C T I C A L O R G
S TAT E G I C A L O R G

18. 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

19. W W W. A G I L E S Q R . C O M
« there is only one way to be agile »
19