Ever wondered why some teams and organisations don’t feel they can make Agile work for them? – Why do we often see teams implementing Agile, but without really getting the results they had hoped for? Should we change our expectations of the process, or is there something else we can do? Will fine-tuning the process and highlighting internal ownership even work, and how can we do that? These are just some of the questions that we will answer together in this session, targeted at new practitioners – we will cover a lot of real life scenarios and cases from the teams I’ve been working with and experiments I have been a part of.

1. Agile ME 2017 - Rasmus Runberg
Pimp
my
Agile
Rasmus Runberg

2. Agile ME 2017 - Rasmus Runberg
Sponsors & partners
Sponsors & partners Bronze sponsor
Supporter
Media partners

3. Agile ME 2017 - Rasmus Runberg
People
Rasmus Runberg
• Product Owner
• Working agile for more than 6 years
• Background as classic Project Manager
Fellow
• UAE based community of people being
passionate about agile software
development

4. Agile ME 2017 - Rasmus Runberg
Why the title?
“Pimp my Ride” where a MTV TV-
show from 2004 to 2007, where
people’s old rusty cars where
“pimped” into cool rides.

5. Agile ME 2017 - Rasmus Runberg
What’s the goal?
Empowered employees
• Happy engaged employees
• Better solutions and better
quality
• United teams
• Etc.
Ability to evolve and adapt
• MVPs and frequent deliveries engages
the client and creates transparency
• Feedback to the team(s) creates
understanding and purpose
• Ability to change with an ever changing
world
• Etc.

6. Agile ME 2017 - Rasmus Runberg
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
+ Twelve principles
The Manifesto

7. Agile ME 2017 - Rasmus Runberg
Scrum

8. Agile ME 2017 - Rasmus Runberg
Kanban

9. Agile ME 2017 - Rasmus Runberg
LeSS

10. Agile ME 2017 - Rasmus Runberg
SAFe

11. Agile ME 2017 - Rasmus Runberg
The Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
+ Twelve principles
Individuals and interactions over processes and tools
Responding to change over following a plan

12. Agile ME 2017 - Rasmus Runberg
Modern agile
Safety is both a basic human need and a key to unlocking high
performance. We protect people’s time, information, reputation, money,
health and relationships
You can’t make people awesome or
safe if you aren’t learning. We learn
rapidly by experimenting frequently.
We make our experiments “safe to
fail” so we are not afraid to conduct
more experiments.
This includes the people who use, make, buy, sell or fund our products
or services.
Anything that isn’t delivered isn’t
helping anyone become more
awesome or safe. In modern agile
we ask ourselves, “How could
valuable work be delivered
faster?”

13. So, what
is the
“Agile Process”

14. Agile ME 2017 - Rasmus Runberg
So, what is the “Agile Process”
Is being agile only about our Product
Development?
If no, how do we apply the Agile
Product development to our process?

15. Agile ME 2017 - Rasmus Runberg
So, what is the “Agile Process”

16. Agile ME 2017 - Rasmus Runberg
So, what is the “Agile Process”
What would be your Minimal
Viable Process?
Focus on deliveriesWorking software
Collaboration
Open to changes

17. Agile ME 2017 - Rasmus Runberg
Be agile about your process
Key Stones in
Agile Software Development
• Deliver running software
• Learn fast
• Interaction and collaboration
• Welcome changes
Create your
Minimal Viable Process:
• Focus on delivering value
• Make learning and experimenting
part of your daily routines
• Facilitate team communication
• Use the feedback!

18. Agile ME 2017 - Rasmus Runberg
… And then you can add
to the process
Be explicit about your additions
Run it as experiments
Get feedback!
Learn and adapt
If the additions or change doesn’t
create value, stop doing it!

19. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools

20. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
How long should your sprint be?
Should length of the sprint be the
same every sprint?

21. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
SCRUM or KANBAN – Or
SCRUMBAN?
When can KANBAN be a better option
than SCRUM?
Do I need to strictly follow one
or the other every time?

22. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
How should I facilitate reviews?
The usual “board meeting”?
What brings value to your
stakeholders?
Who are your stakeholders?

23. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
When do you do your refinement /
Grooming?
Who’s in charge of this work?
How well should a user story be
groomed?

24. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
Are the purpose of the Retrospective
the same every time?
Should the agenda then be the same?
Are Retrospectives always at the end
of the sprint?

25. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
At planning do you take one item at
the time from the top of the backlog?
Who do the actual planning?

26. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
Who creates your user stories?
- The PO?
- The Developers?
- The Client?
How many items do you have in your
backlog?

27. Agile ME 2017 - Rasmus Runberg
Experiment examples
Sprint length
SCRUM vs. KANBAN
Review
Backlog refinement /
User story grooming
Retrospectives
Planning
Backlog management
Process Tools
What backlog tool do you use?
Jira? - Trello?
- And why?

28. Agile ME 2017 - Rasmus Runberg
Be careful, it’s
my experience
Keep
your DS
Involve
the team
Not everyone
loves changes
N
Please
don’t

29. Just ask me!
And Fellow Academy