software development

What Exactly Does a DevOps Architect Do?

According to Wikipedia, "an Architect is a person who plans, designs, and reviews the construction of buildings."

Times have changed. Now we have a DevOps Architect. No, don’t think of it as a replacement. In fact, we need both. We are talking about the web world. We are trying to make you understand the roles and responsibility of a DevOps Architect with this post.

Original Link

DevOps in 2019 (Part 5)

Given how fast technology is changing, we thought it would be interesting to ask IT executives to share their predictions about the future of DevOps in 2019. Here’s more of what they told us:

Ari Weil, Global VP Product and Industry Marketing, Akamai

Original Link

DevOps Trends 2019 — What You Need to Know

DevOps has evolved big time since many of us thought it was just a buzzword. Now we know that is a myth. DevOps has become a main focus and has been shaping the world of software for the last few years. Experts say that DevOps is going to be the mainstream and its popularity is going to reach its peak in 2019.

Below is the Google trend shown for the term “DevOps” and a hypothesis of its projected growth in 2019.

Original Link

DevOps in 2019 (Part 4)

Given the speed with which technology is changing, we thought it would be interesting to ask IT professionals to share their thoughts on their predictions for 2019. Here’s more of what they are thinking about DevOps:

Stefano Bellasio, CEO, Cloud Academy

Original Link

DevOps in 2019 (Part 3)

Given how fast technology is changing, we thought it would be interesting to ask IT executives to share their predictions about the future of DevOps in 2019. Here’s more of what they told us:

Bill Peterson, VP, Industry Solutions, MapR

Original Link

Supercharge Your Strategic Functionalities by Integrating Quality Engineering With DevOps

DevOps is being embraced by most if not all of the IT sector for a transparent workflow. DevOps’s main principality is that it allows for a continuous flow between software development and deployment which enables the user to receive software updates at ease. It also provides for a transparent and visual understanding of the entire software lifecycle.  

The focal point is to engineer quality into software coding and development and generate revenue in such a way that the ROI is a linear upward curve, year-on-year. Hence, companies are slowly shifting from quality assurance to quality engineering. According to 2018-2019 World Quality Report, 30% of organizations rate time to market the most important part of their corporate strategy. Implementing quality engineering involves a decrease in the time-to-market statistic, a shift left approach to the testing cycle, lesser defect rate and minimum observation of bugs in the production environment.

Original Link

A Crash Course on Serverless With AWS – Building APIs With Lambda and Aurora Serverless

Ever since AWS made a serverless option of AWS RDS Aurora generally available, I’ve been on the edge of my seat, eagerly anticipating all the various possibilities. It would mean a breakthrough in building serverless architectures. No more managing connection pools with SQL. No more worrying about capping out available connections. This would make it viable to use serverless for database intensive operations.

I wrote an article a while back explaining how to build a serverless API with MongoDB. But, I saw a pattern emerge. Higher throughput in a system, even though a database instance could take the load, would cause connections to drop because of a limited set of available connections.

Original Link

DevOps in 2019 (Part 2)

Given the speed with which technology is evolving, we asked IT professionals to share their thoughts about how the agile methodology would evolve in 2019. 

Here’s what they told us about agile and DevOps:

Original Link

Raspberry Jam Gets Thin in the Pool

Gerald Weinberg’s classic book The Secrets of Consulting continues to provide me with the nuggets of wisdom needed to sustain a long career. I reread the book every few years to remind me of the sometimes counterintuitive recommendations made within. But each time I’ve ignored Weinberg’s advice, it’s been at my own peril.

The more experience I gain (in other words, the older I get), the more I recognize that much of the advice is universal, not just relegated to consultants. Somewhere along the way, I realized that the crux of consulting is helping people solve their problems, not solving problems for them — they’ll never let that happen. This has allowed me to expand the applicability of Weinberg’s wisdom to many other arenas, such as my now 30-year marriage.

Original Link

The Anti-Transformation Transformation of Agile and DevOps

