Infrastructure slowing delivery

To get a new environment you open a ticket and wait

For a new environment you open a ticket, and the infrastructure team has a full queue. Every server is configured by hand, because there was never time to write it as code. A cloud migration left half done adds a second way of doing things, and the time developers spend waiting never shows up in the reports.

Book a call

Does this sound familiar?

  • Developers open a ticket for every environment, database or permission, then wait for their turn.
  • Staging and production were configured by hand, each in its own way, and the differences only come to light when something breaks.
  • The disaster recovery plan exists on paper and has never been tried.
  • The move to the cloud has started, and so far it has added a second way of getting code into production.

How do you end up with infrastructure that slows developers down?

Developers see the queue of requests. Behind the queue are hand-built environments, which multiply when a migration stalls halfway. Waiting that nobody measures stays out of the priorities.

  1. Servers and environments configured by hand

    Each server was set up by someone, at different times and through steps that were never written down, so no environment can be recreated identically. For the same reason a disaster recovery plan stays on paper. An environment that isn’t written as code can’t be rebuilt after a failure, and nobody has been able to test it. With infrastructure as code, servers, networks and permissions become versioned code, and the difference between test and production can be read in a diff.

  2. Every request goes through the infrastructure team

    When only the people who run the infrastructure can create an environment or change a configuration, every team waits its turn and that team becomes the organisation’s bottleneck. Self-service tools and a ready-made path for creating, releasing and observing a service give teams their autonomy back.

  3. A migration left half done

    A move to the cloud or to Kubernetes that began without a step-by-step path leaves the old and the new running together, with two ways of releasing and much more to keep track of. It is best carried forward one piece at a time, asking whether you need Kubernetes at all or whether a managed service from your cloud does the same job with less maintenance.

  4. The hours lost waiting appear in no report

    Hours lost waiting for an environment or a permission are paid developer time that nobody adds up, so it never reaches the priorities. Following the path of a few recent changes shows where they stopped, and where it is best to begin.

What changes when infrastructure stops slowing you down

An environment is created from code, identical every time, and developers get it themselves without opening a ticket. Knowledge of the infrastructure lives in the repositories, where the whole team can read it, and recreating an environment after a failure is something you simply run again from code.

The infrastructure team, which used to handle the requests, spends its days improving the platform the teams use, and whoever is building something new in the product can spin up an environment to try it out.

What are you waiting for today?

The path of a recent request shows where it stopped. From there we decide whether to begin by bringing the infrastructure into code, with our DevOps, Continuous Delivery and Platform Engineering service, or by measuring the waiting first.

We use your data to respond to your request. Read our Privacy Policy.