Definition of Agile and the Schrödinger's dilemma - Do not open the box.
As soon as...
You define what 'Agile' is,
You show people what 'Agile' is in your company,
You list what you do to implement 'Agile'...
Everyone has an opinion
And most of the time, that opinion would be... "that's not real 'Agile'''.
Every time you try to go specific with Agile, you lose some of the options available, based on the Values of the Agile Manifesto.
So, what's best?
Stay in an undecided state of 'Agile' and keep a whole and rich 'Agile' concept, or make 'Agile' specific to your context and lose some of the flawlessness of the 'Agile' concept?
Outline/Structure of the Lightning Talk
Using the analogy with the Schrodinger's Cat experiment
Learning Outcome
-> Define 'Agile' make you lose the flawlessness of 'Agile'
-> How to overcome this tradeoff?
Target Audience
Agile Practitioners
Links
- Schrodinger's Cat experiment https://simple.wikipedia.org/wiki/Schr%C3%B6dinger%27s_cat
schedule Submitted 3 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
David Alia - The Dome: A powerful experiment for change when change is hard
45 Mins
Case Study
Intermediate
-
keyboard_arrow_down
David Alia - "I'll start my transformation next Monday" - Overcoming the fear of pain to successfully transform corporates' mass
30 Mins
Talk
Intermediate