Toolkit for writing, refining, and prioritizing tickets on issue-tracking systems (Jira and equivalents). Covers three concerns: writing clear acceptance criteria for user stories; applying MoSCoW prioritization to requirements and backlogs; and readying sparse backlog tickets for refinement by gathering incident context, applying a YAML template, and generating a validated structured document.
93
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Use this guide after initial categorization.
Must: 50-60% effortShould: 20-30% effortCould: 10-20% effortWon't: explicit exclusionsMust > 60%, downgrade lowest-impact Must items.Could is empty, force explicit enhancement candidates.Won't is empty, add at least 3 deferred items.Must to Should to protect launch date.Should to Could when staffing drops.Could to Won't when demand is low.Review the final mix with stakeholders and capture sign-off date.