You’re probably a believer in the benefits of continuous delivery and DevOps (why else would you be at this meetup?). The rest of your organization... maybe not so much. Maybe you’re getting pushback on changes you believe will make your organization better. Maybe you’re not sure where or how to start to give yourself the best chance of making a change that will work.
I’ll give you some tactics to start your journey toward continuous delivery (or toward any meaningful change, for that matter). I’ll also show how you might apply those tactics to address a specific challenge: adding test automation to a large legacy codebase. The goal is that you walk away with more tools in your “change toolkit” and a little more enthusiasm for shaking things up for the better where you work.
7. (You may have heard of us.)
DC Software
Craftsman User
Group (DCSCUG)
DC Scrum User
Group
Alt .NET
DC
International
Institute of
Business Analysis
(IIBA)
User Experience
Professionals
Association
(UXPA DC)
Tech Talk DC
(Polyglots unite)
Agile Defense
Proponents Team
(ADAPT)
DC Continuous
Delivery
(DCCD)
Agile Leadership
Network
(ALN-DC)
django-district
DC Business
Intelligentsia
(DCBI)
DevOpsDC
8. I used to be this guy.
https://thatcleverchick.files.wordpress.com/2012/01/man_looking_at_stack_of_papers.jpeghttp://educationblog.serif.com/assets/images/2012/05/mark-ingram1.jpg
Coincidence?
9. Then I became this guy.
http://archive.computerhistory.org/resources/still-image/ibm/ibm_people/ibm.man_looking_at_stack_of_papers.102649709.lg.jpg
Coincidence?
10. Then I read this.
http://ecx.images-amazon.com/images/I/71sYKaNItcL.jpg
19. Find (or create) your champion.
http://screenrant.com/wp-content/uploads/Captain-America-3-Avengers-Characters-Roster.jpg
20. Who is a good champion?
http://media3.washingtonpost.com/wp-srv/photo/gallery/090122/GAL-09Jan22-1433/media/PHO-09Jan22-147287.jpg
http://i.huffpost.com/gen/1956193/images/o-JUDGE-GAVEL-facebook.jpg
http://www.corynikkel.com/wp-content/uploads/2013/05/Conductor-Influence.jpg
http://www.maluproperties.com/wp-content/uploads/2015/07/Budgeting-Money-300x235.jpg
29. Involve the head and heart.
http://lauriehaller.org/wp-content/uploads/2015/05/20150518-1.jpg
30. Build a coalition of the willing.
https://www.flickr.com/photos/fncll/145149313
31. Who has the most pain?
http://3.bp.blogspot.com/-XSS3IBgLdPo/UrEHIZSxfUI/AAAAAAAACK4/00SeIqiiSB4/s1600/009-garcia-vs-matthysse-img_8137.jpg
32. May not be many to start…
http://www.canadianbusiness.com/wp-content/uploads/2014/11/hand-up-standing-out-from-crowd-200330166-004-stone-getty-compressor.jpg
47. Do you have automated testing?
http://memegenerator.net/instance/61147726
48. The situation.
Let’s make one small update.
Change that one. What could
possibly go wrong?
https://c2.staticflickr.com/2/1044/1348380154_7f8644effe_b.jpg
63. And it’s backed up.
http://ecx.images-amazon.com/images/I/51Eb%2BdU3WRL._SY344_BO1,204,203,200_.jpg
64. Metric Before After
Time to produce a viable
build or Minimum Viable
Build (MVB)
48 hours <30 minutes
Defects exposed to
production
49/year 2/year
Time spent on
regression
20% of release time (15
days)
5% of release time (4
days)
System Test (API)
Coverage %
15% (estimated) 68%
Cycle time to run full test
suite
15-20 days 2.5 hours
Feature time % 15% 55%
If you want more justification…
65. And that’s backed up, too.
http://www.csgi.com/img/logo_csgi.png http://i.ytimg.com/vi/f4et0EGvKXA/maxresdefault.jpg