linear-planning

Project management in Linear is structured by organizing work into a hierarchy of Initiatives, Projects, and Issues. This framework separates work status tracking in Linear from design rationale stored in the repository, ensuring clear scope definition and efficient progress management.

Task dependencies in Linear are tracked using the blockedBy feature. This mechanism manages interdependencies between individual tasks and projects, allowing teams to visualize blocking relationships and sequence work items efficiently within the workflow.

To separate design rationale from task tracking in an agile workflow, maintain work status and progress in Linear while storing architectural knowledge and design documents in the repository. Link Linear issues to these repository documents for context.

Linear can be used for agile project planning to track work status, but specific design rationale and architectural knowledge should be stored in the repository. This clear separation of concerns prevents cluttering issues with dense design specifications.

To create a new project in Linear for an existing initiative, group the work under the parent Initiative, define the project scope, and break down the deliverables into individual Issues. Use naming conventions and link issues to relevant repository documents.

Linear project issues may not reflect the correct workflow status if specific naming conventions and status transitions are not followed. Adhere to the defined workflow management rules to ensure efficient progress tracking and accurate status updates.