There are a lot of disappointment with Agile nowadays, as many agile initiatives fail - at least fail to deliver the brand new world of hyper-productivity that was envisioned. However, it does not suffice to make small changes and hope for large benefits. For an agile initiative to really pay off, several fields must be agile-minded: technology, process, and organisation. Shortcoming in any of these will cap the possible success. This presentation covers the three "elements" tech, process, and org, in an attempt to make an inventory of what practices we have in each field. And, of those practices - which of them are well-established, which are well-known and well described, and which are totally avant-garde? Hopefully each organisation can find something to pick to move their agile initiative a little bit further.

1. Failed Agile?
On agile tech, agile process,
and agile organisation
Dan Bergh Johnsson
@danbjson
dearjunior.blogspot.com
dan.bergh.johnsson@omegapoint.se

2. Manifesto for Agile Software Development
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.
@danbjson

3. http://www.halfarsedagilemanifesto.org
3

4. http://programming-motherfucker.com
4

5. Agenda
• Hip-hop
• Agile technology
• State of the Art
• Bang for the Buck
• Books
• Agile process
• Agile organisation
• … and a travel
5

6. Four Elements of Hip-Hop
6
http://www.flickr.com/photos/coupdoreille/11980711276/
http://www.flickr.com/photos/93163771@N08/11980682486/
http://www.flickr.com/photos/49180634@N05/10678483545
http://www.flickr.com/photos/54237011@N02/5032121885/

7. Three Elements of Agile
7
Organisation
Process
Technology
http://www.flickr.com/photos/82397118@N00/5173687358
http://www.flickr.com/photos/85546319@N04/9546047237
http://www.flickr.com/photos/85546319@N04/11874970786

8. Three Maslow-pyramids for Agile
8
Avant-garde
Well-known
Established
https://www.flickr.com/photos/s_w_ellis/3859525046/

9. The Manifest, again
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.
@danbjson

10. 10
Organisation
Process
Technology
We build
systems that
rock!

11. Technology
11
system quality testing
unit tests
daily release
context-based test
/ exploratory testing
build server
domain-based code (DDD)
automated
acceptance tests
platform as code
- vagrant, puppet TDD
versioned databases
feature toggle
two generation architecture
build pipeline

12. Bang for the Buck
Agile Testing
• Human testning á la Exploratory Testing in sprint
• A few automated acceptance tests
Controlled Technical Debt
• Quality reports e g Sonar
• Automated acceptance tests
• Daily release - eventually
A database in each mans pot
• Automated rigging of test data
• Automated rigging of structure - versioned DB
• (spice with) Vagrant/Puppet, or bash-script
12

13. Books
Implementing Domain
Driven Design
[Vernon]
Refactoring Databases
[Ambler/Sadalage]
97 Things Every
Programmer Should
Know [antologi]
Continuous Delivery
[Humble/Farley]
https://www.flickr.com/photos/shutterhacks/4474421855

14. 14
Teknik
Organisation
Process
We ensure things
get done without
waste or detours!

15. Process
15
non-functional requirements
forecast-based planning
test in team / test in sprint
sprint retrospective
MVP-release
domain modelling a la DDD
hypothesis-driven,
A/B-testning
project retrospective
effect-governed project
demo
kanban
sprint 1-2 w
Specification by Example

16. Bang for the Buck
16
lojalty relevanc
scale PV/UV (w) #eshares
rod GA Tw+FB
now/base 20 1000
ROI 25 1000
ambition 50 5000
1/3-release; MVP
project retrospective

17. Books
Succeeding with Agile
[Cohn]
Lean Software Development
[Poppendieck]
Domain Driven Design
[Evans]
Specification by Example
[Adzic]
Impact Mapping [Adzic]
Agile Estimation and
Planning [Cohn]
https://www.flickr.com/photos/shutterhacks/4474421855

18. 18
We create an organisation where
people work by inner drive, and
direct that drive toward a purpose!
Process
Technology
Organisation

19. Organisation
19
sociocracy Beyond Budgeting
portfolio management
self-organised team
destilled processes
and standards
”Ambition to Action”
multi-team
coordination
flexible work-hours
open salaries
lattice-organisations

20. Bang for the Buck
?
20

21. Frederick Winslow Taylor
@danbjson
(1856 - 1915)
([1904]1911 – still going
strong)

22. Drive á la Daniel Pink
Autonomy
Purpose Mastery
@danbjson

23. ἐκκλησία - responsible autonomi
@danbjson
http://www.flickr.com/photos/robwallace/6950767/

24. Process office of SVTi
@danbjson

25. SVTi: ecclesia + double loop learning
@danbjson

26. Bang for the Buck
Central targets
- Specific, measurable, possible to monitor
- Interpreted locally by each team
Management meeting agenda
- What can we do specifically right now to support
”autonomy, mastery, purpose”?
26

27. Books
LESS! Essays on Business
Transformations
[antologi]
Principles of Scientific
Management [Taylor]
The Human Side of
Enterprise [McGregor]
Drive [Pink]
Implementing Beyond
Budgeting [Bogsnes]
Radical Management
[Denning]

28. Take-away
Three elements in balance:
Technology, Process,
Organisation
Not making progress in one element
might depend on state of another element
@danbjson

29. </Failed Agile?>
Dan Bergh Johnsson
@danbjson
dearjunior.blogspot.com
dan.bergh.johnsson@omegapoint.se