Most large companies can’t drop their gate reviews overnight, and most shouldn’t try. Gates exist because executives need to decide where to put money, and that need doesn’t go away when a team starts using Scrum. The good news is that the two can coexist. The trick is translating what agile teams produce into what the gate committee needs to see.

Start with what a gate is for

A gate is a decision point: continue, change, or stop. Gate reviews often ask for documents because documents were once the only evidence available. Working software, a stable velocity, and a prioritized backlog are better evidence of progress. Your job is to present that evidence in terms the committee understands.

Consider a manufacturer building an internal ordering application under a standard five-gate process. The team works in two-week sprints. At each gate, the project manager doesn’t need to produce a new set of artifacts. She needs to map what the team already has.

What to show at each gate

• Early gates (concept and business case): a vision statement, an initial backlog sorted by value, and a rough estimate range. Be honest that it’s a range.
• Middle gates (development): a demonstration of working software, the release plan, the burndown for the current release, and the top risks.
• Late gates (readiness and launch): test results from the last several sprints, the remaining backlog, and the operational plan.

Notice that each item comes from the team’s normal work. If you’re building extra paperwork to satisfy the gate, you’re doing it wrong.

Where friction appears

Expect three trouble spots. First, gates that want a fixed scope and date, but the team wants to trade scope for time. Agree early that the date and budget hold and the scope is the flexible part, and get that written into the business case. Second, gates that require a complete requirements document before development starts. Negotiate a lighter version, such as a prioritized list of themes with detail added shortly before each sprint. Third, committees that read a changing backlog as scope creep. Explain the difference between adding work and learning what the work is.

Teams also struggle when the gate calendar is out of step with the sprint calendar. Schedule reviews right after a sprint review so the demonstration is fresh.

Build trust gradually

The committee will relax as it sees a pattern: gate after gate, the evidence is real and the surprises are fewer. Over time, you can propose fewer documents and more demonstrations. That change should come from the governance group, not from the team, so give them the chance to arrive there.

Before your next review, list every artifact the gate requires and mark which ones your team already produces in another form. The unmarked ones are your negotiation list.