I work with companies that use Linear. Fundamentally it’s a todo list. Why can’t we do better?<p>User stories/features don’t have a binary finished state. Equating them with tasks makes no sense.<p>Tools should build on user stories and requirements instead of tasks.<p>Stories should be organized into phases of planning, working, review.<p>Stories should be organized into releases, and be part of multiple releases.<p>User stories and releases should be <i>separate</i> things. A feature isn’t “done” when it’s shipped. The context around a feature should be kept across iterations.<p>Anybody else feel the same way? Thoughts?
The question is: what is "better". Better for your workflow is not necessarily true in another context.<p>I agree with some of your points. But, IMHO, user stories are not the best tool to describe a feature. Even Linear don't advocate on User Stories: <a href="https://linear.app/method/write-issues-not-user-stories" rel="nofollow">https://linear.app/method/write-issues-not-user-stories</a><p>Either way, I see this as a build-your-own-workflow. Each company should try to find the best way to work. It's an iterative and empiric process.