User Story Mapping for Beginners: Order Actions, Draw the Release Line, Build a Backlog

Project & Development

User Story Mapping for Beginners: Order Actions, Draw the Release Line, Build a Backlog

Solo developers and small teams whose feature lists keep growing use this user story mapping template for beginners to order actions left to right and lock in what ships first. Page 1 sets the user and pain point, page 2 lines up actions as activities, tasks, and stories, page 3 sorts them into release 1, release 2, or later, and page 4 copies release 1 into a backlog table. The task board has three columns - not started, in progress, and done - with four parent tasks matching the four pages and three subtasks each, all starting in not started. First-timers can rewrite the household-budget-app example for their own product to practice writing stories, cutting the release line, and building a backlog. Each story is one line - "As a ___, I want to ___, because ___" - sized with story points, co-edited with planners and designers in limited-visibility sharing, and shared with collaborators via a public URL once done.

0 Likes 0 Copies Author: WeProcess
user story mapping release planning backlog agile solo development
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode User Story Mapping for Beginners: Order Actions, Draw the Release Line, Build a Backlog

Whiteboard preview

① Before You Start (order and terms) ② The User (pick just one) ③ Their Pain Point ④ What to Check in Release 1 ⑥ Story Map (expand ⑤ with your own p... ⑦ The Story Template ⑧ A Good Example ⑨ A Story That's Too Big ⑩ Place ⑥'s Stories by Value × Effort High value × low effort High value × high effort Low value × low effort Low value × high effort ⑪ Release Cutoff Table (sort by row, ... ⑫ Can Release 1 Alone Carry You End t... ⑬ Backlog Table (what to build next, ... ⑭ How to Proceed (from ⑬ to the task ... User Story Mappin... How to use (4 pag... Goal / what's in ... Rules / how to wr... Blockers / gaps a... Learnings / what ... 1/4 Set the user and ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Line up the actions ↙ 3/4 Writing orderWrite page 1, then 2, then 3, then 4, in order.The "e.g." on each sticky note is from a budgeting-app example.Rewrite it in your own product's words. TermsActivity = a big chunk of behaviorTask = the steps inside itStory = one line: "As a ___, I want to ___" This map's briefProduct name: ____Target date for the first release: ____ e.g. an office worker tracking a budget for the first time e.g. uses it for just five minutes a day on a phone e.g. currently keeps no record of money at all Write the one person you most want to use it, not everyone e.g. runs short of money at the end of the month e.g. can't remember what the money went on e.g. installed a budgeting app and quit in three days Write when and where the trouble happens e.g. whether daily logging lasts a week e.g. whether seeing the total changes behavior Write how you'll check it too, e.g. have 10 people try it for a week Keep it to two or three items - this becomes the cutoff on page 3 ⑤ Sample Story Ma... e.g. Starting the app Task: e.g. sign up by email Story: e.g. As an office worker, I want to sign up in a minute, because a hassle makes me quit Story: e.g. As an office worker, I want to learn the app in three screens, because I want to start without confusion e.g. Logging a purchase Task: e.g. enter the amount and category Story: e.g. As an office worker, I want to just enter the amount and save, because I want to keep it up daily Story: e.g. As an office worker, I want to snap a photo of the receipt, because typing is a hassle e.g. Reviewing spending Task: e.g. check the monthly total Story: e.g. As an office worker, I want to see this month's total, because I'm worried about overspending Story: e.g. As an office worker, I want to see the share by category, because I want to find where to cut back Action 1 (left = ... Action 2 Action 3 Action 4 (right =... Activity e.g. Starting the app e.g. Logging a purchase e.g. Reviewing spending e.g. Setting and keeping a budget Task e.g. Sign up by email e.g. Enter the amount and category e.g. Check the monthly total e.g. Enter the monthly budget Story (top row) e.g. I want to sign up in a minute, because a hassle makes me quit e.g. I want to just enter the amount and save, because I want to keep it up daily e.g. I want to see this month's total, because I'm worried about overspending e.g. I want to see what's left of the budget, because I don't want to struggle at month end Story (middle row) e.g. I want to learn the app in three screens e.g. I want to snap a photo of the receipt e.g. I want to see the share by category e.g. I want a warning when I overspend Story (bottom row) e.g. I want to use it with my family e.g. I want to import bank statements e.g. I want to compare with the same month last year e.g. I want to set a savings goal Write one line: "As a ___, I want to ___, because ___" ___ (who) = the user you wrote in ② ___ (why) = what they gain, or which pain point shrinks e.g. As an office worker, I want to just enter the amount and save, because I want to keep it up daily Sized to finish in one screen or one action You can tell whether it's done e.g. As an office worker, I want to manage all my money Takes days, and means different things to different people How to split it: e.g. break it into logging, totals, and budget stories 3/4 Scope the first r... → 4/4 4/4 Move into the bac... 縦軸: Value to the ... The top pick for release 1, e.g. just enter and save the amount. Start release 1 in ⑪ from here. Split into smaller stories and take only the must-have part into release 1, e.g. swap receipt scanning for manual entry. A release 2 candidate. Add it once release 1 works end to end, e.g. the share by category. Leave it for later, and revisit if users ask for it, e.g. importing bank statements. Action 1 Action 2 Action 3 Action 4 Release 1 e.g. Sign up by email e.g. Enter and save just the amount e.g. See this month's total e.g. See what's left of the budget Release 2 e.g. Explain the app in three screens e.g. Scan and enter a receipt e.g. See the share by category e.g. Overspending alert Later e.g. Use it with the family e.g. Import bank statements e.g. Compare with last year's same month e.g. Set a savings goal Read it straight throughRead release 1 in ⑪ from action 1 to action 4.e.g. sign up → enter the amount → see the total → see what's leftPass if that covers one month. A missing actionList any action left empty in release 1.e.g. if action 4 is empty, pull "see what's left of the budget"into release 1 in a lower-effort form. Does it answer ④?Can release 1 measure what you wrote to check in ④?e.g. "does daily logging last a week" can be measured. Story to add as a... Done means Size (story points) Which release Action 1 e.g. Can sign up in a minute e.g. Signup finishes with just an email address e.g. 2 e.g. Release 1 Action 2 e.g. Can save with just the amount e.g. Can save in three taps e.g. 3 e.g. Release 1 Action 3 e.g. Can see this month's total e.g. The total shows first when opened e.g. 2 e.g. Release 1 Action 4 e.g. Can see what's left of the budget e.g. Entering a budget shows what's left e.g. 3 e.g. Release 1 Later e.g. Use it with the family e.g. Decide after release 1 ships e.g. Not decided yet e.g. Later 1 WriteWrite the backlog tableAdd one row per action to ⑬, with the story to add as a child and what done means. 2 MatchMatch it to subtasksAdd each row of ⑬ as a subtask, one at a time, and compare against ⑬ to catch gaps. 3 SetSet priority and pointsGive higher-row stories higher priority. Points are a rough size (compare using 1, 2, 3, 5). 4 MoveMove across columnsMove subtasks through not started → in progress → done. Aim for at most two in progress per person. 5 ReviewReview the map after releaseWatch how users respond, fix ⑥ and ⑪, and set the scope for the next release. Share the finished map with collaborators via a public URL. → 2/4 Line up the actions ↙ 3/4 Scope the first r... → 4/4 Move into the bac...
100%

Drag to move, scroll to zoom

Task board contents

Not started 16 items

Set user and goal
Line up actions
Scope release 1
Move to backlog
Write user and pain
Write what to check
Practice the sample
Add actions, tasks
Write out stories
Split big stories
Plot value & effort
Sort into releases
Check end to end
Copy to backlog
Move via subtasks
Review after launch

In progress 0 items

Done 0 items

← Back to templates