Organizational transformations have been part of organizational life for many years. There are reorganizations, big IT transformations and nowadays Agile, Cloud, digital, or DevOps transformations. These transformations used to follow a familiar pattern: an organization is going through a major transformation and invests significant amounts of money over a 3-5 year horizon into the transformation. At the end of the transformation when the "end-state" was achieved, the level of investment got reduced and focus shifted to stabilization and cost reduction. Over time the requirements changed more than the current level of investment allowed us to adapt for. Technical debt and the gap between needs and system functionality increased until this reached a level that required significant reinvestment or a new transformation to the next trend.

The cycle repeated every few years. While far from ideal, it seemed to work okay, it was good business for technology companies and consultancies, it provided a level of comfort for organizations as they executed their 3-5 year roadmaps of transformation. The duration was not really a problem as the environment changed slowly enough for organizations to catch-up with each cycle. The level of change in the environment has increased and competitors are increasingly coming from digital startups that move very quickly. This means that the traditional transformation cycle is too slow to react. We cannot afford 3-5 year cycles any longer and rather need to create an organizational capability to continuously adapt to the environment. If you do one more transformation in your organization it needs to be the anti-transformation transformation. The idea of this transformation is to transform not with a specific technical capability in mind but rather to transform to an ever improving, a learning organization and to build the organizational capability that allows you to drive this ongoing process in a sustainable pace and process.

Original Link

Top 5 Things Development Writers Need to Leave in 2018: A Rant

Now that 2018 is finally (finally) drawing to a close, the Editorial team at DZone is looking ahead to the new year in anticipation of the fresh, new content that we will receive from our community of software developers. The excitement is palpable.

But, first, we need to address something with you. You might want to have a seat. No, you’re not in trouble; we’re your friends, and we’re here to help you. 

Original Link

Convincing Your Team to Adopt TDD

Test-driven development is a simpler concept than agile itself: all you need to know, technically, is its red-green-refactor cycle — write a test, watch it fail, get it to pass, clean up the design.

And yet, many developers struggle to adopt TDD. The common reasons people give are that TDD is awkward and unnatural, and some people think it is ineffective. But I don’t believe TDD is ineffective, and neither do many other “test-infected” TDD practitioners. As far as being unnatural, I’ve seen plenty of developers immediately embrace the rhythm of TDD.

Original Link

Should Architects Write Code? You Bet They Should!

There’s a common misconception that’s permeated our profession: Architects don’t need to write code to do their jobs.

Now, this may seem like a harmless approach. After all, writing code is what developers do. And architects should be busy with more important tasks.

Original Link

How to Create GitOps Pipelines With GitHub Actions and Weave Cloud

GitHub Actions will become a major player in the CI SaaS market. It can easily replace most CI tools out there especially if you ship code as container images. With GitHub Actions, you can do more than CI/CD. Most tasks performed today with bots (code sign validations, issue management, notifications, etc) can be made into workflows and run solely by GitHub.

Why would you give up your current CI SaaS and self-hosted bots for GitHub Actions? For one, GitHub Actions simplifies automation tasks by offering a serverless platform that is capable of handling most development tasks. As a developer, you don’t want to jump from one SaaS to another in order to diagnose a build error. The fewer environments you have to use on a regular basis, the more productive you’ll be. Not to mention that as a developer you probably spend most of your time on GitHub anyway.

Original Link

10 Questions to Ask a Potential Software Development Partner

Nobody embarks on a software development project with the goal of failing. Unfortunately, failure is a real possibility if you don’t find the right development partner. The key is getting the right information to help you make the choice that’s genuinely right for your project. So how do you do that?

Simple. You need to ask the right questions, and make sure you get good answers. After all, even if you’ve heard amazing things about a company, you need to ensure they’re a fit for YOU.

Original Link

What Is DevOps, Exactly?

Everything changes. Everything inevitably evolves. In the IT environment, this maxim is even truer, as the emergence of new technologies and methodologies transform processes much faster than in other areas. This requires an immense capacity for adaptation from Information Technology professionals. It was this demand that gave rise to the term DevOps, which brings together the two main IT activities: development and operations. And now we’ll help you understand why the concept has been spreading so fast by companies in the industry.

