Story Maps, User Stories
A typical phenomenon when working with user stories in agile projects is the loss of contextual knowledge. Splitting a user story into several smaller ones always means separating what once belonged together. This original context is then lost in the product backlog because it plays no role in the Scrum-typical further handling of the user stories.
Understanding the business processes and workflows is helpful overall in order to decide competently and comprehensibly which parts need to be newly developed and which should be done manually or by existing systems. Story maps are an effective and pragmatic tool for this.
More knowledge about story maps
Learn the technique of story maps in our seminars Agiles Requirements Engineering.
Interview with Marcus Winteroll in der CIO 'How Story Maps save Scrum-Projects"
More Knowledge about agiles Requirements Engineering.
Talk Produktgestaltung mit Story Maps form Marcus Winteroll.
Jeff Patton about Story Maps.
English
