Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix broken link #114

Merged
merged 1 commit into from
Mar 13, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion product_design/how_we_write_user_stories.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.<br>
4. **Add User Stories to the Epic**<br>
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.*<br>
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.*<br>
5. **Preview stories**<br>
The Product Manager, Designer, and Lead Engineer review all stories before Storytime and estimation.<br>
6. **Initial prioritization**<br>
Expand Down
Loading