You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| A/B Testing | Deploy different versions of an EUT to different customers and let the customer feedback determine which is best. |
17
19
| Administration Testing | The purpose of the test is to determine if an End User Test (EUT) is able to process administration tasks as expected. |
18
-
| Agile | A project management method for complex projects that divides tasks into smal "sprints" of work with frequent reassessment and adaption of plans |
20
+
| Agile | A project management method for complex projects that divides tasks into small "sprints" of work with frequent reassessment and adaption of plans |
19
21
| Agile Coach | Help teams master Agile development and DevOps practices; enables productive ways of working and collaboration. |
20
22
| Agile Manifesto | A formal proclamation of values and principles to guide an iterative and people-centric approach to software development. |
21
-
| Agile Portfolio Managment| Involves evaluating in-flight project and proposed future initiatives to shape and govern the ongoing investment in projects and discretionary work. |
22
-
| Agile Principles | The tweleve principle that underpin the Agile Manifesto |
23
-
| Agile Process Owner | An ITSM or other type of process own that uses Agile and Scurm principles and practices to design, manage and measure individual processes. |
24
-
| Agile Service Manager | The operational equivalent to Dev's ScrumMaster. A role within an IT organisation that understand how to leverage Agile and Scurm methods to improve the design speed and agility of ITSM processes. |
25
-
| Agile Software Development | Group of software development methods in which requirement and olutions evovle through collaboration between self-organzing, cross-functional teams. Usually applied using the Scrum or Scaled Agile Framework approach. |
26
-
| Amazon Web Services (AWS) | AWS is a secure cloud services platform offering comupute power, database storage, content delivery and otehr functionality to help businesses scale and grow. |
23
+
| Agile Portfolio Management| Involves evaluating in-flight project and proposed future initiatives to shape and govern the ongoing investment in projects and discretionary work. |
24
+
| Agile Principles | The twelve principle that underpin the Agile Manifesto |
25
+
| Agile Process Owner | An ITSM or other type of process own that uses Agile and Scrum principles and practices to design, manage and measure individual processes. |
26
+
| Agile Service Manager | The operational equivalent to Dev's ScrumMaster. A role within an IT organisation that understand how to leverage Agile and Scrum methods to improve the design speed and agility of ITSM processes. |
27
+
| Agile Software Development | Group of software development methods in which requirement and solutions evolve through collaboration between self-organising, cross-functional teams. Usually applied using the Scrum or Scaled Agile Framework approach. |
28
+
| Amazon Web Services (AWS) | AWS is a secure cloud services platform offering comupute power, database storage, content delivery and other functionality to help businesses scale and grow. |
27
29
| Analytics | Test results processed and presented in an organised manner in accordance with analysis methods and criterion |
28
30
| Andon (Cord) | A system that gives an assembly line worker the ability, and moreover the empowerment, to stop production when a defect is found and immediately call for assistance. |
29
-
| Ant-pattern | A commonly reinvented bu poor solution to a problem. |
30
-
| Anti-fragility |Antifragility is a property of systems that increases it capability to thrive as a result of stressors, shocks, volatility, noise, mistakes, faults, attacks, or failures. |
31
+
| Ant-pattern | A commonly reinvented but poor solution to a problem. |
32
+
| Anti-fragility |Anti-fragility is a property of systems that increases it capability to thrive as a result of stressors, shocks, volatility, noise, mistakes, faults, attacks, or failures. |
31
33
| Application Programming Interface (API) | A set of protocols used to create applications for a specific OS or as an interface between modules or applications. |
32
34
| API Testing | The purpose of the test is to determine if na API for an EUT functions as expected. |
33
35
| Application Release | Controlled continuous delivery pipeline capabilities including automation (release upon code commit). |
34
36
| Application Testing | The purpose of the test is to determine if an application is performing according to its requirements and expected behaviors. |
35
37
| Architecture | The fundamental underlying design of computer hardware, software or both in combination. |
36
-
| Artifact | Any element in a software development project inclding documentation, test plans, images, data files and executable modules. |
38
+
| Artifact | Any element in a software development project including documentation, test plans, images, data files and executable modules. |
37
39
| Artifact Repository | Store for binaries, reports and metadata. Example tools include: JFog Artifactory, Sonatype Nexus or Azure Artifacts. |
38
-
| Audi Managment| The use of automated tools to ensure products and services are auditable, including keeping audit logs of build, test and deplooy activities, auditing configurations and users, as well as log files from production operations. |
39
-
| Authentication | The process of verifying an asserted identity. Authentication can be based on what you know 9e.g. password or PIN), kwhat you have (token or one-time code), what you are (biometrics) or contextual information. |
40
+
| Audi Management| The use of automated tools to ensure products and services are auditable, including keeping audit logs of build, test and deploy activities, auditing configurations and users, as well as log files from production operations. |
41
+
| Authentication | The process of verifying an asserted identity. Authentication can be based on what you know 9e.g. password or PIN), what you have (token or one-time code), what you are (biometrics) or contextual information. |
40
42
| Authorisation | The process of granting roles to users to have access to resources |
41
-
| Auto-DevOps | Auto DevOps brings DevOps best practices to your project by automatically configuring software development lifecycles. It automatically detects, builts, test, deploys and monitors applications. |
43
+
| Auto-DevOps | Auto DevOps brings DevOps best practices to your project by automatically configuring software development lifecycles. It automatically detects, builds, test, deploys and monitors applications. |
42
44
| Auto-scaling | The ability to automatically and elastically scale and de-scale infrastructure depending on traffic and capacity variations while maintaining control of costs. |
43
45
| Automated Rollback | If a failure is detected during a deployment, an operator (or automated process) will verify the failure and rollback the failing release to the previous known working state. |
44
46
| Availability | Availability is the proportion of time a system is in a functioning condition and therefore available (to users) to be used. |
| Backlog | Requirements for a system, expressed as a prioritized list of product backlog items usual in the form of 'User Stories'. The product backlog is prioritized by the Product Owner and should include functional, non-functional and technical team-generated requirements. |
53
+
| Basic Security Hygiene | A common set of minimum-security practices that must be applied to all environments without exception. Practices include basic network security hardening, vulnerability and patch management, logging and monitoring, basic polices and enforcement and identity and access management. |
54
+
| Batch Sizes | Refers to the volume of features involved in a single code release |
55
+
| Behavior Driven Development | Test cases are created by simulating an EUT's externally observable inputs, and outputs. Example tool: Cucumber. |
56
+
| Beyond Budgeting | A management model that looks beyond command-and-control towards a more empowered and adaptive state. |
57
+
| Black-Box | Test case only uses knowledge of externally observable behaviors of an EUT. |
58
+
| Blameless Postmortems | Used for impact analysis of service incidents. When a particular IT service fails, the users, customers, other dependent service that are affected. |
59
+
| Blast Radius | Used for impact analysis of service incidents. When a particular IT service fails, the users, customers, and other dependent services that are affected. |
60
+
| Blue/Green Deployments | Taking software from the final stage of testing to live production using two environments labelled Blue and Green. Once the software is working in the green environment, switch the route so that all incoming requests go to the green environment - the blue one is now idle or used for new feature updates. |
61
+
| Bug | An error or defect in software that results in an unexpected or system-degrading condition. |
62
+
| Burndown Chart | A chart showing the evolution of remaining effort against time. |
63
+
| Bursting | Public cloud resources are added as needed to temporarily increase the total computing capacity of a private cloud. |
64
+
| Business Case | Justification for a proposed project or undertaking on the basis of its expected commercial benefit. |
65
+
| Business Continuity | Business continuity is an organisation's ability to ensure operations and core business functions are not severely impacted by a disaster or unplanned incident that take critical services offline. |
66
+
| Business Transformation | Changing how the business functions. Making this a reality means changing culture, processes, and technologies in order to better align everyone around delivering on the organisation's mission. |
67
+
| Business Value | The benefit of an approach to key business KPIs |
0 commit comments