putting the 'dev' back to devops, tampere meetup 02-04-2014
DESCRIPTION
Your "DevOps" might benefit from applying knowledge ja practices from agile and lean software development. You should know your users, prioritize your backlog and make demonstrations and get feedback. To do this, you probably need to ally with the developers if your DevOps is run by traditional administrators.TRANSCRIPT
Agenda
› Two DevOps flavours› Startup mode› Facebook mode
› Whom do you serve?› Getting DevOps to right track› Start doing DevOps
Who?
• Programmer, 16/30 years professionally
• Linux side-kick, semi-pro• Jack of all trades• *** hat hacker
My perspective is a developer’s point of view in this presentation.
Two modes of DevOps
DevOps, startup mode
› Emphasis on development› Fast iteration, continuous delivery› No production, no users
› Usually DevOps == 1-2 developers › Foremost programmers› Basic Linux admin skills› Possibly zero experience on production environments
DevOps, Facebook mode
› Complex production problems› Huge amount of users› HA requirements. › Constant attacks (DOS, security holes)› Big software system, complex deployment› Distributed system, cascading failure a possibility
› Development no longer straightforward› Canary testing (A/B testing)› Complex test automation. Security, HA, performance.› Big code base. Single Jenkins not web scale.
› Programmers no longer running DevOps?
Whom do you serve?
DevOps is a service for users.
› Use UX knowledge for user modeling› Define your user groups. Stereotypes. Personas.› What does a “Java developer” want from you?› What is the best way to serve different groups?
› Priorization between various needs› Who decides? Who is your PO (Product Owner)? › Where is your backlog? Is it visible?› Where’s the best value for users?
Example dev “persona”
• 28 years old. • 8 years programming.• Master’s degree from
univ.• Likes board games
• Dogecoin farming cluster in the carage. No car.
• Own Linux honeybot for fun (and profit?).
• No professional admin experience. (root rm –Rf has not happened yet)
• Hates waterfall development.
• Wants root access to production. Not happy if not allowed.
• Out of the box thinker. Hacker and tinkerer.
• Has the “proper” sense of humor and URL’s. Linux skills: 4/5
Programming: 4/5Humility: 1/5
Backlog priorization
› Developers want a new CI server› Production lacks proper audit log› Backup server’s disk is almost full› Must evaluate Graylog and Splunk› …› What is the most valuable thing to do?
› Use lessons from the software projects.
Ok, now what
In developers we trust
› Developers are an important group of users› There is no DevOps without software › There is no software without developers
› Developers are valuable allies› They are master programmers. You are not.› They know customer needs. Better than you.› They know things about Linux and DevOps. › They do agile development. Lean. Kanban. Do you?
DevOps as an agile project
› Is your DevOps serving all user groups?› Do you know it? Or is it your personal opinion? Feedback!
› Are you running iterations? Scrum? Kanban?› Is there a demo every two weeks for your users about new
things?
› Communicate! › This is the core competence of project managers and architects.
› Ask consults, managers, architects for more information on software project practices.
Dev and Opsas seen in XKCD
Summary
› DevOps is an agile project› Resources are always too few.› The goal is ever moving.› There are many conflicting needs and user groups.
› Software people know how to handle this. › Use UX personas. Lean. Kanban. Other good ideas.
› Developers are the key user group.› When treated properly they are a powerful ally.
QUESTIONS?Thank you..