Bob Davis of Plutora on DevOps and Value Stream Mapping

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Bob Davis of Plutora about DevOps, Value Stream Mapping, making bottlenecks visible, and using metrics effectively.

Key Takeaways

• DevOps came into many organisations in a very fragmented way
• Value stream mapping the end-to-end DevOps process makes bottlenecks visible
• Value stream management exposes data from across the whole toolchain, irrespective of the toolset
• Tools can communicate status without needing to interrupt work
• Effective metrics expose gaps and bottlenecks in the process which can then be addressed and improved

#development #devops

What is GEEK

Buddha Community

Value Stream Mapping the DevOps Void

In this article, learn about value stream mapping and also see some of the benefits.

Ever wonder why your releases take so long?

After all, your company just invested a “zillion” dollars on a whole bunch of great ‘agile’ tools and a cloud framework. Tools that allow you to automatically provision your infrastructure, applications, data, and ensure that all your security obligations are met.

Hey! With this new” DevOps toolchain”, we should be moving our releases, from request to delivery, in a matter of minutes. You know … full push-button automation! … environments on demand! … And all that stuff!

Yeah! Right! But no! That’s not how it typically plays out.

In fact, a more realistic example might follow a storyline as follows:

• Project manager raises a request for a Test Environment
• Request sits in its service management queue for a few days
• Gets approved and assigned by Test Environment Manager and distributed to engineering teams
• Sits in the team ITSM queues for another few days
• Apps team build the package in 5 minutes but can’t deploy as infra not ready
• Infra team provisions
• Test team can’t start testing as data not ready
• Data team ensures Data secure and Compliant
• Data team provisions
• …
• Sorry, testing now too busy with another test cycle
• Test teams spot a defect with the build
• Higher priority project comes along and acquires environment
• Go back to go

#devops #value stream mapping #devops void

How to Extend your DevOps Strategy For Success in the Cloud?

DevOps and Cloud computing are joined at the hip, now that fact is well appreciated by the organizations that engaged in SaaS cloud and developed applications in the Cloud. During the COVID crisis period, most of the organizations have started using cloud computing services and implementing a cloud-first strategy to establish their remote operations. Similarly, the extended DevOps strategy will make the development process more agile with automated test cases.

According to the survey in EMEA, IT decision-makers have observed a 129%* improvement in the overall software development process when performing DevOps on the Cloud. This success result was just 81% when practicing only DevOps and 67%* when leveraging Cloud without DevOps. Not only that, but the practice has also made the software predictability better, improve the customer experience as well as speed up software delivery 2.6* times faster.

3 Core Principle to fit DevOps Strategy

If you consider implementing DevOps in concert with the Cloud, then the

below core principle will guide you to utilize the strategy.

• It is indispensable to follow a continuous process, including all stages from Dev to deploy with the help of auto-provisioning resources of the target platform.
• The team always keeps an eye on major and minor application changes that can typically appear within a few hours of development to operation. However, the support of unlimited resource provisioning is needed at the stage of deployment.
• Cloud or hybrid configuration can associate this process, but you must confirm that configuration should support multiple cloud brands like Microsoft, AWS, Google, any public and private cloud models.

Guide to Remold Business with DevOps and Cloud

Companies are now re-inventing themselves to become better at sensing the next big thing their customers need and finding ways with the Cloud based DevOps to get ahead of the competition.

#devops #devops-principles #azure-devops #devops-transformation #good-company #devops-tools #devops-top-story #devops-infrastructure

Java: How to Get Keys and Values from a Map

Introduction

Key-value stores are essential and often used, especially in operations that require fast and frequent lookups. They allow an object - the key - to be mapped to another object, the value. This way, the values can easily be retrieved, by looking up the key.

In Java, the most popular Map implementation is the HashMap class. Aside from key-value mapping, it’s used in code that requires frequest insertions, updates and lookups. The insert and lookup time is a constant O(1).

In this tutorial, we’ll go over how to get the Keys and Values of a map in Java.

#java #java: how to get keys and values from a map #keys #map #values #how to get keys and values from a map

DevOps Basics: What You Should Know

Once an industry term becomes popular, particularly in technology, it can be difficult to get an accurate definition. Everyone assumes that the basics are common knowledge and moves on. However, if your company has been discussing DevOps, or if you are interested in learning more about it, here are some basics you should know.

What Is DevOps?

DevOps refers to the restructuring of the traditional software application cycle to support Agile development and continuous improvement/continuous delivery. Traditionally, the software was created in large-scale, monolithic bundles. New features and new releases were created in large packages and released in full-scale, infrequent, major deployments.

This structure is no longer effective in the modern business environment. Companies are under increasing pressure to be agile. They must respond rapidly to changes in the business environment to remain competitive. Software development needs to be completely changed as a process so that incremental improvements can be made frequently – ideally, several times per day.

However, changing a development lifecycle completely requires major changes – in people and culture, process, and enabling tooling – to be effective. DevOps was created by the breaking down of cycles between development and operations, combining two separate functions in application development. These changes intend to support agile, secure, continuous improvements, and frequent releases.

#devops #devops adoption #devops benefits #q& #a #devops goals #devops migration #devops questions

Measuring DevOps Metrics: A How-To Guide

DevOps is supposed to help streamline the process of taking code changes and getting them to production for users to enjoy. But what exactly does it mean for the process to be “streamlined”? One way to answer this is to start measuring metrics.

Why metrics are important to track

Metrics give us a way to make sure our quality stays the same over time because we have numbers and key identifiers to compare against. Without any metrics being measured, you don’t have a way to measure improvements or regressions. You just have to react to them as they come up.

When you know the indicators that show what condition your system is in, it lets you catch issues faster than if you don’t have a steady-state to compare to. This also helps when you get ready for system upgrades. You’ll be able to give more accurate estimates of the number of resources your systems use.

After you’ve recorded some key metrics for a while, you’ll start noticing places you could improve your application or ways you can reallocate resources to where they are needed more. Knowing the normal operating state of your system’s pipeline is crucial and it takes time to set up a monitoring tool.

The main thing is that you decide to watch some metrics to get an idea of what’s going on when you start the deploy process. In the beginning, it might seem hard to figure out what the best metrics for a pipeline are.

Figuring out which metrics are important to you

You can conduct chaos engineering experiments to test different conditions and learn more about which metrics are the most important to your system. You can look at things like, time from build to deploy, number of bugs that get caught in different phases of the pipeline, and build size.

Thinking about what you should measure can be one of the harder parts of the effectiveness of the metrics you choose. When you’re considering metrics, look at what the most important results of your pipeline are.

Do you need your app to get through the process as quickly as possible, regardless of errors? Can you figure out why that sporadic issue keeps stopping the deploy process? What’s blocking you from getting your changes to production with confidence?

That’s how you’re going to find those key metrics quickly. Running experiments and looking at common deploy problems will show you what’s important early on. This is one of the ways you can make sure that your metrics are relevant.

#devops #devops-principles #devops-tools #devops-challenges #devops-adoption-challenges #devops-adoption #continuous-deployment #continuous-integration