Balance disciplined decisions with fast learning by adapting gate rigor to project risk. This quiz probes hybrid practices, evidence, and anti‑patterns that affect cycle time.
What is the primary decision purpose of a Gate in Stage‑Gate governance?
Approve budgets for all future stages automatically
Lock scope so it cannot change later
Assign code tasks to developers
Make go/kill/hold/recycle calls based on predefined criteria and evidence
A modern way to increase speed without losing control is to ______.
remove all gates after ideation
tailor gates by risk and blend Agile execution with Stage‑Gate checkpoints
outsource gate reviews to a single functional lead
skip user validation until after launch
Which governance anti‑pattern most often slows time‑to‑market?
Running customer tests before development
Time‑boxed experiments between gates
Using lightweight checklists for low‑risk projects
Demanding near‑perfect information at each gate before any progress
What should change as uncertainty falls during development?
Stakeholders stop attending gate meetings
Gate criteria become looser over time
Only financial metrics are kept; user evidence is dropped
The evidence burden increases while gate cadence can space out
Which artifact is most useful for a gatekeeper board to balance speed and rigor?
A press release with no metrics
Unbounded backlogs without prioritization
A concise risk‑based checklist mapping proofs to the gate decision
A full technical design for all future features
What digital capability is repeatedly cited as improving Stage‑Gate throughput?
Portfolio/project systems that give real‑time visibility and automate workflows
Banning any automation around gates
Restricting dashboards to finance only
Gate minutes recorded solely in spreadsheets
In a hybrid approach, where does Agile typically operate?
Outside the process entirely
Only after launch for maintenance
At the gates only, replacing decisions with stand‑ups
Within stages to deliver increments, with gates used for investment decisions
Which option best describes a healthy gate meeting?
Approvals contingent on future undefined work
Single‑function vetoes based on opinion
Endless debates with no recorded decision
Cross‑functional reviewers apply clear criteria and make timely decisions with action items
When should teams lean toward lighter gates?
Whenever deadlines are tight regardless of risk
For first‑in‑class launches with heavy uncertainty
For lower‑risk or incremental releases with strong precedent evidence
When the team prefers to avoid documentation
Which set of gate outcomes is valid in the Stage‑Gate method?
Only Go or Kill
Go, Kill, Hold, or Recycle with clear conditions
Promote or Demote the team
Auto‑Go if the meeting times out
Starter
You know the basics of gates; tighten your risk‑based tailoring and decision focus to gain speed.
Solid
Good grasp of hybrid governance; refine your checklists, cadence, and board behaviors.
Expert!
You balance speed and rigor with risk‑scaled gates, crisp decisions, and digital visibility.
