This is the first session to share knowledge on Agile ways of working to 10 inclusive colleaegues in PMO Company by Getjan Lammers

1. The PMO Company B.V.
Birkstraat 95-10, 3768HD Soest - The Netherlands - +31 30 85 000 85 - info@thepmocompany.com
1
Introduction Workshop
Agile & Scrum for PMOC

2. Service Operation
Unit 3 : Service Operation Processes ─ Part 1
r3.0.0
Module 2 Introduction to Agile
2
Introduction Workshop The PMO Company for Agile &
Scrum certification

3. Basic Planning
3
Date Subject
2 Oct Introduction
2 Oct Domain 1 Value Driven Delivery
2 Oct Domain 2 Stakeholder Engagement
9 Oct Domain 3 Boosting Team Performance
9 Oct Domain 4 Adaptive planning
16 Oct Domain 5 Problem Detection and Resolution
16 Oct Domain 6 Continuous Improvement
16 Oct Retrospective and sprint planning

4. Structure of the sessions
➢Learning backlog
➢Sprints of 30 minutes:
❑ 20 minutes explanation,
❑ 10 minutes interaction.
➢Every person puts the top three suggestions on a
“Learning Flip Over Backlog”
4

5. What will you go for?
Sleutel
Pizza
Model
PMP
ACP
IPMA
BCD
IPMA C
Agile
Prince2
SCM
PSM
etc
Scrum
SAFe
suite
XP

6. Shu-ha-ri
➢SHU (守) "protect", "obey" — traditional wisdom —
learning fundamentals, techniques, heuristics,
proverbs
➢HA (破) "detach", "digress" — breaking with
tradition — detachment from the illusions of self
➢RI (離) "leave", "separate" — transcendence — there
are no techniques or proverbs, all moves are
natural, becoming one with spirit alone without
clinging to forms; transcending the physical
6

7. Shu-ha-ri
➢SHU (守) Agile Individual learning
➢HA (破) Communities of Practice
➢RI (離) Team collaboration/ ceremonies
7

8. Can we agree on the following?
➢No mobile phones or computers during the training,
unless…
➢Anyone that have to leave earlier?
➢We have a joint responsibility for the results of the
session;
➢If I am going too fast, please interrupt;
➢If you require a break, please interrupt;
➢We will end around 16:00; scrum scale webinar till17:00
➢Start at 13:30
8

9. Agile or traditional
• What would you do ?
9

10. 12 Agile principles: PMI-ACP
o Highest priority is satisfy customer through
early and continuous development of working
product,
o Welcome change, agile harnesses change
for customer's competitive advantage
o Deliver frequently from weeks - month with
preference weeks
o Business people and developers must work
together daily throughout the project
o Build projects around motivated individuals:
give support + environment they need and
trust them,
o Most efficient + effective method of
communication to a team is face2face
o Working software primary measure of
progress,
o Agile process promote sustainable
development,
o Continuous attention to technical excellence
& good design enhances agility.
o Simplicity is essential = art of maximizing the
amount of work not done
o The best architecture requirements and
design emerge from self-organising teams
o At regular intervals team reflects on how to
become more effective then tunes and
adjusts.

11. Basic Planning
11
Date Subject
2 Oct Introduction
2 Oct Domain 1 Value Driven Delivery
2 Oct Domain 2 Stakeholder Engagement
9 Oct Domain 3 Boosting Team Performance
9 Oct Domain 4 Adaptive planning
16 Oct Domain 5 Problem Detection and Resolution
16 Oct Domain 6 Continuous Improvement
16 Oct Retrospective and sprint planning

12. Service Operation
Unit 3 : Service Operation Processes ─ Part 1
r3.0.0
Module 2 Introduction to Agile
12
Domain 1 Value Driven Delivery

13. Agile concepts (Agile Manifesto)
Values:
1. Individuals and interaction over processes and tools
2. Working software over comprehensive
documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.
13

14. Tools and Techniques
• ROI, NPV, IRR
• Agile earned value
management (EVM)
• Product Roadmap
• Value stream Mapping
• Wip Limits
• Relative prioritization /
ranking
• Risk-adjusted backlog
• Cumulative flow diagrams
• Task/kanban boards
• Chartering
• Customer-value
prioritization
• Risk burn down graph
14

15. Knowledge and skills
• Prototypes, simulation,
demonstration
• Incremental delivery
• Prioritization
• Project and quality
standards
• Agile manifesto
• Agile contracting
• Agile accounting
• System thinking
• Variations in agile
methods
15

