Backlog, Sprint and User Stories / Tickets

This page shows all challenges and their respective Best Practices related to the Backlog, Sprint and User Stories / Tickets

Index Challenge Best Practice
(1) Quality related Tickets are neglected due to short deadlines [1, p. 5, 2, p. 2] Every team member owns the quality of the produced code [3, p. 294]
(2) Insufficiently defined tasks [4, p. 91, 1, p. 5] A User Story should be independent, negotiable, valuable, estimable, small and testable [5, p. 700]
(3) Having an inadequate Product Backlog [6, p. 200, 2, p. 2, 7, 8] Order your Backlog by the highest business impact or use other prioritisation techniques [9, 10, 11]
Offer the team some freedom in letting them create their own process of managing the product Backlog [7]
Create unique identifiers for each Backlog Item [9, 10]
Establish meetings to groom your Backlog every two weeks to maintain your clean / up-to-date Backlog. [12] There, the topmost User Stories of the Backlog will be structured using the value of each item [16, p. 200]
Prepare your Backlog with stakeholders [10]
(4) Having multiple (unstructured) Backlogs [13, p. 83] Use only one prioritised Product Backlog [13, p. 83]
Use only one Sprint Backlog, which ought to be separate from the Product Backlog [14, 9, 10, 13, p. 83]
Create unique identifiers for each Backlog Item [9, 10]
(5) Introducing new requirements or changes to a running Sprint [6, p. 201, 15, p. 11 | 66, 16, p. 163] Rather change scope during a Sprint and with a positive attitude to change, than after the Sprint [15, p. 11]
Analyse team performance with different Sprint lengths and apply the best one to your process [6, p. 201]
Communicate the impact of changes within a Sprint to your customer [15, p. 11]
Meet with the responsible Product Owner and assess the team’s state. After taking the state into account, set the direction and timely details for the new Sprint Planning [15, p. 67]
(6) Software bugs are not being fixed enough or take up too much time within the Sprint [17] Hold sophisticated triage meetings to determine on the share of new tickets to bug fixes [17]
Define the bugs priority through a combination of severity, significance and risk (e.g. project delay) [17]
Every team member owns the quality of the produced code [3, p. 294]
(7) Unsuitable Sprint length [6, p. 201, 15, p. 64, 2, p. 2, 7] Analyse team performance with different Sprint lengths over the course of a few months and apply the one best suited for your process or try iterating to the best Sprint length [6, p. 201]
Let the Scrum Master advocate in favour of lesser Sprint lengths in front of the team [15, p. 64]
The Scrum Master may decide upon the Sprint length given the Scrum Master has extensive experience [7]Offer the team some freedom in letting them create their own process of managing the product Backlog [51]
Create unique identifiers for each Backlog Item [9, 10]
Establish meetings to groom your Backlog every two weeks to maintain your clean / up-to-date Backlog. [12] There, the topmost User Stories of the Backlog will be structured using the value of each item [16, p. 200]
Prepare your Backlog with stakeholders [10]
(8) The team is going to take shorter than anticipated to finish all tasks they committed to [9] Do not deflate your remaining Sprint time [9, 10]
Pull new User Stories into your Sprint [15, p. 12]
(9) The team is going to take longer than anticipated to finish all tasks they committed to [15, p. 73] Do not inflate your remaining Sprint time [9]
The Scrum Master and Product Owner should assess potential consequences of the failed deadlines [15, p. 74]
The Scrum Master may investigate the situation and gather information on why the deadlines were missed to present to the customer [15, p. 74]
The Scrum Master and Product Owner should prioritise remaining Sprint Backlog Items in an effort to maximise the value of the Sprints’ outcome [15, p. 74]
(10) The count of User Stories within the Backlogs is already sufficient for a Sprint [9] Plan another Sprint ahead [9, 10]
(11) Insufficient visualisation of Product Backlog and Sprint Backlog [18, p. 109] Use Information Radiators (regardless of digital or analogue) [13, p. 83]