5. Environment provisioning for testing 6. Testing (QA) 7. Deployment to pre-production 8. Release management 9. Env. provisioning for production 10. Deployment and release to production

1. Quick time to market - delay of promised new features although agility is being adopted 2. Issues in code quality & application stability - code comes back at the same speed 3. Drop in SLAs for support and operations - steady drop in SLA’s for resolving queries

DevOps and Agile Flashcards by Edgar Woode

Provides Mechanisms

Perform software development, testing, and deployment in an automated and synchronized fashion

Quick time to market

How well did you know this?

Not at all

Perfectly

Provides Mechanisms and benefits 1

Perform deployments with great quality and stability in short duration of time

Reliable and stable applications

How well did you know this?

Not at all

Perfectly

Provides Mechanisms and benefits 2

Ensure support teams are enabled

Maintain service level agreements(SLA) for support related activities

How well did you know this?

Not at all

Perfectly

Continuous integration

Code Analysis
Unit testing
Code coverage
Build

How well did you know this?

Not at all

Perfectly

Continuous Delivery

Environment provisioning for testing
Testing (QA)
Deployment to pre-production
Release management
Env. provisioning for production
Deployment and release to production

How well did you know this?

Not at all

Perfectly

Need for DevOps

Quick time to market - delay of promised new features although agility is being adopted
Issues in code quality & application stability - code comes back at the same speed
Drop in SLAs for support and operations - steady drop in SLA’s for resolving queries

How well did you know this?

Not at all

Perfectly

DevOps definition

Business, Devs/QA, and Ops work together with common goal process and metrics to achieve speed, quality for early and continuous delivery for valuable software

How well did you know this?

Not at all

Perfectly

Benefits of DevOps

Quick to market
Reliable and stable
Maintenance of service levels for support and ops

How well did you know this?

Not at all

Perfectly

Involves a collaborative working

Development
Testing
Infrastructure
Ops Team

How well did you know this?

Not at all

Perfectly

DevOps maturity is measured by..

The speed, frequency, stability and quality of releases

How well did you know this?

Not at all

Perfectly

DevOps is driven by…

Automation

How well did you know this?

Not at all

Perfectly

DevOps is not…

Conglomeration of tools and their synchronization

Jenkins tools for orchestration of some build activities

How well did you know this?

Not at all

Perfectly

Managed by..

Stakeholders and Vendors

How well did you know this?

Not at all

Perfectly

People and process dimensions are…

Very critical in DevOps adoption

How well did you know this?

Not at all

Perfectly

People transformation

Stage 1 - Dev & Ops separate
Stage 2 - Progressive Dev + Ops
Stage 3 - Integrated DevOps

How well did you know this?

Not at all

Perfectly

Process adoption

Stage 1 - a separate dev and ops processes with interventions
Stage 2 - enhanced process to accommodate dev and ops tasks
Stage 3 - unified process with unified metrics

How well did you know this?

Not at all

Perfectly

Technology innovation

Stage 1 - Continuous Integration
Stage 2 - Continuous delivery
Stage 3 - Monitoring and support

How well did you know this?

Not at all

Perfectly

Challenges in DevOps Adoption 1

People
Conflict in goals
Little collaboration 
Ops teams not sensitized on the requirements & urgency of deployments 
Geographically distributed teams

How well did you know this?

Not at all

Perfectly

Challenges in DevOps Adoption 2

Process
Delays due to formal knowledge transfer
Tedious change management process
Complex release management process

How well did you know this?

Not at all

Perfectly

Challenges in DevOps Adoption 3

Study These Flashcards

Technology
Lack of automation
Defects generated due to inconsistent environments
Delays due to infrastructure unavailability

Stakeholders involved for successful DevOps adoption

Study These Flashcards

Business
Dev teams 
Test teams
Infrastructure teams
Ops teams

Capabilities to be built for DevOps: Business

Study These Flashcards

Agile approach
Automated acceptance test
Rapid prototyping 
Lean processes
Big room planning

Capabilities to be built for DevOps: Dev team

Study These Flashcards

Continuous integration 
Build automation 
Agile approach
Micro services
Feature toggle
Version control
Code quality analysis 
Code coverage
Unit test automation 
Artifact repository 
Incremental design

Capabilities to be built for DevOps: Test team

Study These Flashcards

Functional test automation 
Test management 
Test Data management 
Service virtualization 
Performance test automation 
Security test automation
Progressive test automation

Capabilities to be built for DevOps: Infra team

``` Database deploy Infrastructure layer Environment management CD automation Release management Containerization On demand infra Infra-as-code Just enough infra ```

Capabilities to be built for DevOps: Ops team

``` Incident management tools Support analytics Monitoring and dashboard Predictive monitoring Self healing ```

Technology stacks

Depends on the project, tech, and customers desire for automation

SDLC

Planning stage Construct stage Validate/Test Deploy and Release

Application life cycle management tools

Tool used in Planning stage Ex: Jira

Scrum Design phase tool

Rapid prototyping tool Ex: Infosys rapid prototyping tool

Scrum Construct build phase

Version control tool Ex: GIT Static code quality analysis tool Ex: Sonarcube Dynamic code quality Ex: probe Unit testing Ex: JUnit Code coverage, check the quality of tests written Ex: JaCoCo, Cobertura Code review Ex: Jupiter Build automation, code built Ex: Maven, Grunt

Baseline in Artifact repository

Where the word file with the code goes so that the next stages can pick up from the right folder. Ensures the same version of the binary file undergoes testing, deployment to pre production, release to production Construct stage Ex: Nexus, Artifactory

Continuous Integration

Where all the build activities from static code analysis to construction of the word file to baselining in artifact repository are sequenced and orchestrated Construct stage and beginning of validation Ex: Jenkins, Bamboo

Validation is also orchestrated through..

Continuous Integration engine

Deployment and Database Deployment

Automated deployment of application/database, next step of SDLC Ex: liquibase

Functional/Acceptance testing, Performance testing, and Security testing

Testing done in validation step of SDLC Tool Ex: functional testing, selenium Performance testing, JMeter Security testing, AppScan

Test and defect management and Test Data management

Tool Ex: Zephyr Jira

Continuous validation + deployment to pre-production environment =...

Continuous delivery

Environment management tool

Used for the Environment for deployment in the pre-production environment Used in tandem with a virtual environment using a cloud or Environment for testing and also be configured using these tools Ex: Chef, puppet

Release management tools

Used for approvals for release Ex: XL Release

Incident management/Support analytics/Monitor Dashboard

Used to keep support and operations teams up to speed in the activities associated with SDLC Ex: Nagios, splunk

Developer role in DevOps set up

Collaborative planning for dev (+test) and ops activities Resolving recurring Ops issues Understanding and developing as per Ops requirements Build automation and continuous integration

Tester role in DevOps

Test automation (all phases including service virtualization) Test data deploy management Understanding Ops scope of work needs Performing Ops-like testing for Ops-like metrics (e.g security)

Ops role in DevOps

Providing Ops insights to Dev Understanding Dev stories/configuration Proactive planning for releases Continuous integration for continuous KT

Automation experts

``` End to end pipeline automation for build progression Infra and release automation Infra testing Database deploy automation Dynamic test data management ```

Process Models | Model 1: Dev & Ops separate

Two separate teams Teams follow their own processes Teams brought together through common points of intervention Teams discuss issues and dependencies

Process models | Model 2: Dev & Ops separate but following similar process

Teams separate Representatives of ops and testing in Dev teams Teams start to follow the same processes

Process models | Model 3: Unified process

Single DevOps team | Scrumban model

DevOps and Agile Flashcards

(48 cards)