Write issues not user stories - Linear Method
linear.app · 956 words · saved by 1 readers
At Linear, we don’t write user stories and think they’re an anti-pattern in product development. Here's how we write issues instead.
Method Building Write issues not user stories At Linear, we don’t write user stories and think they’re an anti-pattern in product development. We write short and simple issues that describe the task in plain language instead. The point of writing an issue is to communicate a task. It needs to be clear enough so that the assignee can perform it and also give enough context so that teammates who need to know understand what work is being done. So the goal when writing issues should be to do this as effectively and quickly as possible. Why user stories are obsolete User stories evolved over twe
related reading
- How to Write a User Story: Guide with Examples and Templatesstormotion.io
- BA viết User Story? - Thinhnotesthinhnotes.com
- How Linear builds product - by Lenny Rachitskylennysnewsletter.com
- Issue tracking is dead – Linearlinear.app
- How I've run major projects | benkuhn.netbenkuhn.net
- Building at the early stagelinear.app
- Now – Updates from the Linear teamlinear.app
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- Manage design projects - Linear Methodlinear.app
- How Stripe Built a Writing Culture - Knock Down Silos by Slabslab.com
- A better way to build software - by Sar Haribhaktisarharibhakti.substack.com
- Linear: Designing for the Developers | Sequoia Capitalsequoiacap.com