Putting the „dev‟ back to DevOps
2.4.2014
ANTTI VIRTANEN
+358 44 507 0050
antti.virtanen@solita.fi
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 perspec...
Two modes of DevOps
DevOps, startup mode
Emphasis on development
Fast iteration, continuous delivery
No production, no users
Usually DevOps ==...
DevOps, Facebook mode
Complex production problems
Huge amount of users
HA requirements.
Constant attacks (DOS, security ho...
Whom do you serve?
DevOps is a service for users.
Use UX knowledge for user modeling
Define your user groups. Stereotypes. Personas.
What doe...
Example dev “persona”
• 28 years old.
• 8 years programming.
• Master‟s degree from
univ.
• Likes board games
• Dogecoin f...
Backlog priorization
Developers want a new CI server
Production lacks proper audit log
Backup server‟s disk is almost full...
Ok, now what
In developers we trust
Developers are an important group of users
There is no DevOps without software
There is no software...
DevOps as an agile project
Is your DevOps serving all user groups?
Do you know it? Or is it your personal opinion? Feedbac...
Dev and Ops
as seen in XKCD
Summary
DevOps is an agile project
Resources are always too few.
The goal is ever moving.
There are many conflicting needs...
QUESTIONS?
Thank you..
Upcoming SlideShare
Loading in …5
×

Putting the 'dev' back to Devops, Tampere meetup 02-04-2014

734 views

Published on

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.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
734
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • How many of you are developers?How many of you are operators?
  • Stereotypes, the real world is usually in-between the two extremes
  • How many know what “persona” means in UX ?
  • Remember that “product owner” decides the priorities. Who decides your priorities? Do you know the criteria?Do other people know the criteria?
  • If you have identified “users”, by all means, do make a demonstration and get feedback from them!
  • I’m intentionally provocative in the last point.
  • Putting the 'dev' back to Devops, Tampere meetup 02-04-2014

    1. 1. Putting the „dev‟ back to DevOps 2.4.2014 ANTTI VIRTANEN +358 44 507 0050 antti.virtanen@solita.fi
    2. 2. Agenda Two DevOps flavours Startup mode Facebook mode Whom do you serve? Getting DevOps to right track Start doing DevOps
    3. 3. 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.
    4. 4. Two modes of DevOps
    5. 5. 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
    6. 6. 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?
    7. 7. Whom do you serve?
    8. 8. 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?
    9. 9. 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/5 Humility: 1/5
    10. 10. 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.
    11. 11. Ok, now what
    12. 12. 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?
    13. 13. 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.
    14. 14. Dev and Ops as seen in XKCD
    15. 15. 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.
    16. 16. QUESTIONS? Thank you..

    ×