From 84466854f5212385d33c0a3a67b3ec904d6fc764 Mon Sep 17 00:00:00 2001 From: tgaff Date: Thu, 14 Mar 2024 07:35:59 +0900 Subject: [PATCH] fix broken link As reported by CI, this link was broken sometime in the last couple PRs. Fixing. --- product_design/how_we_write_user_stories.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_design/how_we_write_user_stories.md b/product_design/how_we_write_user_stories.md index b36728c..0d2117e 100644 --- a/product_design/how_we_write_user_stories.md +++ b/product_design/how_we_write_user_stories.md @@ -47,7 +47,7 @@ When the Designer has enough context on the problem (from the speclet and discov Product Manager creates the Epic(s) and possibly shell user story tickets in Jira. Follow [this guidance](../product_design/structuring_epics_stories_bugs_and_tasks.md#epics) on epics.
4. **Add User Stories to the Epic**
-When designs are agreed on, the Designer prepares the designs for handoff and [writes detailed user stories based on the designs](../product_design/structuring_epics_stories_bugs_and_tasks.md##user-stories). *If the epic doesn’t have a user interface, it may be more appropriate for the Lead Engineer to write the user stories.*
+When designs are agreed on, the Designer prepares the designs for handoff and [writes detailed user stories based on the designs](../product_design/structuring_epics_stories_bugs_and_tasks.md#user-stories). *If the epic doesn’t have a user interface, it may be more appropriate for the Lead Engineer to write the user stories.*
5. **Preview stories**
The Product Manager, Designer, and Lead Engineer review all stories before Storytime and estimation.
6. **Initial prioritization**