A citizen self-service portal needs an identity-integration enabler before several journeys can ship. Low-value brochure pages are also waiting. How should the backlog be ordered?
Select an answer to reveal the explanation.
Short Explanation
Sometimes the on-ramp matters more than the gift shop. An identity enabler that unlocks many citizen journeys can beat a stack of pretty brochure pages. Value includes what you unblock next, not only what’s flashy today.
Full Explanation
When a citizen self-service portal needs an identity-integration enabler before several journeys can ship, while low-value brochure pages also wait, the backlog should prioritize the enabler story that unlocks multiple citizen journeys ahead of low-value brochure pages. Enablers that unlock value streams often outrank easily demoed but low-value cosmetics in adaptive ordering for municipal portals serving many services.
Always ranking brochure pages first because they are easier to demo at council meetings fails conceptually because demo ease is not the same as citizen journey value. Rejecting all enablers because adaptive teams never build technical foundations fails because adaptive backlogs routinely include enablers that unlock delivery of multiple features. Scheduling enablers only after every cosmetic page is live in production fails by delaying the foundation that multiple journeys depend on.
Exam caveat: Value-unlocking enablers can and should outrank low-value brochure work when they gate multiple civic journeys. Operational check: place identity integration above brochure pages, show leadership which journeys it unlocks, and demo enabler progress with a thin vertical slice when possible so sponsors see progress without waiting for cosmetics.