DevOps is the English term originated from the collision between "development" ("Development") and "operations" (Operations). The concept arose from the union of two IT tendencies: the first is the agile infrastructure, or agile methodology, which consists of an agile and lean approach of the operations of an IT company.

Original Link

What Is Continuous Integration?

It’s hard to find terms getting more attention in the software world in the last few years than the closely related practices of Continuous Integration (CI) and Continuous Delivery or Continuous Deployment (CD), often referred to in tandem as CI/CD. Organizations across the world, from one-person development shops to multinational corporations, are implementing CI and CD for their software products.

In this article, we will describe CI, briefly mention CD, and see how you can use them effectively. We will evaluate some of the popular tools and systems available in the space that allow you to get up and running quickly with your development workflow.

Original Link

How Does Your DevOps Measurement of Success Stack Up?

CloudBees teamed up with IDG to conduct a DevOps measurement survey to investigate how well organizations think they are doing with their DevOps journey. We spoke to 100 respondents consisting of IT executives, IT operations, engineering and shared services who are all involved with DevOps adoption in their organizations. These organizations represent a cross-section of small, medium and large businesses. The majority of our survey takers work in the technology, manufacturing, and financial services vertical industries throughout North America.

Our initial findings include:

Original Link

Why and How to Use Git LFS

Although Git is well known as a version control system, the use of Git LFS (Large File Storage) is often unknown to Git users. In this post I will try to explain why and when Git LFS should be used and how to use it. The source code of this post can be found on GitHub.

What Is It?

Git LFS is an open-source project and is an extension to Git. The goal is to work more efficiently with large files and binary files into your repository.

Original Link

Ad-Hoc YAML DSLs and Productivity

One of my frustrations with the DevOps and cloud infrastructure tools is that most of them are badly designed DSLs that eschew all features of modern programming languages. Things like modules, data structures, functions, imperative control flow constructs, debuggers, linters, standard versioning/deployment practices, and rich library ecosystems are all missing. Of course, it is hard to do any real work without these features so the folks using these tools at some point come to the same conclusion and re-invent non-standard analogs to get by. The re-invention usually ends up being some kind of templating system built with a real language. Two obvious examples I can think of are Ansible with its Jinja templating and Terraform with its own ad-hoc variable interpolation mechanism that I presume is built on top of Go’s templating features. Oh and I almost forgot Kubernetes and Helm.

The arguments the tool designers bring up for why they made yet another DSL are usually some variation of "YAML or FooBarLang is declarative and so it reduces complexity". On the surface, this seems to make sense because declarative solutions, in theory, reduce complexity by hiding more details but when you start actually trying to solve problems the shortcomings become obvious. When real-world use cases are brought up along with the shortcomings of the tool to address them the response ends up being some variation of "You’re using the tool wrong". Again, this kinda makes sense until you dig deeper and realize that it’s not really an answer. Tools must always be subordinate to human intentions. If a tool can not accomplish a goal or requires extraordinary workarounds then it’s not the user’s fault and the logical conclusion is that the tool is badly designed. If I want to write a loop and can’t for some reason then that’s a lack of foresight on the tool designer’s part and not my problem. There could be several valid reasons I’d want to use a loop (or recursion) but because DSLs are not really programming languages I don’t have any real recourse other than to figure out how to work around the limitation.

Original Link

5 Questions to Ask Before Launching Your Citizen Development Strategy

Good strategy requires clear objectives, so that’s always a good place to start before introducing something new into your organization. As a CIO or IT professional, maybe you’re already convinced of the benefits of citizen development and ready to get it moving. But where to start first? What is your vision for citizen development within your organization? What do you hope to achieve with citizen developers and a no- or low-code platform?

It is likely that many people in your organization will not yet be familiar with citizen development, and more still will need to be convinced of not only its value, but also its viability. You’ll have to convince them of the "why" for your pursuit of citizen development in order to educate, generate support, and keep an overall vision central for all stakeholders.

Original Link

Why Are Engineers Getting DevOps Fatigue?

