Glossary

CONTINUOUS PRACTICES

Continuous Practices is a catch-all term for:

• Continuous Integration - regularly committing code changes back to a common location (trunk), thus minimising isolation and increasing feedback.
• Continuous Delivery - ensuring software is always in a releasable state.
• Continuous Deployment - ensuring software is continually promoted to a production environment (even if it's disabled for use).
• Some of the mechanisms that make the above concepts possible; e.g. Trunk Development (Branching Strategy), Blue/Green Deployments, Feature Flags, Canary Releases.

THE MOSCOW METHOD

MoSCoW (intentional emboldening) is a very simple (and quick) way to classify, and thus prioritise, ideas and activities, using a memorable acronym.

It uses:

• M(ust) - the activity is critical, so must be done.
• S(hould) - the activity should be done, but isn't critical.
• C(ould) - the activity is desirable, but not imperative.
• W(on't) - the activity won't be pursued.

REGRETFUL SPEND

Regretful Spend is the need to spend money or time on an activity that: doesn't meet your strategic goals, diverts you from more valuable activities, or has a short shelf-life. However, it may be required either to survive (The Three S's) or to alleviate others. Make sure you're not Overprocessing (The Seven Wastes) on Regretful Spend.

SATISFYING THE SYSTEM

All systems make certain expectations on those that use them; whether that's a person, or simply another system. Those are constraints that the consumer needs to satisfy.