16. Wat is Agile according to YOU?
Afhankelijk van de situatie en de samenstelling van het team ingrijpen of
motiveren om er zelf uit te komen
Agile is ook in waterval kunnen werken wanneer dat noodzakelijk is
Als iets tijdskritisch is dan kunnen we beter een beproefde methode
gebruiken
Als je een sprint opstart, lever je op wat is afgesproken
Als waardestroom manager bevestig je het resultaat van de door het team
uitgevoerde prioritering
16

17. What is Value-Driven delivery
➢To generate Business value
➢Maximizing Value delivery
➢Minimize Risk
➢Consider also:
❑Technical dependencies
❑Cost of ownership
❑Non functional requirements
➢As soon as possible
❑Risk mitigation;
❑Stakeholder satisfaction.
17

18. Prioritization / Ranking and Incorporate change
➢Late-breaking change cannot bend the laws of scope
and space
18
A
C
B
D
E
F
Δ
Cutoff €/•
A
C
B
D
E
F
Cutoff €/•
Δ

19. Risk Management process
➢Risk management is part of Agile and not a separate process.
➢Risk can be threats to the project but could also be opportunities
for the project.
➢Risk-adjusted Backlog is to get a better discussion with the
business
➢A Guess x Guess = still a Guess!
19

20. Risk adjusted Backlog
20
Risk 1
(€ 9.000x 50%=) € 4.500
Expected Monetary Value
Risk 2
(€ 8.000x 50%=) € 4.000
Risk 3
(€ 3.000x 50%=) € 1.500
Risk 4
(€ 6.000x 25%=) € 1.500
Risk 5
(€ 2.500x 25%=) € 625
Risk 6
(€ 500x 25%=) € 125
Risk 7
(€ 500x 20%=) € 100
Percentage that we require
the mitigation action
Determinewhich
riskscan
proactively
tackled
Req 1 (€ 5.000)
Req 2 (€ 4.000)
Req 3 (€ 3.000)
Req 4 (€ 2.000)
Req 5 (€ 1.000)
Req 6 (€ 500)
Req 7 (€ 100)
ROI
Req 1 (€ 5.000)
Req 2 (€ 4.000)
Req 3 (€ 3.000)
Req 4 (€ 2.000)
Req 5 (€ 1.000)
Req 7 (€ 100)
Risk 2 action (€ 4.000)
Risk 4 action (€ 1.500)
Risk 5 action (€ 625)
Req 6 (€ 500)
Risk 7 action (€ 100)
Risk 2 action (€ 4.000)
Risk 4 action (€ 1.500)
Risk 5 action (€ 625)
Risk 7 action (€ 100)

21. Service Operation
Unit 3 : Service Operation Processes ─ Part 1
r3.0.0
Module 2 Introduction to Agile
21
Domain 2 Stakeholder engagement

22. Tools and Techniques
• Wireframes
• Servant Leadership
• User stories/backlog
• Conflict resolution
• Agile modeling
• Negotiation
• Information Radiators
• Distributed teams
• Story maps
• Personas
• Burn Down/up Charts
• Velocity
22

23. Knowledge and skills
• Incorporating stakeholder
values
• Communications
management
• Leadership tools and
techniques
• Stakeholder management
• Participatory decision
models
• Active listening
• Facilitation methods
• Globalization, culture &
team diversity
• Vendor management
23

24. Do we understand each other!
24

25. Wireframe ?
25

26. Personas
Provide an archetypal description of users
Be grounded in reality
Be goel-oriented, specific, and relevant
Be tangible and actionable
Generate focus
Not replacements for requirements, should argument them
26

27. Personas
27
http://asinthecity.com/2011/05/13/explaining-personas-used-in-ux-design-%E2%80%93-part-2/

28. necessity
28
➢ The backbone of the application is the list of essential
activities the application supports
➢ The walking skeleton is the software we build that supports
the least number of necessary tasks across the full span of
user experience
time
Story mapping
The backbone
The moving skeleton

29. 29
Iteration and release planning
➢ Choose coherent groups of features that consider the span of business
functionality and user activities
➢ Support all necessary activities with the first release
➢ Improve activity support and add additional activities with
subsequent releases
time
optionality
necessary
less
optional
more
optional
first release
second release
third release

30. User stories/Backlogs
As a <Role>,
I want <Functionality>,
so that <Business Benefits>.
Advantage :
• Who is asking for this?
• Why are we doing this?
Acceptance criteria
30

31. User Stories
I-idependent
N-Negotiable
V-Valuable
E-Estimatable
S-Small
T-Testable
31

32. That’s it folks …………….for the 1st session
What did we learn
What did you like
What can i improve next time
32