As an engineer, you already have enough responsibilities when developing software. Adding more tasks-say, DevOps-related ones-to your workday activities might not sound very appealing. With DevOps, not only are you responsible for producing working software, but now you also need to automate the building, testing, and deployment phases of the software. That’s a lot to take care of! But the extra work aside, maybe you’re just tired of the DevOps movement, and all the hype surrounding it is causing DevOps fatigue.

As a former developer, I can identify with that feeling of fatigue. I’ve also seen some colleagues reach a certain level of frustration with DevOps. There are times when we make the mistake of taking on everything, even the releases. This is especially common if we’re perfectionists and don’t like to deliver software with bugs. We could even get to the point of releasing our code to production. (Although now that you’re "doing" DevOps, that might become your responsibility anyway.) After all, if we code it, we know the things that could go wrong and how to fix it if there are problems.

Original Link

Why Are Engineers Getting DevOps Fatigue?

As an engineer, you already have enough responsibilities when developing software. Adding more tasks-say, DevOps-related ones-to your workday activities might not sound very appealing. With DevOps, not only are you responsible for producing working software, but now you also need to automate the building, testing, and deployment phases of the software. That’s a lot to take care of! But the extra work aside, maybe you’re just tired of the DevOps movement, and all the hype surrounding it is causing DevOps fatigue.

As a former developer, I can identify with that feeling of fatigue. I’ve also seen some colleagues reach a certain level of frustration with DevOps. There are times when we make the mistake of taking on everything, even the releases. This is especially common if we’re perfectionists and don’t like to deliver software with bugs. We could even get to the point of releasing our code to production. (Although now that you’re "doing" DevOps, that might become your responsibility anyway.) After all, if we code it, we know the things that could go wrong and how to fix it if there are problems.

Original Link

Why I Practice TDD: Speed and Need

“We need you to go faster, so we need you to stop practicing test-driven development,” said the manager. “Just ship it, and we’ll worry about problems later.”

For developers who have ingrained TDD as just how they develop software, the manager’s proposition is laughable. It’s akin to telling a race car driver, “We need you to go faster, so we’re going to take out the steering wheel, and we’re going to turn the windshield into seamless, opaque body molding for aerodynamic reasons.”

Original Link

Why You Need a DevOps Consultant

Efficiency is one of the fundamental pillars upon which any successful business is built. We’re all familiar with the old adage that “Time is money,” but many companies don’t appreciate just how deep this simple observation runs.

Amongst businesses who do prioritize the efficiency of their operations, there is an ongoing need to devise better workflows and to identify where other inefficiencies lie.

Original Link

Increasing Deployment Safety With Metric-Based Canaries [Video]

In September, Brandon Leach, Sr Engineering Manager at Lookout, gave a talk at our Test in Production Meetup on Increasing Deployment Safety with Metric-Based Canaries.

"You can configure a canary to watch any metric you want, like here we’re watching system metrics and application-based metrics. You can see we’re watching for response codes, other application metrics, and other system-level metrics like memory utilization and CPU."

Original Link

Why Continuous Integration Isn’t Improving Software (Yet)

The University Zurich’s study, Continuous Code Quality: Are We (Really) Doing That? quantifies the practices performed by developers to understand how continuous code quality is applied to projects in continuous integration. Their research reveals a strong dichotomy between theory and practice: developers do not perform continuous inspection but rather only focus on controlling software quality at the end of a sprint, and even then, only focus on the release branch.

Continuous code quality, also known as continuous inspection, is a core principle of continuous integration that includes automated testing, automated code inspection and performing static/dynamic code analysis at every build as a way to continuously improve code quality.

Original Link

How to Write Software: 5 Lessons Learned from Running Businesses

I used to write software for a living. I did that for a lot of years, as a matter of fact. And, in doing so, I learned a lot about how to write software.

But I learned this from the perspective of, well, a wage software developer. Today, I’d like to reflect on how my view has evolved over the last number of years.

Original Link

5 Effective Ways to Reduce Custom Software Development Costs

Too many software projects fail. Yup, we did it! Someone had to address the elephant in the room. Planning inadequacies and lack of communication are the essential reasons for the failure of custom software development, way more than technical incompetencies or unattainable requirements. Custom software development is far from quintessential and thus, the word “custom.” There might be a few similarities between some projects, but each project is a cluster of innovative ideas and business logic.

