DevOps Practices

 Continuous integration :

Continuous integration (CI) is a development practice that requires developers to commit code into a shared repository at least daily.

• Each check-in is validated by

– An automated build

– Automated unit, integration and acceptance tests

• Is dependent on consistent coding standards

• Requires subversion version control repositories and CI servers to collect, build and test committed code together

• Runs on production-like environments

• Integrates multiple code branches into a trunk (also known as a master)

• Must pass unit, acceptance and integration tests

• Allows for early detection and quick remediation of errors from code changes before moving to production

Continuous delivery :

Continuous delivery is a methodology that focuses on making sure software is always in a releasable state throughout its lifecycle.

• Takes continuous integration to the next level

• Provides fast, automated feedback on a system’s production-readiness

• Prioritizes keeping software deployable over working on new features

• Relies on a deployment pipeline that enables push-button deployments on demand

• Reduces the cost, time, and risk of delivering incremental change

Continuous testing :

Continuous testing is the process of executing automated tests as part of the deployment pipeline to obtain immediate feedback on the business risks associated with a software release candidate.

• Functional

– Unit tests, API, integration, system testing

• Non-functional

– Performance, security, compliance, capacity

Automated testing is a key aspect of Continuous Integration and Continuous Delivery and encourages a “shift left” testing strategy.

Testing and Deployment Strategies :

• Test driven development (TDD)

• Performance testing

• End-to-end use-case testing

• Security testing

• Manual testing

• Testing in production

“Shifting left” is about building quality into the software development process. When you shift left, fewer things break in production, because any issues are detected and resolved earlier.

Continuous deployment :

Continuous deployment is a set of practices that enable every change that passes automated tests to be automatically deployed to production.

• Removes the manual step in the deployment pipeline

• Results in multiple deployments per day

Continuous deployment may not be practical or possible for companies constrained by regulatory or other requirements.

Release is the process or event of making a feature (or set of features) available to a segment of customers.

Rugged DevOps :

Rugged DevOps is a method that includes security practices as early in the continuous delivery pipeline as possible to increase cybersecurity, speed, and quality of releases beyond what DevOps practices can yield alone.

• Rugged software development is a cultural approach to creating available, survivable, defensible, secure, and resilient software

• Rugged organizations are comfortable with instrumentation, experimentation and experience

• It is not the same as DevSecOps but related

DevSecOps :

The purpose and intent of DevSecOps is to build on the mindset that "everyone is responsible

for security" with the goal of safely distributing security decisions at speed and scale to those

who hold the highest level of context without sacrificing the safety required.

• Introduces security as code

• Embraces the “shift left” testing strategy

• Leverages automation for resilience, testing, detection and audit

ChatOps :

Chat client + chat bots = conversation-driven development, delivery and support.

The transparency of ChatOps shortens feedback loops, improves information sharing, enhances team collaboration and enables cross-training. It can also be used to decrease MTTR .

Kanban :

Kanban is a method of work that pulls the flow of work through a process at a manageable pace.

• Visualizes and manage workflow

• Pulls work for teams when they are ready for it

• Enables people to work collaboratively to improve flow

• Measures team velocity (quantity of work done in an iteration)

• Reduces idle time and waste in a process

• Makes work visible

• Make policies explicit

• Limits work in progress (WIP) to capacity

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...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
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 withou...
Read more