Fundementals Flashcards
(109 cards)
Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change overa a plan
Agile Manifesto
An adaptive approach to project management that implies that requirements - made at the very start of a project - are expected to change and evolve as the project advances. It uses continual iterations to adapt and incorporate these changes.
Agile Project Management
The means to not only respond to and resist incidents and disruptions of all kinds but to use them as an opportunity for learning and adaptation.
Antifragility
An acronym for the values of DevOps: Culture, Automation, Lean, Measurement, and Sharing.
C.A.L.M.S
The level to which a service meets a customer’s expectations or exceeds them.
Business Value
A set of practices designed to ensure that code is always able to be deployed rapidly and safely throughout its lifecycle to production, achieved by pushing the executables into a production-like environment and conducting automated testing to detect problems.
Continuous Delivery
An extension of the concept of Continuous Delivery in which all changes that pass automated tests are automatically pushed into production. It automates the step that was previously manual in Continuous Delivery, and enables multiple deployments per day.
Continuous Deployment
The bundling of an entire runtime environment - into one package or “container” so that the application platform and its dependencies, differences in OS distributions and underlying infrastructure are abstracted away.
Containerization
The practice of merging all developer working copies into a shared mainline (a code repository or a main code trunk) throughout the day. Within an automated Continuous Delivery process, continuous integration covers mainly the build stage. Usually, continuous integration applies to integrating, building and testing code within the development environment.
Continuous Integration
The execution of automated tests at every stage of the deployment pipeline. It provides immediate feedback at each stage to mitigate risk. Automated continuous testing is a key component of continuous integration and delivery. It ensures that the code and environment operate properly and remain in a deployable state.
Continuous Testing
A 15-minute time-boxed Scrum event for the Development Team to synchronize activities and create a plan for the next 24 hours.‖
Daily Scrum
The ITIL® practice of moving new or changed hardware, software, documentation, processes, or any other service component to live environments.†
Deployment Management
Model your current delivery process as stages that then allow you to examine your end to end delivery for bottlenecks, opportunities for automation, and opportunities for collaboration.
Deployment Pipelines
States that “organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.”
Conway’s Law
A coined noun used to describe an evolution of existing IT best practices from ITIL, Lean and Agile into a development and operations approach that supports automation and continuous delivery, and encourages a culture of collaboration and learning to help IT deliver business value better, faster and cheaper than ever before.
DevOps
A model which provides guidance for continual improvement throughout five stages: Define, Measure, Analyze, Improve and Control.
DMAIC Cycle
Occurs when outputs are routed back as inputs as part of a chain of cause-and-effect that forms a loop.
Feedback
The Agile Scrum team which consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.‖
Development Team
The way people, information and products move through a process.
Flow
Testing of the features which are necessary for the product to work, including unit, API, integration or systems testing.
Functional Testing
Best practice guidance for IT service management
ITIL
Kanban emerged in the 1940s as part of the initial evolution of Lean manufacturing. It provided a way for assembly line workers to notify downstream partners of demand for parts or other work. This allowed for transparency and increased communication, and it standardized processes
Kanban
A quality system focused on flow. It is all about increasing customer value, eliminating waste, and continuous improvement.
Lean
An architecture in which one function is associated with one service which is scaled by distributing services across nodes.
Microservice Architecture (MSA)