Sprints & Planning
Sprints are time-boxed work cycles with a defined scope. Tulsk’s sprint system tracks velocity, scope drift, and auto-generates retrospectives.
Creating a Sprint
From a project, open the Sprint tab and click Start Sprint. Configure:
- Name — e.g. “Sprint 12” or “Launch Week.”
- Start & end dates — the time box.
- Goal — a one-liner describing what “success” looks like.
- Initial tasks — tasks pulled from the backlog.
Ema can plan a sprint for you: “Plan a 2-week sprint for the Website Redesign project focused on the nav refactor.” She’ll pick tasks from the backlog, estimate velocity, and surface risks.
Sprint Statuses
| Status | Meaning |
|---|---|
| PLANNING | Scope being defined; not yet started. |
| ACTIVE | In flight — tasks are being worked on. |
| COMPLETED | Sprint closed; retro generated. |
Only one sprint per project can be ACTIVE at a time.
Velocity Tracking
Velocity is the count of Completed tasks per sprint (weighted by priority if configured). It’s displayed on:
Velocity chart over the last 6 sprints.
📊Ema DashboardCurrent-sprint velocity vs. historical average.
📁Project ViewAuto-generated retro at sprint close compares actual vs. planned.
🔄RetrospectivesScope Drift
When a task is added or removed from the sprint mid-flight, Ema’s scope tracker records the change. At retro time, you’ll see:
- Tasks added after sprint start (scope creep).
- Tasks removed (descoped).
- Tasks deferred (pushed to next sprint).
High scope drift triggers a Ema warning and factors into the project health score.
Work Breakdown Structure (WBS)
For complex initiatives, ask Ema to generate a WBS:
“Generate a WBS for the mobile launch project.”
Ema creates a parent task plus subtasks with dependencies wired up, assigns them to the right agents based on skills, and drops them into the current sprint. Edit as needed — it’s a starting point, not a commitment.
Task Dependencies & Blockers
Dependencies wired between tasks (see Tasks → Dependencies) show up in the sprint view as a DAG. Blocked tasks are styled differently so planners know what’s actually ready to pick up.
A sprint can end with blocked tasks still In Progress. Ema’s retro will flag these and suggest whether to roll them or rethink the dependency.
Closing a Sprint
Close the sprint from the Sprint tab. Ema automatically:
- Calculates final velocity.
- Lists completed vs. rolled tasks.
- Generates a retrospective with action items.
- Creates follow-up tasks for each action item in the next sprint.
- Posts the retro to the project and to the PM chat.
See Ema → Scheduled Reports if you want a recurring sprint summary on top of the auto-retro.