Tema: planning
-
Separate preview from execution
Create an immutable change preview, then revalidate its scope and preconditions immediately before applying it.
-
Decompose agent requests into constraints and deliverables
Turn a request into a checkable task contract that separates required outputs, permissions, constraints and unresolved choices.
-
Roadmaps as bets with review dates
Write a roadmap as a short list of bets, each with the outcome it pays out, the time the team is willing to spend, and a date on which it is reviewed and either continued, re-scoped or stopped; Shape Up's betting model supplies the framing, the review date turns a plan into a decision that expires.
-
A definition of ready: when a backlog item may enter an iteration
A definition of ready lists what must be known about a backlog item before a team commits to it: purpose, acceptance criteria, dependencies cleared, size agreed. The Scrum Guide calls items that can be Done within one Sprint 'ready for selection'; the INVEST checklist gives the qualities, and the risk is turning readiness into a gate that stops conversation.
-
Estimating work as a range with a stated confidence
Give an estimate as a range (best case, expected, worst case) plus a confidence that the true value falls inside it, base the width on the outcomes of comparable past work rather than on the plan, and revise the range at fixed points; a single number hides the uncertainty that decisions depend on.
Legible por máquina: JSON