State the transition, constraints, ownership, and evidence before commitment.
A deliberate alternative to LeSS
Less guessing.
Less guessing.
MoRE clarity.
MoRE (Modelling, Refinement, Execution) turns multi-team product intent into explicit, reviewable work through living contracts, reviewed delegates, and focused participation.
Prepared refinementStart with written context
Explicit readinessCommit with bounded uncertainty
Reviewed delegatesRepresentation without permanent authority
Fluid executionTeams choose how to collaborate
Why MoRE
Shared understanding does not scale by itself.
Coordination fails when scope lives in conversations, decisions depend on attendance, and implementation starts before teams agree on their seams.
Product Owners and delegates shape work so broader refinement starts from something challengeable.
Keep decisions written and let owners choose their internal workflow.
Fundamental ideas
Document understanding before committing.
MoRE makes important communication durable. Intent, assumptions, boundaries, decisions, and Evidence become a shared record instead of context that disappears after a meeting. The Contract remains living: explicit boundaries make learning and change visible without pretending requirements will remain unchanged.
Computational thinking
Decompose complex outcomes into understandable state transitions with explicit inputs, outputs, constraints, and acceptable Evidence.
Seams, Contracts, and Black Boxes
A Black Box hides how behaviour is produced, its Contract describes what others can rely on, and its Seams are the boundaries where it interacts with people, teams, or other systems.
Agile Manifesto
Use structure to support people, working results, customer collaboration, and responsiveness to change—not to defend documentation, Contracts, or plans for their own sake.
Adaptive Requirements
Treat requirements as learning that evolves through conversation, implementation, feedback, and use. A living Contract records current understanding without freezing it.
The lifecycle
One Work Item. Three phases.
Each item moves independently through three lifecycle states: Candidate Item, Ready Work Item, and Result. Planning records commitment before Execution, and a final Demo records the product decision before closure.
PO + delegates
Modelling
Turn product intent into a prepared Candidate Item with boundaries, reasoning, and provisional priority.
StateCandidate Item
PO + delegates; teams as needed
Refinement
Make the Contract strong enough for informed commitment while keeping uncertainty visible and bounded.
StateReady Work Item
Owning team or teams
Execution
Deliver, learn, seek useful feedback, and keep the living Contract aligned through the owners' chosen workflow.
StateResult
The MoRE Manifesto
Three challenges guide the framework.
How can teams maintain alignment while reducing unnecessary meetings and participation?
Explore the response →How can cross-team boundaries and dependencies evolve without surprises or excessive control, while teams retain implementation autonomy and shared accountability?
Explore the response →How can shared understanding survive beyond the people and meetings that produced it?
Explore the response →Scale the clarity, not the meeting.