|
Erstellt von Charlotte P
vor fast 3 Jahre
|
|
Frage | Antworten |
What is the purpose of Story Elaboration? | Story Elaboration is used to specify the detailed design and acceptance criteria needed to validate a working solution. |
At what Horizon is Story Elaboration used? | Delivery Horizon (DH) |
Story Elaboration is the ____________ _______ of story decomposition. | lowest level |
Story Elaboration is the process whereby the story is broken down into the pieces of ______. This facilities the elicitation of the _______ ____________ requirements. Story Elaboration is an ________ activity. | work most detailed ongoing |
How is wasted effort reduced? | By adopting a 'just in time', 'just enough' approach. |
What is Story Elaboration completed in preparation for? | A Planning Workshop |
Elements of Story Elaboration: E_____________ S_______ D___________ A_____________ C__________ A_______ O___________ E____________ O____________ | 1. Elicitation (draw forth requirements from stakeholders) 2. Story Decomposition 3. Acceptance Criteria (clarifies, adds or removes ac) 4. Additional Optional Elements (may identify tasks to complete in upcoming release) 5. Outcomes (result is shared understanding among shareholders of what is considered 'done' state for story) |
STRENGTHS of Story Elaboration? | - Reduces elicitation time & potentially less documentation - Elaborating requirements only when needed helps team to avoid rework (may change over time) - Keeps the team focused on the highest priority item |
WEAKNESSES of Story Elaboration? | - Incomplete elaboration may lead to too many or too few details for a story to be completed - Proper timing of elaboration can be difficult (too early wasteful, too late delays team) - Challenging to elicit the correct amount of detail |
Möchten Sie mit GoConqr kostenlos Ihre eigenen Karteikarten erstellen? Mehr erfahren.