Project Lifecycle
Route the work
- Choose the collaboration mode: explore an unclear problem, start a chosen direction, or implement an agreed outcome.
- Identify the project stage separately: discovery, startup preparation, MVP, growth, stabilization, or maintenance.
- Select the deliverable most useful now, such as a problem statement, blueprint, prototype, code slice, test evidence, or release plan.
- Frame substantial work with current evidence, inferred problem, acceptance, actual risk, the smallest vertical slice, and explicit non-goals.
- Keep a small low-risk task to one sentence when that is enough to verify it.
Design Thinking bridge
- Empathize and define during exploration.
- Ideate while moving from exploration toward startup.
- Prototype while moving from startup toward implementation.
- Test during implementation, then route new evidence back when it changes the problem.
Vertical slice
- Complete one independently verifiable loop per cycle.
- Include UI, backend, data, tests, and docs only when the outcome needs them.
- Park unrelated discoveries instead of expanding the active slice.
- Return to exploration or startup when validation changes the problem or direction.