A recent Harvard Business Review article revealed that one in six IT projects has a cost overrun of 200%. Sounds like an industry that loves to fail. So, how can we reduce the expense of custom software development? Do it yourself? That goal is unreachable when it comes to software. And it is unimaginable to think that a modern business can prosper without software. As a result, costs skyrocket and eventually might even displace the company’s overall profit, especially for a startup and new small firm. Then, is there even a way to develop a custom software without losing all your money? Can we save costs in software development & maintenance? Absolutely.

Original Link

Wanted: Managed Services for Murdering DevOps

The growth of managed services has provided the developers with cloud-based infrastructure management tools, thus making the DevOps teams obsolete for startups and small businesses.

After the introduction of Agile methodology, developers, operations engineers, and QA specialists received powerful tools for streamlining the delivery of new software. Their teams became more closely connected, as developers stopped tossing the code over the wall for Ops engineers to deploy and maintain.

Original Link

50 Useful Docker Tutorials, From Beginner to Advanced (Part 1)

Containers bring many benefits to DevOps teams along with a number of security concerns. This post brings you details about 50 Docker training resources that are designed to train beginner, intermediate, and advanced practitioners on current knowledge about Docker.

Containers can be a big help in shipping and deploying your application where it’s needed. But using them adds a layer of complexity to your architecture and can be painful to implement and operate. The introduction of Docker to the IT community transformed the way many departments handled this type of work.

Original Link

Junior, Middle and Senior: How to Effectively Build a Team of Different Level Specialists

The success of any project in many ways depends on the team. Even a small product is mostly designed by a team, even if that team consists of just two people. Building an effective team is very important and, at first glance, this looks like a much simpler task than it really is.

Each member of the team has his own opinion and vision about the project, its development, evolution, and other processes. It is necessary to organize everything in such a way that all these factors will be in harmony with each other, and specialists’ joint efforts will be focused on achieving the customer’s specific business objectives. Therefore, this must be taken into account when starting a project.

Original Link

Decoupling Policy Decisions From Policy Enforcement for Agile Development

Developers are under increasing pressure for faster application delivery. Security is traditionally seen as something that can slow down the process because security scans, configuration checks, and of course discovery of vulnerabilities or bugs can slow things down. Instead, we can use policy as a way to implement security into the coding process for greater security control as your development becomes more agile.

In this article, we’ll look at how policy for software development helps define rules to manage access and protect information and systems. Then we’ll discuss the benefits of policy enablement, which decouples policy decisions from policy enforcement so you can offload policy decisions from your applications. This gives you more control and flexibility to make changes or updates to policies without affecting the application.

Original Link

DevOps Enterprise Summit 2018, Day One Recap: The ”Project to Product” Movement

In his opening remarks to the Las Vegas iteration of DevOps Enterprise Summit 2018, Gene Kim set the tone for Day One by providing an alternative definition of DevOps via Jonathan Smart (formerly of Barclays): “Better Value Faster, Safer, Happier.” At the London show in June, Jonathan expanded on that by extolling the pressing need to go beyond Agile and DevOps to think more end-to-end about how we build products.

DevOps legend Gene Kim kicks off proceedings with aplomb.

Four months later, amid the glowing neon lights of Sin City, that key message has evolved and intensified. Traditional organizations are moving away from a project approach towards a product-centric model, and focusing on the flow of work and business value across their value streams. That sentiment was echoed across the show floor and the stage as the DevOps and wider IT community considered how to take DevOps and enterprise software delivery to the next level. How do they transform their business in the Age of Digital Disruption? How does IT deliver more value to the business?

Original Link

How to Format a Large Codebase Automatically

If you introduce code formatting rules retroactively, you have to solve the problem of how to format existing codebase according to the new formatting rules. You could check out every code repository one by one in your IDE and click on Autoformat the whole project. But this is boring and a waste of time. Fortunately, Intellij IDEA has a format CLI tool in its installation. You can locate it in the path <your Intellij IDEA installation>/bin. It’s called

