|
1 | 1 | --- |
2 | 2 | title: User Stories |
3 | | -seoTitle: How to Write Effective User Stories |
4 | | -summary: How to write effective User Stories |
| 3 | +seoTitle: How to Actually Write Effective User Stories |
| 4 | +summary: How to actually write effective User Stories |
5 | 5 | isReleased: true |
6 | 6 | isSequel: false |
7 | 7 | lastModDate: 2023-06-14T09:15:00-0401 |
@@ -32,7 +32,7 @@ An effective user story should adhere to the <L href='https://www.agilealliance. |
32 | 32 | </C> |
33 | 33 |
|
34 | 34 | <C> |
35 | | - **Independent:** User stories should be self-contained and independent, to enable teams to develop and deliver them without reliance on other stories. |
| 35 | + **Independent:** User stories should be self-contained and independent, to enable developemnt and delivery without reliance on other stories. |
36 | 36 | </C> |
37 | 37 |
|
38 | 38 |
|
@@ -85,14 +85,14 @@ An effective user story should adhere to the <L href='https://www.agilealliance. |
85 | 85 |
|
86 | 86 |
|
87 | 87 | <C> |
88 | | -**Remove Technical Details If not needed:** Separate user goals from implementation specifics to maintain relevance and flexibility. Should the user get notified by Kafka or a web hook? Does it really matter? The user just wants to get notified, using either technology won't matter, in the end. But will it matter if the user receives the notification through email or other means? Yes. |
| 88 | +**Remove Technical Details If not needed:** Separate user goals from implementation specifics to maintain relevance and flexibility. Should the user get notified by Kafka or a web hook? Does it really matter? The user just wants to get notified, using either technology won't matter, in the end. But will it matter for the user if they receives the notification through email or other means? Yes. |
89 | 89 | </C> |
90 | 90 |
|
91 | 91 |
|
92 | 92 |
|
93 | 93 |
|
94 | 94 | <C> |
95 | | -**Clarifying Roles:** Yes it's called User Story but, not everyone is a user. Tailor user stories to specific user roles (e.g., manager, admin, architect, <L href='https://www.urbandictionary.com/define.php?term=group%20leader'>group leader?</L> to ensure features meet diverse user needs. |
| 95 | +**Clarifying Roles:** Yes, it's called User Story but, not everyone is a user. Tailor user stories to specific user roles (e.g., manager, admin, architect, <L href='https://www.urbandictionary.com/define.php?term=group%20leader'>group leader?</L> to ensure features meet diverse user needs. |
96 | 96 | </C> |
97 | 97 |
|
98 | 98 | <H2>Good and Bad User Story Examples</H2> |
@@ -139,7 +139,7 @@ You might find these ones in the wild |
139 | 139 | </C> |
140 | 140 | <H2 id='testability'>Testability</H2> |
141 | 141 | <C> |
142 | | -Rewrite user stories using Behavior-Driven Development format, such as <L href='https://cucumber.io/docs/gherkin/reference/'>Gherkin</L> syntax, so you can directly map these stories to executable tests, and ensure that the software meets the specified requirements and behaviors. |
| 142 | +Rewrite user stories using Behavior-Driven Development (<L href='https://www.agilealliance.org/glossary/bdd/'>BDD</L>) format, such as <L href='https://cucumber.io/docs/gherkin/reference/'>Gherkin</L> syntax, so you can directly map these stories to executable tests, and ensure that the software meets the specified requirements and behaviors. |
143 | 143 | </C> |
144 | 144 | <H2>Gherkin Syntax</H2> |
145 | 145 |
|
|
0 commit comments