SAFe

 Scaled Agile Framework serves the business imperative of making organizations more agile in responding to digital disruption. The DevOps and Release on Demand competency’s focus on enabling the business to release on demand plays a key role in ensuring greater enterprise agility. It is a critical enabler for the ability to release on demand, because it helps overcome traditional misalignments across the Value Stream.

In SAFe DevOps, we also have a tool called the SAFe DevOps Health Radar. The health radar was built to help Agile Release Trains (ARTs) assess their ability to deliver continuous value to their customers. The assessment allows the ART to drill down into the 16 sub-dimensions of the Continuous Delivery Pipeline and rate their proficiency in more than 50 specific skills. After identifying gaps using the health radar, ARTs upskill in the areas that improve value flow the most and conduct periodic follow-up assessments to manage their ongoing improvement. The DevOps Health Radar is a popular, free tool that helps ARTs manage the long term evolution of their Continuous Delivery Pipelines.

Value Stream Mapping

When implementing DevOps, the problem is that even after a good action plan is created, the team is not sure how to act on it or whether the right people are even working on it. Value Stream mapping is a multifaceted tool for identifying problems with the flow of value and building a better future map and action plan. This draws clarity to where the bottlenecks lie and where the improvements are most needed.

A CALMR approach to DevOps

Approaches to implementing DevOps are diverse, without a standard playbook or central manifesto. But successful DevOps organizations do tend to have certain capabilities in common. They help inform the principles on which SAFe DevOps is based. SAFe calls these principles a CALMR approach to DevOps.

Culture

Establish a culture of shared responsibility for development, deployment, and operations.

Automation

Automate the continuous delivery pipeline.

Lean flow

Keep batch sizes small, limit WIP, and provide extreme visibility.

Measurement

Measure the flow through the pipeline. Implement application telemetry.

Recovery

Architect and enable low risk releases. Establish fast recovery, fast reversion, and fast fix-forward.

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources and services.
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more