Stories that are vague or unclear lead to lost development time or incorrect deliverables. Ideal user stories are clear about the user audience, the action, and the purpose of the feature.
As an Analyst, when viewing the home page dashboard, entries should be listed in the date of descending order so that I can see the most recent entries first.
Sorting is not
in the correct order.
Discussion, comments, and - more importantly - decisions are communicated inside of the project management system so engineers and managers understand what is being done and why.
Stories are “pointed” out by level of challenge/difficulty by the team in the planning meeting. Stories that have a higher number of points are likely complex and should be broken into multiple smaller stories.
Bugs do not receive points because we are fixing something that was never working as intended. Stories that change existing functionality because a Product Manager was not clear or because we “changed our mind” receive points, because the developer successfully did what they were told. We are “spending additional points” because we made a change.
When stories are completed and approved by the team the team is awarded points towards their velocity. If a developer completes an item and it goes unreviewed, no points are awarded until it is approved.
It is critical that any developer actively contributing code to a product associates their pull requests with a feature or bug story. If one does not exist, it must be created. Most integration workflows are set up to not allow a developer to deploy without their PRs being associated with a story. This ensures every person involved in a product understands what is being contributed and what effect it should have on the product.