Task Management (Linear)

Overview

• Velocity (story points completed each cycle Tue-Mon) on each Linear team helps business better plan ahead.
  • Each story should be estimated by the team on the Fibonacci scale (0/½/⅗/8) based on difficulty.
  • As a baseline, a day of work would be 3 points.
  • If more than 5 points, the story should be broken into sub issues.
  • 0 points for bugs and parent issues.
  • Individual velocity target is 15 points/person/week.
• Each story should only have one owner.
• Add description, tasks, blockers, and comments as needed.

Story States

• In Progress when you begin working on the story.
  • Select stories in related epics/labels to maintain domain expertise and consistency.
  • Only start one story at a time, unless they're part of the same feature.
• Finished when you finish working on the story and submit the Pull Request.
• Delivered when the PR gets deployed to review app.
• PM/QA will mark the story as Accepted (and merge PR to dev) or provide feedback.
• Deployed when it is in production.

Best Practices

• Focus on one story at a time
• Break down large stories (>5 points) into smaller sub-issues
• Use descriptive titles and detailed descriptions
• Add blockers and dependencies clearly
• Update story status regularly
• Use labels and epics for organization