Why user story mapping?

The transformation of the flat backlog to a customer-centric story map means teams have a better understanding of their customer journey and what customers want.
Work can be prioritised based on customer needs rather than a flat backlog or to-do list.
For more information about Atlassian training and certification, please visit: www.atlassian.com/university

[@surfviewgardens2396]

This looks interesting. Do the sticky-notes align with the Event Storming process of Alberto Brandolini?

[@siddharthseksaria6302]

What should we do in case of Back-end/Micro-service oriented project? How do we build story map and user stories that are backend centric?

[@jimiwikmanofficial]

Then you can use a system map, but more likely you will have independent components matching your micoservices and integrations.

[@impropiano4962]

'No phones/laptops' - Proceeds to show an image with laptops on table :))

[@EasyAgile]

You got us!

[@miriammulders2341]

How does the definition of the User Story itself fit in? I mean: when is the famous phrase 'As a user, I ....' specified, and the acceptance criteria? Is it part of the User Story Mapping process or is it separate?

[@krccmsitp2884]

Look at the section from 02:34 on.

[@jimiwikmanofficial]

It is very useful, but not for developers. Developers work across customer journeys because the technonlogy is not confined to the steps a user takes. Things like login, product presentations and pretty much all user information exist in multiple places in the customer journey. Things like calculations, taxes and integrations will never fit into a customer journey either, because they are not a part of the customer experience in that way. Story mapping is awesome for requirements and to visualize work for management. It is rarely useful for frontend developers and it makes no sense to backend development or operations.

[@s.z.9579]

‚Hidden features‘ or backend issues contribute to the customer journey as well, often rather indirectly. They enable a convincing user experience ‚on the surface‘. Thus, they can be prioritized on the map too. What experience do they make possible?

[@krccmsitp2884]

This is not about customer journeys.

[@jimiwikmanofficial]

@@krccmsitp2884 This....as in what? The video or the responses?

[@krccmsitp2884]

@@jimiwikmanofficial user story mapping is not about customer journeys

[@jimiwikmanofficial]

@@krccmsitp2884 What do you map against when you do Story mapping at the operational level then? Business processes works for strategic story mapping, but this video is for operational level for the teams... So what would you map against then?

[@user-xg4fk7by1b]

it which black KZbin and google play code dealer bad control me

[@user-ke1in5cf8u]

Переведите на русский