DevOps and SAFe

DevOps and SAFe

“Nothing gets sacrificed if you’re willing to invest in DevOps and SAFe”

Agile practices improve cycle times from concept to development/test, but many organizations still suffer from slow deployments and infrequent releases, lowering customer satisfaction and delaying feedback and response. Old IT placed Development, QA, Support, Infrastructure management, Security and Production Operations into separate silos that can’t collaborate effectively and frustrate alignment on accountability for customer outcomes. To deliver value effectively, Development and Production Operations must perform like one aligned Agile team.

Let us compare two of the most leading enterprise delivery practices:

  • SAFe (Scaled Agile Framework) allows you to apply the same Agile structure as you use with software development teams to an enterprise by scaling Agile on a larger basis for the enterprise level.
  • If you have many Agile teams, SAFe gives a single view of the entire process, in that it provides a structure around them by which the teams can coordinate with each other. Ultimately, by using SAFe, the organization becomes more nimble.
  • SAFe requires program and portfolio levels of management to be a part of the process. These layers of management must be aligned with the goals and processes across the enterprise in order to achieve optimal results.
  • DevOps isn’t a framework really; instead, it is a change of culture that focuses on empowering the frontline workers. The DevOps solution establishes cross-functional teams made up of all stakeholders and encourages communication throughout the cycle.
  • Using DevOps, the way to shorten development and release cycles is through automation, in particular in testing. The deployment pipeline stays full due to automating the testing of smaller pieces.
  • DevOps requires management to enable the workers to learn from failures and experimentation. The framework brings together a looser set of principles and, therefore, is integrated depending on the organization’s needs.

While SAFe promotes continuous integration, continuous deployment and release on demand. Bringing Lean thinking and automation together with advanced technologies, practices and tools. DevOps accelerates business results, it creates alignment and collaboration between Development and Operations to optimize quality and value delivery.

SAFe DevOps principles are built around CALMR

C – Culture: Where culture is a shared responsibility across the organization from development to operations to security – everybody who’s building anything needs to be part of this.

A – Automation: Automation is very important – making sure you automate the entire delivery pipeline, dynamically spinning and tearing down development environments that emulate production, test automation, and deployment automation.

L – Lean flow: General push for smaller batch sizes of software delivery, limit WIP, provide real-time visibility of software. Increase predictability, accelerate feedback, reduce rework, increase release frequency and lower costs.

M – Measurement: Measure flow through delivery improvement. For example, use Kanban to map out the entire delivery pipeline, measure cycle time, lead-time, and use telemetry for all applications and servers.

And finally, R – Recovery: Enable real-time monitoring, enable faster recovery. Redundancy, and scalability.

Which verifies that you can’t do just Agile or just DevOps. You must merge the concepts together so lean-flow becomes an important part of the delivery approach. Ultimately, you want those two things to go hand in hand to maximise the outcome for your organisation. By doing that you’re taking out the manual work that is typically cumbersome and error-prone and treating everything as code.

Leave a Reply

Your email address will not be published. Required fields are marked *