Modern Analyst Flashcards
Describe the life cycle of a user story?
User stories are used by agile methodologies to capture the functionality that a system or software should support.
IDENTIFICATION AND PRIORITISATION
At the beginning of a project user stories are identified and developed in a story writing workshop. Each story is sized and prioritised for the first time, creating a product backlog (release backlog). During the workshop the tam selects an iteration length (between 1-4 weeks) and also the rate they will be able to complete user stories (velocity).
SEGMENTATION AND SPRINT PLANNING
During the iteration planning process, the user stories contained in the product/release backlog are segmented into iterations or sprints. The user stories for the first sprint make up the sprint backlog.
ACCEPTANCE CRITERIA FOR TESTING
Once the first iteration is ready to kickoff, conversations begin for each user story between members of the agile team. The user stories get updated with detail of the conversation, captured in the form of acceptance tests.
UPDATING
The user stories can be updated at any point as needed up until the iteration coding has been completed.
HANDLING ISSUES
If a user story cannot be completed during the iteration for some unforeseen reason, it is returned back to the product backlog and rescheduled for another iteration.
THE END
Once the user story has been coded, typically the user story is discarded. It does not live on beyond the development process.
