Project Management
Backlog management, iteration planning, dependency tracking, and retrospectives.
Overview
Datarim provides a complete project management workflow: maintain a backlog, plan iterations, track dependencies, execute tasks, and run retrospectives. Each task in the backlog can follow its own mini-pipeline, while the overall project follows a higher-level iteration cycle. The framework's backlog management commands make it natural to pick the next task, track progress, and archive completed work without switching to external tools.
Example: Plan and Execute a Product Launch
A team is preparing a product launch that spans marketing materials, a landing page, press kit, demo video, and partner outreach. The work is multi-phase and requires careful dependency management across workstreams.
Pipeline Walkthrough
| Stage | What happens |
|---|---|
| /dr-init | Create project backlog with all launch tasks. Complexity: L4 (multi-phase) |
| /dr-prd | Launch requirements: marketing materials, landing page, press kit, demo video, partner outreach |
| /dr-plan | Work breakdown: 4 phases over 6 weeks. Dependencies mapped. Critical path identified |
| /dr-do | Execute tasks from backlog one by one. Each task follows its own mini-pipeline |
| /dr-qa | Per-task quality check. Cross-task consistency review (branding, messaging, dates) |
| /dr-archive (Step 0.5) | Sprint retrospective: what slipped, what was overscoped, what to adjust for next iteration |
| /dr-archive | Archive phase, carry forward incomplete items to next phase backlog |
Backlog management is central to this use case. Use /dr-init to pick the next task, /dr-status to see pending items and priorities, and /dr-archive to complete tasks and update the backlog automatically.
Key Benefits
- Integrated backlog — no need for external tools; the backlog lives alongside the work and updates automatically on archive
- Nested pipelines — each task in the backlog runs its own pipeline, while the project follows a higher-level iteration cycle
- Dependency visibility — the planning stage maps dependencies and identifies the critical path before execution begins
- Built-in retrospectives — the reflect stage captures lessons at both task and phase levels
- Automatic carry-forward — incomplete items are moved to the next phase backlog during archive, nothing gets lost
Relevant Agents
Which agents are most active in this use case:
- Planner — backlog management, task prioritization, dependency mapping
- Strategist — phase planning, risk assessment, critical path analysis
- Reviewer — cross-task consistency and quality verification
Complexity Routing
How complexity levels apply to project management:
- L1 — Reprioritize a few backlog items or update task statuses
- L2 — Plan a single sprint with 5-10 tasks and basic dependencies
- L3 — Multi-phase project with cross-team dependencies and milestone tracking
- L4 — Full product launch with 4+ workstreams, external partners, and 6-week timeline