In the next section, I’d like to show you how you can automate formatting big code base. First, I will show the preparation steps like exporting your code formatting rule setting from the IDE. Then, I will demonstrate how to use the CLI-Tool At the end, I will show a small Groovy script that query all repositories (in this case they are Git repositories), formatting the code and push it back to the remote SCM.

Original Link

A Cambrian Explosion of DevOps Tools

Any discussion of how to scale the benefits of DevOps invariably lands on tools. The planning, tracking, automation, and management tools we use define the "ground truth" of where and how work happens. One of the most interesting, and at times challenging, aspects of agile and DevOps transformations is the sheer volume of tools involved. How many are required? Must there be so many? Before we proceed further on our journey of defining value stream architecture, let’s look at how this ground truth has evolved to get us where we are today.

The Catalyst for DevOps Tool Diversification

We’re at an interesting time in the evolution of DevOps tools; the sheer number of available tools points to a sort of Cambrian explosion of tool specialization and diversity. Is all this diversity necessary? Will a big wave of consolidation drive the extinction of most of these tools? What are the lines of specialization driving the diversity, and do we need to consider them when architecting our software value streams? We need to address these questions and inspect the ground truth captured in today’s toolchains in order to inform the discussion of how to abstract away the tools’ implementation details to focus on the architecture of our value streams.

Original Link

Something Is Missing in The Agile Manifesto

As Agilists we keep using the Agile Manifesto and are pretty much beyond questioning the exact words on the page. One key one is:

"Working Software over comprehensive documentation."

Original Link

Low-Code — Implications for Developers

Modern application development is a complex business, requiring multiple language support, knowledge of tools to build, test, and deploy applications, understanding of client experience, data handling, security skills, and the ability to provide experiences on multiple channels including web, mobile, and desktop.

In addition, developers are adapting to enable rapid app building by utilizing agile methodologies in parallel with a DevOps mindset and culture for delivery. Financial service institutions are increasingly adopting an iterative approach to providing apps and updates to the business, where regular small-scale updates/improvements are made to systems and customer/user interfaces with minimal disruption to their consumers.

Original Link

9 Reasons DevOps Is Better With Docker and Kubernetes

One of the main challenges that companies face with is a long time to market, which usually happens when your development process is slowed down. When deploying applications most of the teams usually face a problem between Dev and Ops because these two departments make the same application but work completely in different ways.

Wouldn’t it be nice if they work together without any misunderstandings to make shorten time to market? I’ve assembled this list of advantages that DevOps plus Docker and Kubernetes can provide you compared to a traditional DevOps approach.

Original Link

Refactoring: How Do Agile and DevOps Processes Affect Software?

Agile and DevOps adoption continues to accelerate and scale across organizations, yet the question many executives, and researchers, are asking is: Are Agile and DevOps practices improving the software itself? 

To offer deeper insight, Carmine Vassallo, Fabio Palomba, and Harald C. Gall of the Department of Informatics at the University of Zurich, have released several studies that look at DevOps and Agile outcomes by examining the impact of continuous refactoring on software quality.

Original Link

5 Steps to Automated NetOps

In Juniper Networks’ anthology of 5-step frameworks, we take a different turn. Instead of focusing on a network domain vertical like the 5-steps for data center, campus, WAN and branch, we are focused horizontally across all domains on network automation. This 5-step can apply to any place in network, and be overlaid like a transparency, for example, over the data center 5-step.

Not 5 Steps to Network Automation

Sometimes you climb the ladder only to find it’s standing against the wrong wall. 

Original Link

Software Engineering Daily — GitOps Key Takeaways

In a recent episode of Software Engineering Daily, Alexis Richardson spoke with Jeffrey Meyerson and recorded a podcast on GitOps. Here is a small excerpt from that interview.

When did convergence start to happen around the ideas that became GitOps?

Original Link

DevOps: The Blue Ocean Tide Is Rising

As the CEO at Sonatype, I have long believed that software is the last path to differentiation in every industry. From banking to manufacturing to healthcare to entertainment, companies capable of delivering innovative software applications are disrupting established players and growing shareholder value.

