Agile Certified Practitioner Terminology

Agile Unified Process

A Simplistic and understandable approach to developing business application software using agile techniques and concepts. It is a simplifies version of the Rational Unified Process (RUP).

Behavior-Driven Development (BDD)

A System design and validation practice that uses test-first principles and English-like scripts.

Framework

A basic system or structure of ideas or facts that support an approach.

Daily Scrum

A brief, daily collaboration meeting in which the team reviews progress from the previous day. declares intentions for the currentday, and highlights any obstacles encountered or anticipated. Also Known as Daily Standup.

Crystal Family of Methodologies

A collection of lightweight agile software development methods focused on adaptability to a particular circumstance.

DevOps

A collection of practices for creating a smooth flow of delivery by improving collaboration between development and operation staff.

Hybrid Approach

A combination of two or more agile and non-agile elements, having a non-agile end result.

increment

A functional, tested, and accepted deliverable that is a subset of the overall project outcome.

Burndown Chart

A graphical representation of project work left to do versus time to do it.

Burnup Chart

A graphical representation of the work completed toward the release of a product.

Anti-Pattern

A known, flawed pattern of work that is not advisable.

Feature-Driven Development (FDD)

A lightweight agile software development method driven from the perspective of features valued by clients.

Acceptance Test-Driven Development (ATDD)

A method of collaboratively creating acceptance test criteria that are used to create acceptance test before delivery begins.

Agilist

A person embracing the agile mindset who collaborates with like-minded colleagues in cross-functional teams.

Agile Practitioner

A person embracing the agile mindset who collaborates with like-minded colleagues in cross-functional teams. Also referred to as agilist.

Continuous Integration

A practice in which each team member's work products are frequently integrated and validated with one another.

Continuous Delivery

A practice of delivering feature increments immediately to customers, often through the use of small batched of work and automation technology.

Backlog

A prioritized list of features or user stories to add to a program

Disciplined Agile (DA)

A process decision framework that enables simplified process decisions around incremental and iterative solution delivery.

double-loop learning

A process that challenges underlying values and assumptions in order to better elaborate root causes and devise improved countermeasures rather than focusing only on symptoms

Fit for Purpose

A product that is suitable for its intended purpose.

Fit for Use

A product that is usable in its current from to achieve its intended purpose.

Collective Code Ownership

A project acceleration and collaboration technique whereby any team member is authorized to modify any project work product or deliverable. thus emphasizing team-wide ownership and accountability.

cadence

A rhythm of execution. (See also Timebox)

Functional Requirement

A specific behavior that a product or service should perform.

Functional Specification

A specific function that a system or application is required to perform. Typically represented in a functional specification document.

Impact Mapping

A strategic planning technique that act as a roadmap to the organization while building new products.

Hoshin Kanri

A strategy or policy deployment method.

Cross-Functional Team

A team that includes practitioners with all the skills necessary to deliver valuable product increments.

Definition of Ready (DoR)

A team's checklist for a user-centric requirement that has all the information the team needs to be able to be begin working on it.

Definition of Done (DoD)

A team's checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use.

Mobbing

A technique in which multiple team members focus simultaneously and coordinate their contributions on a particular work item.

Agile Methodology

A term used to describe a mindset of values and principles as set forth in the Agile Manifesto.

Iteration

A timeboxed cycle of development on a product or deliverable in which all of the work that is needed to deliver value is performed.

Information Radiator

A visible, physical display that provides information to the rest of the organization enabling up-to-the-minute knowledge sharing without having to disturb the team.

Kanban Board

A visualization tool that enables improvements to the floe of work by making bottlenecks and work quantities visible.

A3

A way of thinking and a systematic problem-solving process that collects the pertinent information on a single A3-size sheet of paper.

Agile Mindset

A way of thinking and behaving underpinned by the four values and twelve principles of the Agile Manifesto.

Agile Coach

An Individual with n=knowledge and experience in agile who can train, mentor, and guide organizations and teams through their transformation.

Kanban Method

An agile method inspired by the original Kanban inventory control system and used specifically for knowledge work.

Dynamic Systems Development Method (DSDM)

An agile project delivery framework.

eXtreme Programming (XP)

An agile software development method that leads to higher quality software. a greater responsiveness to changing customer requirements, and more frequent releases in shorter cycles

Iteration Life Cycle

An approach that allows feedback for unfinished work to improve and modify that work.

Agile Life Cycle

An approach that is both iterative and incremental to refine work items and deliver frequently

Incremental Life Cycle

An approach that provides finished deliverables that the customer may be able to use immediately.

impediment

An obstacle that prevents the team from achieving its objectives. Also known as blocker.

IDEAL

An organizational improvement model that is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning.

Kaizen Events

Events aimed at improvement of the system.

Large Scale Scrum (LeSS)

Large-Scale Scrum is a product development framework that extends Scrum with scaling guidelines while preserving the original of Scrum.

Lean Software Development (LSD)

Lean Software Development is an adaptation of lean manufacturing principles and practices for achieving quality, speed, and customer alignment.

Business Requirements Document (BRD)

Listing of all requirements for a specific project.

Evolutionary Value Delivery (EVO)

Openly credited as the first agile method that contains a specific component no other methods have: the focus on delivering multiple measurable value requirements to stakeholders.

I-Shaped

Refers to a person with a single deep area of specialization and no interest or skill in the rest of the skills required by the team. See also T-Shaped and Broken Comb.

Broken Comb

Refers to a person with various depth of specialization in multiple skills required by the team. Also known as Paint Drip. (See also T-shaped and I-shape)

Backlog Refinement

The Progressive elaboration project requirements and/or the ongoing activity in which the team collaboratively reviews, updates, and writes requirements to satisfy the need of the customer request.

Flow Master

The coach for a team and service request manager working in a continuous flow or Kanban contect Equivalent to Scrum Master.

Agile Manifesto

The original and official definition of agile values and principles.

Organizational Bias

The preferences of an organization on a set of scales characterized by the following core values: exploration versus execution, speed versus stability, quantity versus quality, and flexibility versus predictability. 152page

Life Cycle

The process through which a product is imagined, created, and put into use.

Automated Code Quality Analysis

The scripted testing of code base for bugs and vulnerabilities.

Agile Principles

The twelve principles of agile project delivery as embodied in the Agile Manifesto.

Blended Agile

Two or more agile frameworks, methods, elements, or practices used together such as Scrum practiced in combination with XP and Kanban Method.

Blocker

tends to be negativistic or stubbornly resistant, opposing beyond reason or maintaining issues the group has rejected