18

Feature toggles are a common practice in high-velocity development because they de-couple development from release. Dev teams can "soft-release" a new feature to production, in a disabled state. This allows the feature to be released any time. If the feature is dependent on other work or preparation, it doesn't have to wait for a major release to go to ...


9

This is not docker-specific, but this general rule for evangelism applies: different audiences require different evidence. In general, software developers (and managers from a development background) want to see it in action, so POC's with measurable outcomes are preferred. Other disciplines and executive stakeholders may be OK with case studies and ...


8

In an ideal world I think you roll out a new build and surprise! NOTHING changes. This is because all of your new features are behind switches that go out with the switch off. Post-deployment you verify that your rolled-out service still works, the phones aren't ringing any more (unless ringing phones is your purpose, that is), etc. Once you are back to a ...


7

You have to understand that processes change people who follow them. As people learn, internalize and get better at a process, it changes the way they learn how to solve a particular problem. A set of similar processes reinforce each other into a mindset the person uses to solve a category of problems and eventually form a set of values that guides decisions ...


5

Hack your Team Bringing about change in your organisation is hard. People have habits, they resist change, and they are often comfortable with the status quo. To bring about change, in no particular order, here are a few tools you can use. Cause others to experience the problem that DevOps solves. Many times the benefits of DevOps is only understood on a ...


4

A successful high-velocity development environment typically relies on a pretty strict automated system involving quality verifications with detection and rejection of faulty changes causing regressions. Feature toggles offer the ability to commit even work-in-progress, untested changes without getting rejected for causing regressions in the integration ...


4

A couple of months ago I gave a presentation about the pros and cons about docker. My expectation was that the developers would start to use tool immediately after the presentation, but it took a couple of months. It turned out that a (huge) problem was required in order to get it accepted by the team members: There a six services at the moment that all ...


3

DevOps applies to Organization Type 2, the Business to Business entity as much if not more than the first Organization type. There are two possible scenarios here: Scenario 1 In the first they are selling a product or service to businesses. In terms of DevOps, this makes them virtually indistinguishable from Organization Type 1. Though their customer is a ...


3

In his book Creativity, Inc, Ed Catmull mentions a practice originating in movie business, when directors would receive feedback on their movie in progress, so called "Notes". At Pixar he was in charge of the company and that was his "movie" and in essence he envisioned a similar way to receive feedback on running the business. It was an event carefully ...


3

I see some interesting parallels in this story and The Phoenix Project. (Spoilers ahead for the book, if you haven't read it read this anyway :)) I take it the title for "Notes Day" comes from the term of art in Hollywood, where "notes" are constructive criticism about a work. In this story, Catmull plays the part of Parts Unlimited CEO Steve Masters. ...


2

Developers (and usually development managers) usually look for two outcomes associated with framework: ease of management, and speed of deployment. You want to ship code faster, and easier. Provide evidence that the approach works; try building a small POC using feature flags versus the old way. Case studies matter less to tactical people (developers\...


1

I feel dev ops is involved more than just the product developed, but the process that is used to go from an idea to in the field. Org 2, I think, could use dev ops to set up a uniform way to gather requirements, incorporate/enforce branching strategy, setup/maintain CI. This is just the dev team. Every organization isn't just dev. Org 2 could may very ...


Only top voted, non community-wiki answers of a minimum length are eligible