Keep release cadence by controlling scope with guardrails such as WIP limits, clear policies, and a solid Definition of Done. Use release trains or trunk‑based practices to ship small, high‑quality increments consistently.
Feature creep is best described as ______.
increasing test automation coverage
removing obsolete features to simplify UX
reducing work‑in‑progress to improve flow
unplanned scope growth that dilutes focus and delays releases
Which Kanban control directly limits overload and protects cadence?
QA after every six sprints only
daily standups lasting 60 minutes
infinite backlog grooming
work‑in‑progress (WIP) limits
A Definition of Done (DoD) primarily ensures that each increment is ______.
larger than the previous increment
estimated with perfect accuracy
releasable against agreed quality criteria
approved by every stakeholder by consensus
To avoid stalling, a proven release pattern is to ______.
merge long‑lived branches once per quarter
batch all testing at project end
delay releases until every stakeholder request fits
ship on a fixed train cadence and move scope between trains
Trunk‑based development reduces feature‑creep risk mainly by ______.
encouraging small, frequent integrations with short‑lived branches
enforcing multi‑month hardening phases
requiring manual merges only
forbidding feature flags
A practical policy to keep scope in check is a ______.
no documentation for scope decisions
formal change‑control gate with impact assessment
ad‑hoc approvals via chat reactions
silent backlog edits during sprints
Which flow metric directly shortens when WIP limits are respected?
CPC
story points per sprint must always rise
domain authority
cycle time
What’s a release‑safe way to include a contentious feature?
block the train until all debate ends
ship it to all users without telemetry
hide it behind a feature flag and ship dark
merge it untested on release day
A healthy DoD typically includes ______.
release notes after the quarter closes
manual regression only
brand‑new scope added mid‑sprint
automated tests, security checks, and documentation updates
To keep cadence after a high‑risk change, teams should ______.
use progressive delivery and monitor telemetry post‑release
freeze releases for the rest of the quarter
skip monitoring to avoid false alarms
increase WIP to catch up
Starter
You understand the anti‑patterns. Tighten WIP limits and make your policies and DoD explicit.
Solid
Nice. Now automate checks, measure flow metrics, and protect the release cadence.
Expert!
Superb. You’re using flow discipline and small batches to deliver without bloat.
