Agility and devops Glossary

This vocabulary aims to illustrate various terms in agile and devops.
Due to the close relationship between agility and devops, a large number of words from agility need to be referenced when talking about devops. Therefore, this article tries to make some preparations.

Word name	English	Description
Reconstruction	Refactor	It is used to optimize the internal structure of an object by keeping its external behavior unchanged. Code refactoring is a type of refactoring.
Code Reconstruction	Code refactor	Optimize the code by keeping the external behavior of the program code unchanged. In object-oriented programming, it is typical to keep the external behavior of the class unchanged and optimize the internal structure of the class.
Test-driven development	Test driven development	Use testing methods to drive the design and implementation of software programs. The main feature of the method is to first write the test program and then code it to pass the test. Common Test-driven development can be divided into unit test-driven development and Acceptance Test-driven development.
Unit Test-driven development	Unit test driven development	The unit test method is typically used to design and implement the driver program. The main feature of the method is to write the unit test program first and then code it to pass the test.
Acceptance Test-driven development	Acceptance Test driven development	The acceptance test method is used to drive the design and implementation of software programs. The main feature of the method is to write an automated interface or interface for testing, and then encode it to pass the test.
Time box	Time box	Activities are carried out within a limited period of time, ending with time.
Iteration	Iteration	Activities that repeat the feedback process usually aim at approaching the desired goals or results. Each iteration is called an "iteration", and the result of each iteration is used as the initial value of the next iteration.
Agile Iteration	Agile Iteration	It refers to the short-term development of software based on the same development method, or the software that is not detailed in the preliminary development. After each development, the software that can be run is obtained for observation by stakeholders, obtain feedback and follow-up development based on feedback adaptability. After repeated development, the software is gradually added, supplemented and improved, and finally the final software is developed. Agile iterations include iterations and increments.
Feature-driven development	Feature Driven Development	FDD was originally conceived by Peter Coad and his colleagues as an object-oriented software engineering process model, and then expanded and enhanced the work of Coad, describes an adaptive agile process that can be used for medium and large software projects. It mainly includes developing a global model, constructing a feature list, feature planning, feature design, and feature building.
Review Meeting	Retrospective MEETING	This is a meeting required in scrum and can be used in a non-Scrum environment. The purpose of the review is to test people, relationships, processes, tools, and other aspects in the early stage. Tests should identify and focus on those that are progressing smoothly, and those that can achieve better results through different approaches. At the end of the review, the team should select the improvements to be taken in the next iteration.
Burnout Diagram	Burn down chart	A graphical representation of the work to be completed over time. A burned-out chart has a Y axis to indicate the work to be completed. Common examples are the number of stories to be completed, the work to be completed, and the number of user stories to be completed. The X axis indicates the time, average, the scale is workday. Ideally, this chart is a downward curve. As the remaining work is completed, the chart is burned to zero.
Planned MEETING	Planning Meeting	This is the meeting as required in scrum. The purpose of the plan meeting is to estimate the iterations that will be carried out immediately, clarify and select the items to be developed, and identify the follow-up actions.
User stories	User story describes the external behaviors of a product to be developed from the user's perspective. The collection of all user stories reflects the value (or commercial value) of products to users ).
Speed	Velocity	It indicates the speed of development. There are two common algorithms: 1) Number of story points after iteration completion; 2) Number of story points completed per day
Agile thinking	Agile thinking	Similar to agile spirit, agile concept, agile value, and other terms, there is no objective and strict definition at present. It is generally understood as the concept derived from the agile declaration, including focusing on team collaboration, respect for individuals, embrace changes, rapid response, focus on communication, focus on value delivery, Incremental delivery of available software, etc.
Agile Method Framework	Agile Method Framework	A system describes the core fields of software development and provides a global framework-oriented methodology. It is composed of multiple agile development practices based on this framework. For example, scrum, XP, FDD, and DSDM.
Agile practice	Agile practice	It refers to a development method that complies with the agile declaration to solve specific and local problems. Such as unit test-driven development, burn-out diagram, and user stories.
Agile management practices	Agile management practice refers to the practice of handling personnel interaction and information exchange in Agile development practices, such as planning meetings, review meetings, and burnout diagrams.
Agile engineering practices	Agile Engineering Practice	It is synonymous with agile technical practices. It refers to practices closely related to code implementation, testing, design, and Requirement Analysis in Agile development practices, such as refactoring, test-driven development, and evolutionary design, continuous integration, automated testing, and so on.
Agile technical practices	Agile Technical Practice	It is synonymous with agile engineering practices. It refers to practices closely related to code implementation, testing, design, and Requirement Analysis in Agile development practices, such as refactoring, test-driven development, and evolutionary design, continuous integration, automated testing, and so on.
Self-Organizing	Self-Organizing	In the field of natural science, self-organization refers to the process in which chaotic systems form a dissipation structure during random identification. In the field of software engineering, it can be understood as pointing to self-organizing (self-organizing in English) forward. Its basic characteristic is that each individual has its own autonomy, it can also integrate the overall features.
Incremental	Incremental	It refers to the available functions added on the basis of previous iterations.
Daily build	Daily build	Compile automatically on a daily basis, run the automated test to verify the build, and provide a report.
Continuous Integration	Continuous Integration	When the code is submitted, automatic compilation and automated testing are started immediately to quickly verify the software, so as to detect errors and code conflicts as soon as possible.
Continuous delivery	Continuous delivery	After the code is submitted, compilation, packaging, and installation can be started quickly and automatically in the running environment. Various types of automatic tests can be arranged during the process to ensure the delivery quality. Generally, continuous delivery includes continuous integration.
Continuous deployment	Continuous deployment	Continuous Automatic deployment to the production environment. Generally, continuous deployment is a form of continuous delivery.
Daily standing MEETING	Daily standup MEETING	In the scrum method, a project status meeting is held every day of each sprint. The meeting starts on time and lasts no more than 15 minutes. All members must stand. Each member answers three questions. 1. What have you done today? 2. What are you planning to do tomorrow? 3. Is there any problem blocking you?
To-do list	Product backlog	It refers to the list of product requirements (backlog entries can be user stories ). The product owner sorts the entries in the list based on the business value, and the team develops the items in sequence.
Epic	Epic	In general, it is a story of large users. Generally, it is composed of many large and uncertain demands and has a lower priority. Therefore, instead of performing iterative planning, you must first divide it into smaller and real user stories.
Application Deployment	Application Deployment	Deploy the compiled result to the running environment
Product Management	Artifact Management	Management of post-compiled products. Generally, post-compiled products with the same source code should be generated only once.
Finished Definition	Definition of done	The same as exit criteria and success criteria
Information Technology Service Management	ITSM (Information Technology Service Management)
Quality Check	Jkk Ji-kotei-kanketsu	From Japanese, there is a strict inspection step by step to ensure quality. The concept of jkk is a perfect state: Do not do low-quality work in your workflow, do not accept output errors that occur early in the process, and do not output bad situations to the next process.
Service Level Agreement	Service Level Agreement-SLA
Single-piece stream	One-piece-Flow
Work in Progress	Work-in-progress WIP

Agility and devops Glossary