33927784
Beschreibung
Karteikarten von Charlotte P, aktualisiert more than 1 year ago
|
Erstellt von Charlotte P
vor etwa 3 Jahre
|
|
| Frage | Antworten |
| Purpose of Job Stories? | Job Stories represent a PBI (Product Backlog Item) & represent the jobs to be done by the stakeholder. |
| Why is it important for job stories to provide as much contextual information as possible? | To help make the right implementation decisions - helps to communicate, interact & focus on consumer needs. |
| Job Stories can be written in _______ or _______ person. | 1. first 2. third |
| The format for writing job stories is as follows: W________ I_________ S_________ | When I want to So I can |
| When <s_________> I want to <m________> So I can <e__________> | |
| Situation provides? | Context for when the job needs to be completed |
| Motivation focuses on? | Customer motivation (internal/external forces) |
| Expected Outcomes should? | Satisfy the or alleviate the movitation. |
| STRENGTHS of Job Stories? | - Removes personas bias - Can be set up for cause or effect scenarios - Focuses on stakeholder motivations - Helpful in User Experience design - Removes focus on features, instead focusing on the stakeholders desired outcomes - Can be combined with user stories in the backlog |
| WEAKNESSES of Job Stories? | - More verbose than user stories (waffling) - Job Stories can decompose into smaller job stories that need to be refined & prioritised - Can be confusing for teams if they have to switch between user/job stories format in the backlog |
Möchten Sie mit GoConqr kostenlos Ihre eigenen Karteikarten erstellen? Mehr erfahren.