Agile Glossary

All | A B C D E F H I K L M N P R S T U V W
There are currently 8 names in this directory beginning with the letter C.

A regular, predictable rhythm or heartbeat. Actualizations of the concept include running Sprints of a consistent duration to establish a rhythm for a development effort, and releasing code to production in accordance with a reasonably consistent, time-based pattern.
Submitted by: Phil Rogers

1. In a general Agile team context, the amount of work that can be completed by that team during a given time interval, based on evaluation of the past history of that team, along with other data, as available; 2. In a Kanban context, a number that is set on a particular workflow state, to indicate the Work in Progress (WIP) limit, such that a new work item can only enter that workflow column when there is available capacity. For definition #1, it is important to point out that capacity is specific to that particular team.
Submitted by: Phil Rogers

Change Management
A process or mechanism through which changes are introduced, at a systemic (organizational) level, or at a more tactical level, such as changes to a particular product or set of products. Various change management models exist, with different levels of rigor and complexity. In iterative software development, change management is essentially a continuous activity, throughout the product lifecycle.
Submitted by: Phil Rogers

Component Team
A team that has an area of focus that tends to fall in one of these two categories: 1) working on a particular service; 2) working on a particular technical specialization, or a group of related areas of technical specialization. As such, component teams often work in areas that have strict Service Level Agreements (SLAs).
Submitted by: Phil Rogers

Continuous Deployment
An extension of Continuous Integration, where the goal is to minimize lead time. The team relies on infrastructure that automates and instruments steps leading up to deployment, so that after each integration successfully meeting release criteria, the live application is updated with new code. Instrumentation is necessary to ensure that any suggestion of lowered quality results in aborting the deployment process, or rolling back the new features, and triggers human intervention.
Submitted by: Phil Rogers

Continuous Integration
The two main objectives are: minimize the duration and effort required by each integration; be able to deliver a product version suitable for release at any moment. To achieve these dual objectives, it is necessary to have an integration procedure which is reproducible and also mostly or entirely automated. Version control tools, team policies and conventions, and tools specifically designed for code integration are employed.
Submitted by: Phil Rogers

A development team that has everyone and everything it needs to produce a shippable product increment. To accomplish this, members of a team have many different skills, and seek to work together as much as possible to get the work done.
Submitted by: Phil Rogers

Cumulative Flow Diagram
A chart that shows the number of items in each state of a workflow over time. Such a chart shows the length of time that it takes, on average, for work items to progress through a particular workflow state, or through some or all of a system. The CFD also makes it easier to visualize where bottlenecks are building up, constraining the flow of work.
Submitted by: Phil Rogers