Story Mapping

Descrição

IIBA Business Analysis Agile Business Analysis (Agile BA Techniques - Requirements Management) FlashCards sobre Story Mapping, criado por Charlotte P em 15-10-2021.
Charlotte P
FlashCards por Charlotte P, atualizado more than 1 year ago
Charlotte P
Criado por Charlotte P quase 3 anos atrás
1
0

Resumo de Recurso

Questão Responda
What is the purpose of Story Mapping? Story Mapping is used to create an understanding of product functionality, the flow of usage & to prioritise product delivery.
Story Mapping provides a _______ view of the _________ of __________ to be supported by the solution. visual sequence activities
Story Mapping uses a two-dimensional grid structure. Horizonal shows = Vertical shows = Horizonal shows the sequence & groupings of key aspects of the product. Vertical shows the detail & priorities of stories.
Story Mapping is an ‘_______ __________’ used to visualise a solutions outcome in the context of _____ & ______. Can be useful in identifying ____________ due to the intended flow through the user stories. 'information radiator' usage priority dependencies
What is shown on the top line of the Story Map? Themes/Activities a customer will follow in a linear path.
What is shown on the second line of the Story Map? Stories/Features that are related to the themes. May apply to more than one persona.
How are stories arranged on the Story Map? They are ranked in priority order (top-down) under each theme
Story Mapping is a s____ f___________ technique. self facilitation
What is prepared in advance of a Story Mapping session? Themes/Activities so that efforts can be spent on priortising & understanding the customer path.
STRENGTHS of Story Mapping? - Useful in avoiding 'getting lost in the detail' and loosing the 'big picture' - Include personas to help the team prioritise features based on most relevant to persona - Can be used to understand the intended flow of systems
WEAKNESSES of Story Mapping? - Can become cumbersome task when solution is too large & may need to create multiple story maps - Whilst maps show a flow, they do not analyse the dependencies between requirements - Contexts that are not process orientated will not be as useful

Semelhante

Story Decomposition
Charlotte P
Story Elaboration
Charlotte P
User Stories
Charlotte P
Spikes
Charlotte P
Minimum Viable Product (MVP)
Charlotte P
Behaviour Driven Development (BDD)
Charlotte P
Impact Mapping
Charlotte P
Planning Workshops
Charlotte P
Kano Analysis
Charlotte P
Job Stories
Charlotte P
Relative Estimation
Charlotte P