DevOps and anarchism

DevOps and anarchism

Browsing over my timeline, I got triggered to the following statement:

 

For our first hypothesis, we discovered that teams that can decide which tools they use do better at continuous delivery. This is in contrast to teams that can use only those tools that are mandated by a central group. Teams that can choose their own tools are able to make these choices based on how they work, and the tasks they need to perform. No one knows better than practitioners what they need to be effective, so it's not surprising that practitioner tool choice helps to drive better outcomes.

 

This comes out of the State of DevOps report 2017. And this to me raises a lot of questions, because I do believe in empowerment of teams. But as a fan of the philosopher Levinas, I would like to state that there is an end to my freedom, and that is usually the beginning of  the freedom for the other starts.

So here are a couple of questions I have:

  • What is doing better at continuous delivery?
  • And I thought the goal of the movement is to deliver business value, so do the teams that can decide their own tools deliver more business value?
  • Have we excluded other factors like market dynamics etc, in this conclusion?

 

Because based on this statement we could state that a writer, a poet like Goethe who accepts the fact that he is bound to certain rules is less successful than the dada poet Van Doesburg, who empowered himself not to follow rules. Of course, you could argue success, but I think more people know Goethe than people know Van Doesburg.

 

So my assumption is that this statement needs more detailed investigation, before I would break all the rules and give freedom to all.

 

What are your thoughts on this one?

Anne, thanks for sharing! Pleasure meeting, you look for connecting with you! Keen to hear about your next post.🚀 Speak to you soon, Jhaanvi ADFAR Tech 😊

Like
Reply

To view or add a comment, sign in

More articles by Anne Plancius

  • DevOps: Learn from others

    Interesting to read in my feed on Devops currently a discussion about DevOps and Root Cause Analysis. And I see people…

  • DevOps, a different perspective

    In my search towards knowledge about DevOps I came across an interesting article with a for me completely different…

  • DevOps and Automation

    The nice part of this time off season is that you will get time to read and research. You can take a step back and try…

  • What is a DevOps culture?

    Last week I spent time in a DevOps fundamentals class leading towards the DevOps Fundamentals exam of DASA and in the…

    1 Comment
  • DevOps and Hammer

    In a constant search towards knowledge I came across this video of Dean Leffingwell on value streams. During the video…

    1 Comment
  • The impact of DevOps

    Last week I was in a session where EMA presented this report: https://www.enterprisemanagement.

  • To document or not to document

    Interesting to read finally Dr. Royce his original article, “Managing the development of large software systems”.

  • DevOps a definition please?

    A new year has started, and last year we saw a lot predictions on the trends in IT. And in those predictions DevOps was…

  • DevOps or OpsDev

    In the last weeks I see a lot of posts about the label that we have placed upon the change in IT, called DevOps. And a…

    2 Comments
  • Rules and creativity

    In preparation for this event I read the following book team of teams and I have to speak there about agile leadership…

Others also viewed

Explore content categories