8. Agile 8
I think it’s very important to have a feedback loop, where
you’re constantly thinking about what you’ve done and
how you could be doing it better. I think that’s the
single best piece of advice: constantly think about
how you could be doing things better and
questioning yourself.
Elon Musk
11. Agile
Two kinds of Mindset
11
Fixed Growing
“I am great in sports, but suck in math”
“I have a talent for skiing, but lack ball
feeling”
“If I try harder I will get better in maths”
“I need to work on my ball feeling”
“This is the way we do it
around here”
“What changes do we need to adapt
and to get better”
12. Agile
The Satir change model
12
Status quo
Foreign element
New Status quo
Transforming
Idea!
14. Agile 14
“Our comforting conviction that the world
makes sense rests on a secure foundation:
our almost unlimited ability to ignore our
ignorance.”
16. Agile 16
”The age of Complexity”
makes it hard to follow a plan…
… unforeseen events more likely to occur
… everything is interconnected
… the needs of the customers are “abstract”
19. Agile
Agile processes promote
sustainable development.
The sponsors, developers, and
users should be able
to maintain a constant pace
indefinitely.
Agile Principle no 7:
http://agilemanifesto.org/principles.html
28. Agile
Create a learning organisation
Concept Planning Develop Integrate Release
Learning
oppor-
tunity
C P I I I I I I I I I I I I I I I I
Agile – Driven by learning
Traditional – One opportunity
C P D I R C P D I R C P D I R
Traditional, project sequence – More opportunities
31. Agile
33
A software bug
is an error, flaw, failure, or fault in a computer
program or system that causes it to produce an
incorrect or unexpected result, or to behave in
unintended ways
32. Agile
34
CEO
VP Sales VP Marketing VP Accounting VP Operations VP IT
Pre-Sales
Churn
….
Strategy
Service
Campaigns
….
Controlling
Payment
…..
….
Service
Support
Stability
QA
….
SW
Development
Architecture
Security
Test
….
33. Agile
What behavior do we want from our organization?
... and what is impeding that behavior?
34. Agile
36
An organisational bug
is an error, flaw, failure, or fault in the system that
creates friction and impedes the flow of work
38. Agile
Organizational impediments
Lack of team spirit
“Dear HR manager, do you think we could sit down and discuss how we can
get the cross functional teams to work better? Right now the individual reward
system weakens the team spirit”
39. Agile
Organizational impediments
Slowed down by architecture
“Dear Chief Architect, do you think we could have a discussion about
collaboration? Right now we are not able to work fast enough”
40. Agile
Organizational impediments
Budgeting
“Dear CFO, do you think we could sit down and discuss budgeting? Right now
we seem to be committing too early which make it difficult for us to make
changes when we need to”
41. Agile
Organizational impediments
Friction between development and operations
“Dear Operations Manager, do you think we could sit down and discuss how
we can collaborate better and deploy more often to get faster feedback?”
42. Agile
Organizational impediments
Lack of common understanding
“Dear CEO, can we please provide Agile training to all stakeholders? Right now
we are not aligned with the same understanding of what we want”
43. Agile
Organizational impediments
Lack of automation
“Dear Test Manager, do you think we could sit down and discuss how we can
automate regression tests so that we safely can deploy more often?”
44. Agile
Organizational impediments
Project time pressure
“Dear Project Manager, do you think we could sit down and discuss how we
can get enough time available to nurture proper craftsmanship in order to avoid
technical debt?”
Kan ikke forstå at det skal være et mål å være “busy all the time”
Simple
Repeating patterns and consistent events
Clear cause-and-effect
Relationships evident to everyone;
Right answer exists
Fact-based management
Complicated
Expert diagnosis required
Cause-and-effect relationships discoverable but not immediately apparent to everyone
More than one right answer possible
Known unknowns
Fact-based management
Complex
Flux and unpredictability
No right answers
Emergent instructive patterns
Unknown unknowns
Many competing ideas
A need for creative and innovative approaches
Pattern-based leadership
Chaotic
High turbulence
No clear cause-and-effect relationships, so no point in looking for right answers
Unknowables
Many decisions to make and no time to think
High tension
Pattern-based leadership
Disorder
You will have disorder when you don´t understand where you are.
Hva skal til for at baby-apen ligger unna frukt som ikke er bra?
Software du have bugs. They are hiding and we need some kind of magnifier to find them
This is an organisation, represented by its organisational hierarchy. It do have bugs as well. These are hiding too!
What does it mean that the system behaves in unintended ways?
The idea is that the SM takes the identified impediment to the right person and tries to find better ways..
The idea is that the SM takes the identified impediment to the right person and tries to find better ways..