Turn CAB themes into MoSCoW priorities
Apply MoSCoW prioritization to CAB themes using viability, pain, workaround, and timing criteria.
The CAB produced seven themes for Q4 enterprise adoption. The team needs a priority set that protects viability without promising every customer request. MoSCoW: Must Have, Should Have, Could Have, Won't Have this time Treating every painful customer comment as a Must creates a fake priority list and removes the contingency that makes delivery credible. Define the timebox Set the priority horizon as Q4 enterprise adoption, not the entire product vision. MoSCoW priorities only make sense against a timeframe. A future Must may be a Won't for this increment. Test viability Ask whether enterprise launch would fail without each theme.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in