This document discusses applying an agile mindset beyond software development. It covers key concepts like customer orientation, responsive planning and execution, and learning quickly through experiments. The document advocates forming cross-functional teams organized around customer journeys. Planning methods like Scrum, Kanban, and SAFe are presented as ways to support responsive adaptation. Continuous learning is emphasized through running many small experiments instead of a few large projects. Applying these agile principles in different workplaces through experiments is proposed.

1. AgileSparks
Agile Mindset/Approach – Beyond
Software/Technology
Yuval Yeret
Head of AgileSparks USA
yuval@agilesparks.com
857-218-9585
1 |

2. AgileSparks
2 |
Agile Mindset/Approach
1. Overview of Agile Mindset applied at the Company level / Beyond
Software – Why companies are adopting this framework
2. Customer/Value Orientation
3. Responsive/Adaptive Planning/Execution
4. Learning/Adapting Quickly
5. Applying Agile Mindset in YOUR Workplace
6. Q&A

3. AgileSparks
Why Agile ? ? ?
https://www.growingagile.co.za/2013/12/the-stacey-matrix-revisited/

4. AgileSparks
We need approaches that embrace uncertainty/complexity
http://www.derailleurconsulting.com/blog/complexity-and-noise-in-systems-development-projects

5. AgileSparks
We expect
uncertainty and manage
for it through iterations,
anticipation, and
adaptation.
Taken from http://en.wikipedia.org/wiki/PM_Declaration_of_Interdependence

6. AgileSparks 6
Supporting Values
Transparency
Inspection
Adaptation
Empericism

