[go: up one dir, main page]
Scribd
Upload
411 views3 pages

Continous Integration (CI) Is A Development Practice Where Development Teams

The document discusses several key DevOps concepts: - Agility, continuous integration, continuous delivery, short releases, quality assurance, and automation which are important principles for efficient software development. - Continuous integration aims for small, frequent code changes to detect problems early. Continuous delivery focuses on producing software in short cycles to release code changes quickly. - Quality assurance and automation help ensure high software quality and reduce human efforts through system control and testing.

Uploaded by

chahoub
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
411 views3 pages

Continous Integration (CI) Is A Development Practice Where Development Teams

The document discusses several key DevOps concepts: - Agility, continuous integration, continuous delivery, short releases, quality assurance, and automation which are important principles for efficient software development. - Continuous integration aims for small, frequent code changes to detect problems early. Continuous delivery focuses on producing software in short cycles to release code changes quickly. - Quality assurance and automation help ensure high software quality and reduce human efforts through system control and testing.

Uploaded by

chahoub
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

• Agility

• Continous Integrity

• Continous Delivey

• Short release

• Quality Assurance

• Automation

Agility is refering to the approach of discovering requirements and developing solutions


through the collaborative effort of self-organizing and cross-functional teams and their end
user(s). It advocates adaptive planning, evolutionary development, early delivery, and
continual improvement, and it encourages flexible responses to change.

Continous Integration (CI) is a development practice where development teams


make small, frequent changes to code. As a result, development teams can detect
problems early in a way to release incremental code changes to production quickly
and regularly.

Continuous Delivey (CD) is an approach to software engineering based on producing


software in short cycles. By developing in short cycles, teams can reliably release their
software at any time. So, development teams can build, test, and release software faster and
more frequently. As a result, they can reduce the cost, time, and risk of delivering each
change.

Quality Assurance Software is a means to ensure proper quality of the software. It


includes standards (such as ISO 25010, SPICE or CMMI) and procedures that
managers, administrators or even developers may use to review and audit software
products and activities to verify that the software meets quality criteria which link to
standards.

Automation engineering is the integration of standard engineering fields. Automatic


control of various control system for operating various systems or machines to reduce
human efforts & time to increase accuracy.
The First Way:

The First Way states the following, about the flow of work:

 Work should only flow in one direction


 No known defect should be passed downstream
 Always seek to increase the flow

The First Way helps us think of IT as a value stream. Think of a manufacturing line,
where each work center adds a component – value – to the line. Since each work
center adds value, it is preferred, that each work center does it right the first time
around.

The Second Way:

The Second Way describes the feedback process as the following:

 Establish an upstream feedback loop


 Shorten the feedback loop
 Amplify the feedback loop

The Second Way teaches us to think of information as a value-addition. When timed


right and used the right way, feedback can help optimize the value stream.

The Third Way:

The Third Way describes the environment and culture, as the following practices

 Promote experimentation
 Learn from success and failure
 Constant improvement
 Seek to achieve mastery through practice

The Third Way teaches us that culture and environment are just as important as the
work being done. It advocates a culture of experimentation and constant
improvement. This results in measured risks and being rewarded for good results.

https://freshservice.com/itsm/phoenix-project-three-ways-devops-blog/
DevOps Concepts (2): Improvement Kata

https://medium.com/@paddycorry/why-the-improvement-kata-can-help-with-your-agile-
transformation-d1b44ade8a8d

You might also like