The document discusses the Agile Manifesto and the importance of embracing change in software development. It emphasizes valuing individuals, working software, customer collaboration, and responsiveness over processes and documentation. Additionally, it outlines frameworks for managing change and the necessity of adapting to evolving requirements.

1. If “embrace change” is hard
Lighting keynote
MVP Edition :-)
6 november 2013 - Milano XPUG
mail@fabio.mora.name
http://creativecommons.org/licenses/by-nc-sa/3.0/it/deed.it
@morafabio

2. Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
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.
Kent Beck
Mike Beedle
Arie van
Bennekum
Alistair Cockburn
Ward
Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas
2
© 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice.
http://agilemanifesto.org/iso/en/

3. The Management 1.0 way
3
@morafabio

4. The Management 1.0 way
$this-­‐>assertSame($person,
$resource);
$this-­‐>assertTrue($person-­‐>persuade());
$this-­‐>assertObjectHasMethod($person,
“motivate”);
FAILURES!
Tests:
1,
Assertions:
3,
Failures:
3
4
@morafabio

5. Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
http://agilemanifesto.org/iso/en/principles.html
Positive change
Software development is a learning process
5

6. Changing by learning
«The personality remains
elastic during the life»
B.F.Skinner
,
1975
http://en.wikipedia.org/wiki/Social_learning_theory
Social learning theory
Bandura,
1997
6
@morafabio

7. Change frameworks
Kotter
Heath
+ Lewin's Change Model, Burke-Litwin Change Model, 7S Framework & more...
7
@morafabio

8. Change frameworks
Common points
1 • Logical conviction
2 • Emotional drive
3 • Remove Obstacles
8
@morafabio

9. 1 • Logical conviction
• Retrospectives
Ask the right questions.
• Lead by example
You do, you rule.
• Find a clear direction
Urgency and critical moves.
9
@morafabio

10. 2 • Emotional drive
• Change is a requirement
As in Agile Manifesto principles.
• Do you like to code?
We’re developers! Motivation is inside.
• External advantages
More time, gratification, satisfaction, money...
10
@morafabio

11. 3 • Remove Obstacles
• Pair
With a domain expert.
• Automated Tests
Manage fear - TDD is as trojan horse.
• Get in a safe environment
Remove management frictions, better tools, benefits...
11
@morafabio

12. Definitely, can you change it?
Yes.
•
Plan, do, check, act/adjust
•
It’s kaizen stuff.
No.
• Take the long way
• Wait...
• Exit
• Exit (yes, you’re free to change)!
12
@morafabio

13. Thanks!
Questions?
13

14. Credits & Books
•
•
Kotter J., Harvard Business School Press 2012
Leading Change
•
Anolli / Legrenzi, Il Mulino 2009
Psicologia Generale
•
Kent Beck, Addison Wesley 1999
Extreme Programming Explained
•
14
Chip & Dan Heath, RH Business Book 2009
Switch
Jurgen Appelo, Addison Wesley 2010
Management 3.0 Leading Agile Developers
@morafabio

15. Surely you're getting back Milan, where
you have a job you do not like. But do
not be so depressed, life smiles you, and
if you do not like it change it!
15