While I am best known as a Java evangelist, my day job prior to joining Oracle was Chief Agile Methodologist where I facilitated 3 company-wide Agile rollouts. If you are skeptical of folks trying to sell you certifications, frustrated with the institution of new processes and tracking systems, or wary of process experts taking the place of technical leadership, then this is the session for you. Come learn the insider secrets of how Agile works in a large enterprise from someone who has been in the eye of the hurricane. However, be warned that this knowledge will give you the power to change the development culture in your organization for better or worse -- are you ready to shoulder this responsibility?
33. And had to resolve internal conflict
33https://www.flickr.com/photos/skinnylawyer/6884960361/
34. Conquering the Universe with Agile turned out to be a lot of
work!
34https://www.flickr.com/photos/jurvetson/83176915/
35. So, I made my escape from the Empire
35https://www.flickr.com/photos/p_valdivieso/9006007735
36. And went back to being just a normal guy…
36https://www.flickr.com/photos/d35ign/11826583146
37. Some things I learned…
37https://www.flickr.com/photos/23950335@N07/6032572260/
38. The Agile Manifesto
Process and toolsIndividuals and interactions over
Following a planResponding to change over
Source: www.agilemanifesto.org
Comprehensive
documentation
Working software over
Contract negotiationCustomer collaboration over
39. The Agile Industry Manifesto
Continuous improvementExpert advice over
In-person collaborationTooling licenses over
CraftsmanshipMethodologies over
Clean codeMetrics over
https://www.flickr.com/photos/dieknochenblume/8454004839
40. The Agile Industry Manifesto
Continuous improvementExpert advice over
In-person collaborationTooling licenses over
CraftsmanshipMethodologies over
Clean codeMetrics over
https://www.flickr.com/photos/dieknochenblume/8454004839
41. ALL YOUR BASE ARE BELONG TO US.
41Source: http://setandbma.wordpress.com/2012/03/23/agile-history/
43. But they are not a substitute for experience
43https://www.flickr.com/photos/nasamarshall/12815430035
44. How do you know things have gone wrong?
• According to Chapter 5, Section 3, Verse 13 of the Agile Bible…
• Expert XXX has a hyper performing team with 3 hour Sprints, so we need to
do that!
• Same issue comes up in the retrospective… for 3 weeks running!
44
45. Confession Time…
• I have trouble disagreeing with Ron… maybe
it is the gray beard.
• The guy who forced all your Sprint lengths to
line up – yeah, that was me implementing
what Dean recommended.
• I hate retrospectives! – I would much rather
be coding.
45https://www.flickr.com/photos/38463026@N04/3925480958
46. The Agile Industry Manifesto
Continuous improvementExpert advice over
In-person collaborationTooling licenses over
Clean codeMetrics over
https://www.flickr.com/photos/dieknochenblume/8454004839
CraftsmanshipMethodologies over
47. There is a methodology for that…
Geek Hero Comic – Salvatore Iovene – "Agile Development Explained"
http://www.geekherocomic.com/2009/02/21/agile-development-explained/
52. What really makes projects fail?
• Build server… yeah, that is Jonny's machine
• We have unit tests… they are just manually run. And manually verified.
• Software quality? Oh, that is what those guys over there do.
52
53. Confession Time…
• I occasionally check in binaries, but that is
better than not having them at all.
• I trained teams on Scrum… when I should
have been training them on JUnit.
• All my Agile talks have been on… guess
what, methodologies! (or anti-
methodologies)
53https://www.flickr.com/photos/lon/5582656222
54. The Agile Industry Manifesto
Continuous improvementExpert advice over
In-person collaborationTooling licenses over
CraftsmanshipMethodologies over
https://www.flickr.com/photos/dieknochenblume/8454004839
Clean codeMetrics over
55. You Think You Are Independent
55
https://www.flickr.com/photos/sylvainkalache/14976661122
56. But you are NOT!
56
https://www.flickr.com/photos/nzdave/491411546
57. We are WATCHING YOU
57
Source: Deviant Art, created by SavageSauron
http://savagesauron.deviantart.com/art/The-Great-Eye-326927311
58. You are a metric junkie when…
• You log in to the Agile tool during vacation to make sure you have a pretty
burn-down chart
• To keep up with the other hyper performing teams, you inflate your
estimates by a factor of 10… then 100… then 1000!
• Your QA team won't accept the build when the code coverage drops below
98%
58
59. Confession Time…
• Some weeks I spent more time in
Excel then my IDE.
• 100% code coverage? I have
accomplished that with 0
assertions!
• I have single-handedly killed
projects with pie charts.
59https://www.flickr.com/photos/hoyvinmayvin/4865553148/
60. The Agile Industry Manifesto
Continuous improvementExpert advice over
CraftsmanshipMethodologies over
Clean codeMetrics over
https://www.flickr.com/photos/dieknochenblume/8454004839
In-person collaborationTooling licenses over
64. You have overdone the tooling when…
• When the QA guy wants you to fix the coffee machine you ask him to file a
bug first
• The only person who writes stories in your planning meeting is the Scrum
Master as he enters them in the online tool
• You go into shock when you meet your team for the first time and realize
you are the only guy… Pat, Alex, Kris, and even Sam are all females!
64
65. Confession Time…
• I was one of those Scrum masters
who entered in all the stories for my
team.
• Oh, and I also put all the estimates in
for efficiency.
• And I even built my own tooling and
unleashed it on unwitting teams!
65https://www.flickr.com/photos/blackzack00/15206347052/
66. And the most important thing!
• Stick with what you are good at…
66
Hacking
Video
Beer
68. Safe Harbor Statement
The preceding is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
68