Story Mapping
Outlining a new product or a new feature for an existing product uses a user story mapping approach. Story Mapping's primary goals are to make product discovery and the prioritizing of development work easier. You do this by placing user tasks and activities on a map that helps to keep them easily interpretable. This method can be done by the Product owner or the manager. The working process of doing this is simple:
1. Begin with the Large Tasks. - Determine the major stories and extensive user interactions that your program should function.
2. Organize the Smaller Tasks. - Divide the story of each user task, or action, into smaller stories.
3. Put the tasks in line. – Group the smaller tasks with the large tasks. The priority of the tasks is divided into 5 groups. Epic is the biggest task followed by product backlog items and feature, bug or just a task is the smallest.
Last updated
