Plan what to build
Tasks for this goal
- Scope a feature request into an issue
An issue that lists what would change, ready for planning.
- Add acceptance criteria to an issue
Acceptance criteria on the issue that match how your product works today.
- Split a large feature into smaller issues
Linked issues, one per part of the product.
- Size a request before planning
A rough size, with the parts of the product that would change.
- Compare two ways to build a feature
A recommendation, with the parts of the product the two options would change.
- Find backlog issues that are already done
Open issues your recent changes already handled, with links to those changes.
- Turn an idea into a spec
A spec with the problem, who has it, what to build, what to leave out and how you'll know it worked, plus open questions.
- Summarize customer interviews
The patterns ranked by how many customers mentioned them, with quotes, separating what they do today from what they want.
See one in action
Product
Acme
-
@devboxes three customers asked this month for invoices in English. can you file it for billing with what would need to change? want to bring it to planning
-
Looked at 3 sources - Searched invoice and reminder text
- Opened the formatting module
- Filed ENG-224 for billing
Filed
ENG-224 for billing. Invoice text and reminder emails are written in German only, but dates and amounts already go through one formatting module, so most of the work is translation. Linear ENG-224 Send invoices and reminders in English when the customer asks
Backlog Billing, Feature
Filed ENG-224
-
devboxes is working…