FMAP glossary

# Master glossary

**Adaptive approach.** A way of working that expects important learning or change and uses short feedback cycles to guide the next decision. It is not the same as avoiding plans.

**Agile.** A software-development movement associated with the 2001 Agile Manifesto. In this course, it names a set of values and principles for responding to uncertainty; it is not a product, a single framework, or a certification standard.

**Incremental.** Adding a usable part of a larger result. An increment creates an opportunity for feedback, but its existence does not prove value.

**Iterative.** Revisiting and improving work through feedback. Iteration may change a previous increment, a plan, or a way of working.

**Predictive approach.** An approach that invests more in early definition and sequencing because the work is well understood or late change is costly. It can be a sound choice.

**Hybrid approach.** A deliberate combination of predictive and adaptive practices. For example, a regulated filing may need fixed controls while a related service can be tested in small increments.

**Scrum.** A distinct framework defined by the official Scrum Guide. It is not another name for agile or for Kanban.

**Kanban.** A flow-oriented approach for knowledge work. The current Kanban Guide describes it as a strategy for optimising the flow of value through a process.

Use the [reference ledger](fmap-references.md) for the source boundaries behind these short definitions.