To survive and compete effectively, organizations are placing intense pressure upon IT leaders to accelerate the pace of software innovation. In response, companies are hiring armies of software developers, consuming unprecedented amounts of open source components, and embracing DevOps patterns and practices to continuously deliver applications to production.

Original Link

In Case of Emergency, Do Not Break — Feature Flagging

What happens to your application when your feature flagging system goes down? There are two possibilities: fail-safe or fail-broken.

The first possibility is that nothing happens. This is the fail-safe mode. No updates to flag states are made, but everything continues to operate the way it has all along. And when the feature flagging system comes back up, there are no changes from the user point of view. This kind of system works because the flag state is set and then maintained on the client side-the flag evaluations are already made.

Original Link

Kubernetes in the DevOps Space: Everything You Need to Know

It can be rightly said that Kubernetes and DevOps are the power couple of the cloud! They run hand-in-hand for enterprises looking to develop complex applications. You may be thinking, both DevOps and Kubernetes have a different context — how this is possible?

In our previous blog, we described every bit about Kubernetes, but how are Kubernetes and DevOps related to each other? What output can software developers and enterprises get if all these terms are mapped together?

Original Link

How to Improve Software Delivery Performance

Software value stream mapping and the ability to visualize how work flows through an ever-changing and complex software delivery system enables teams to measure metrics and provide quick analysis to see if your system is performing well or not.

But where do you start with all of that? Where do you start improving, where do you spend your time? What do the elite performers have in common? The Accelerate: 2018 State of DevOps report by DevOps Research and Assessment surfaces capabilities that are statistically shown to improve software delivery performance and are shared across high performing teams and organizations.

Original Link

Agile Adoption and the Survival of the Fittest

We are living in 21st century and have evolved a lot, from transportation, communication, entertainment and everything which is around us today. We all might have read Darwin’s theory of evolution. The gist of this theory is the humans are the most adaptable species among all due to which it survived all the calamities of nature. The process of adaptation is still in progress. Darwin has rightly stated, “It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is most adaptable to change.”

Today humans are living in every corner of the globe in varied rigid climatic conditions. Some regions are too hot and some are too cold for survival, but humans have adapted those conditions for their need to survive. As time passed, new things evolved and humans adapted everything for their survival and evolved as the strongest.

Original Link

5 Quick Wins for Securing Continuous Delivery

“DevOps is Agile on steroids — because Agile isn’t Agile enough.”

So says Jim Bird, the CTO for BiDS Trading, a trading platform for institutional investors. Jim continued, "DevOps teams can move really fast…maybe too fast? This is a significant challenge for operations and security. How do you identify and contain risks when decisions are being made quickly and often by self-managing delivery teams? CABs, annual pen tests, and periodic vulnerability assessment are quickly made irrelevant. How can you prove compliance when developers are pushing their own changes to production?"

Jim was presenting at the 2018 Nexus User Conference on Continuous Delivery. Pulling on his 20+ years of experience in development, operations, and security in highly regulated environments, Jim laid how and why Continuous Delivery reduces risk and how you can get some easy wins toward making it more secure.

Original Link

Women in DevOps: Charity Majors

Charity Majors is the CEO and founder of, a data-driven platform that helps developers debug their applications, software code, and databases. Formerly with Facebook, Parse and Linden Lab, Charity is an outspoken individual looking to encourage leadership skills among diverse groups in the software industry.

What character traits/habits make you successful in DevOps?

Original Link

What Does a Good Minimum Viable Product (MVP) Look Like?

The key to a successful MVP is not any specific feature or any product-oriented characteristic. In fact, a successful MVP will almost always not be very good.

Purpose of an MVP

The purpose of an MVP is not to design something and then test it to see if it’s good. The purpose of an MVP is to conduct as quick of an experiment as possible in order to learn something about the ultimate direction your product should take to be successful in the market. You use an MVP for the same purpose that you conduct a scientific experiment: to test whether or not some kind of theory holds true in the real world. But you have to be careful because releasing any product that’s not very well-developed can always do damage to your business. Therefore, the MVP must be able to test an idea in a way that’s very small in scale and limits the negative impact that can result from releasing an experimental product.

Original Link

  • 1
  • 2
  • 5