Path 07 · 8 lessons · 89 min
Put Taiga to work
Eight practical scenarios: start a product, bring existing code, shape work, review evidence, and handle the moments that need you.
- 01
Start a new product in Taiga
Prepare a bounded product, establish its context, and connect planning to your actual repository and environments.
- 02
Bring an existing codebase into Taiga
Review what Taiga derives from a repository. Separate current behavior from intended behavior and select the right response to an inaccurate document.
- 03
Review Discovery as a connected document set
Trace a requirement through the specification, architecture, data flow, and security documents. Handle revisions before planning depends on stale assumptions.
- 04
Turn an outcome into an initiative
Write intent that can become reviewable work. Inspect scope and dependencies before placing an initiative in the execution queue.
- 05
Choose where Taiga waits for a decision
Separate plan approval, build execution, merge permission, and deployment. Configure autonomy around the decisions your organization must retain.
- 06
Review a Taiga delivery with evidence
Connect the initiative, plan, run, diff, and checks. Verify the current change before accepting a merge or release decision.
- 07
Resolve a Needs you interruption
Diagnose why an initiative stopped. Choose continuation, replanning, restart, or a human setup action without losing the decision context.
- 08
Enable Taiga with a complete responsibility model
Connect business ownership, policies, platform boundaries, delivery controls, and ongoing operation before expanding use across products.