33941093
Descripción
Fichas por Charlotte P, actualizado hace más de 1 año
|
Creado por Charlotte P
hace alrededor de 3 años
|
|
| Pregunta | Respuesta |
| What is the purpose of User Stories? | To convey the customer requirement to the delivery team. |
| User stories represent the customer ______ and are expressed as small, concise statements of a _________ needed to provide customer ______. | need feature value |
| Well written user stories follow the 'INVEST' Criteria. What does this stand for? I________ N_______ V_______ E________ S________ T________ | Independent (feature can be delivered independently) Negotiable (team can negotiate how to deliver) Valuable (expresses value to customer) Estimable (team can estimate effort to deliver) Sized Appropriately (smaller the better) Testable (validated objectively by stakeholder) |
| User Stories follow the 3 cards. These are? C________ C________ C________ | Card (title) Conversation (invokes conversation) Confirmation (confirm delivered item satisfies the need expressed in user story) |
| What is the format of User Stories? | As a <role> I need to <feature> So that <goal/value> |
| STRENGTHS of User Stories? | - Small, testable slices of functionality that facilitate delivery & customer feedback - Easily understood & learnt - Developed through elicitation techniques e.g. workshop - Invokes conversation for further exploration & decomposition - Collaborative technique - Can be supplemented with analysis models e.g. screen mockups, prototypes |
| WEAKNESSES of User Stories? | - Challenging to create if teams don't have all the information or detailed requirements available upfront - Too many user stories bloat the backlog - More user stories created through decomposition -must be organised & relevant - Can lose sight of vision & product roadmap if too focused on individual stories - Teams may overlook the 'why' by focusing on the 'what' |
¿Quieres crear tus propias Fichas gratiscon GoConqr? Más información.