Tips and user stories for the four types of requirements.
A quick look at user stories, and epics, their purpose and format.
The second in the Backlog management Rock Crusher series outlining meetings and sizing.
Third in the Backlog management Rock Crusher series discussing tools including the Kanban Board for single or multiple teams.
Continuing the Rock Crusher metaphor to discuss problems with backlog owner, multiple backlogs, misunderstanding agility, and no definition of ready.
Follow these steps to run a virtual workshop to create a customer journey map.
To assess business analysis work and to plan to improve processes where required.
To draw out, explore, and identify information relevant to the change.
To check the information gathered during an elicitation session for accuracy and consistency with other information.
To obtain approval of requirements and designs to continue with subsequent activities.