|
Creado por Charlotte P
hace casi 3 años
|
|
Pregunta | Respuesta |
What is the purpose of Story Decomposition? | Story Decomposition is used to make sure that requirements have the right level of detail and are aligned to desired outcomes. |
At what Horizons is Story Decomposition used? | Iterative Horizon (IH) & Delivery Horizon (DH) |
Story Decomposition starts with a broad context and ____ _____to multiple levels until eventually defining detailed ________ ___________for individual stories. | 1. drills down 2. acceptance criteria |
What is a good candidate for Story Decomposition? | Any story that is too large or insufficiently understood (breadth before depth). |
Elements of Story Decomposition? S ______ G______ M______ / _____________ S________ A_____________ C__________ | 1. Story Goals (Highest level of business requirements) 2. MMFs/Features (Logical grouping, often forming themes for single release) 3. Story (user story, job story, requirement) 4. Acceptance Criteria (Conditions of criteria to validate user story) |
STRENGTHS of Story Decomposition? | - Helps to avoid 'getting lost in the detail' or losing 'the big picture' - Can trace functionality back to original objectives - Breaking product into MMFs helps with release planning & provides visibility into the development |
WEAKNESSES of Story Decomposition? | - Need to have emphasis on 'just enough' & 'just in time' otherwise won't know when to stop decomposing - Should not be done based on process, procedure or architecture - should be done on what features are most valuable to the customer |
¿Quieres crear tus propias Fichas gratiscon GoConqr? Más información.