7. AgileSparks
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value :
While there is value in the terms on the right
We value the items on the left more
(http://www.agilemanifesto.org)
Process and
tools
Individuals and
interactions
over
Comprehensive
documentation
Working software over
Following
a plan
Responding to
change
over
Contract
negotiation
Customer
collaboration
over
OVER doesn’t mean INSTEAD OF!!!

8. AgileSparks
min
Does the Agile Manifesto apply
outside software ?
What needs to change?
Agile Manifesto Beyond Software
10

9. AgileSparks

10. AgileSparks 10

11. AgileSparks
The connection to Motivation
http://www.thersa.org/events/rsaanimate/animate/rsa-animate-drive

12. AgileSparks
Familiar?
http://www.youtube.com/watch?v=FGfplQ1FUFs

13. AgileSparks
13 |
v Why Agile
v Key concepts/values/principles in Lean/Agile beyond Software
Doing/Being Agile at the Company Level -
Summary

14. AgileSparks
14 |
Customer/Value Orientation

15. AgileSparks
Marketing
Sales
Product
Prof
Services
Agile
Teams
Customer/Value Oriented Teams
• Aim for customer-oriented teams:
– A specific customer journey (e.g. per
Product/Service)
– A key business challenge/
opportunity/objective
• Autonomous
• Stable

16. AgileSparks http://bit.ly/rugbyvideoforagile

17. AgileSparks 17

18. AgileSparks
min
• You play in one or several Teams
• Starting point equals endpoint
• No passing of the ball to your direct neighbor
• The ball must have air-time
• Everyone in the room participates
• One minute per iteration
• One minute for continuous improvement & new estimate
• You play five iterations
Exercise – Scrum Ball Point Game
20
Credit Boris Gloger
https://borisgloger.com

19. AgileSparks
19 |
v The Agile Team
v Cross-functional / Autonomous Teams
Customer/Value Orientation - Summary

20. AgileSparks
20 |
Responsive/Adaptive planning/execution
methods

21. AgileSparks 21

22. AgileSparks

23. AgileSparks
Product owner
- Where are we going & why?
- Priorities
Scrum overview – structure
PO
SM
Users
Stakeholders
Helpdesk
Operations
Management
Product
Backlog
Sprint
Backlog
... etc ...
Team
Direct communication
Scrum Master
- Process leader/coach
- Impediment remover
Cross functional, self
organizing Team
- How much to pull in
- How to build it
- How to test it

24. AgileSparks 24

25. AgileSparks
min
• Who would be on the ”Dev Team” – Doing the actual
work?
• Can you identify a “Product Owner” in charge of
maximizing value delivered by the team?
Exercise – Who would you want on
your Scrum Team?
10

26. AgileSparks
Transparent, Done Increments, Enabling Empericism
Definition of Done
• …..
• ….
• ….

27. AgileSparks
min
• What is the deliverable that can help you achieve
transparency, inspect and adapt?
• What is the “Definition of Done” that can ensure the
increment is indeed transparent?
Exercise – What is your “Done
Increment”
10

28. AgileSparks
Personal Timeboxes - Pomodoro
28

29. AgileSparks
2017-08-29
orem ipsum dolor sit amet, nse ctetur adi pis cing
elit nisl
2017-09-01
orem ipsum dolor sit amet, co nse ctetur adi pis
cing elit nisl
Scope Create Publish/Deploy Learn/
Tweak
Next
Definition of Done:
• Published and running/used
• Tracking metrics
Ongoing Done
Definition of Done:
• Deliverables ready
• Reviewed if required
• Ready to measure impact
Ongoing DoneOngoing Done
Definition of Done:
• Goal and metrics are clear
• Acceptance Criteria are clear
• Split to small stories
2 3 3 2
Feature / story
= completed
= blocked
= who is doing this right now
2017-08-20 2017-09-30
(description)
• Panic
(should be swarmed and kept moving.
Interrupt other work and break WIP limits as
necessary)
• Priority
• Hard deadline
(only if deadline is at risk)
• Oldest
2017-09-02
orem ipsum dolor sit amet, co nse
2017-08-27
orem ipsum dolor sit amet, adi pis cing elit nisl
2017-08-20
orem olor sit amet, co nse ctetur adi pis cing elit nisl2017-08-30
orem ipsum dolor sit amet, co adi pis cing elit nisl
2017-09-08
2017-08-25
orem ipsum dolor sit ctetur adi pis cing elit nisl
Task / defect
Hard deadline
(if applicable)
Date when added to board
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
(description)
(description)
(description)
Why
(description)
Who is analyzing / testing right now
= priority
= panic
What to pull first
xxxx kjd dj d xxx
Kanban kick-start example
Yuval Yeret
version 0.1
2017-04-28
(description)
orem ipsum dolor sit amet, co nse ctetur
=task =defect
http://www.agilesparks.com/kanban-marketing-kickstart/
Adapted from Henrik Kniberg Crisp.se

30. AgileSparks
min
• Who would be on the ”Dev Team” – Doing the actual
work?
• Can you identify a “Product Owner” in charge of
maximizing value delivered by the team?
How might a Kanban board look like
for your area of work?
10

31. AgileSparks 31
Daily Scrum / Standup

32. AgileSparks
Personal Kanban
32

33. AgileSparks
What if a team isn’t enough?

34. AgileSparks
34 |

35. AgileSparks
Portfolio SAFe aligns strategy and execution

36. AgileSparks
36 |
Learning/adapting fast
via tight feedback loops

37. AgileSparks
37 |
Adapt

38. Many Small Experiments
Over
Few Large Bets
38

39. AgileSparks
39 |
High tempo testing

40. AgileSparks
min
• Choose a task you’re about to do in the next month
that has a lot of uncertainty around “Do we know WHAT
is really required?”
• Phrase the task as an experiment validating an
hypothesis – “We believe that if we do X we will see
effect Y”
From tasks to experiments
10
40

41. AgileSparks
41 |
Applying Agile Mindset In YOUR Workplace

42. AgileSparks
min
42 |
1. Suggest experiments inspired by the workshop –
Principles/Practices changes
What are YOUR Agile Experiments?

43. AgileSparks
https://www.surveymonkey.com/r/
agilesparksfeedback

44. AgileSparks
Questions?
Yuval Yeret
SPCT | CTO | Agile Marketing Practice Lead | Enterprise
Lean/Agile Coach
yuval@agilesparks.com
+1-857-218-9585
https://www.surveymonkey.com/r/
agilesparksfeedback