Sometimes we need help to improve our team and sharing insights into why some practices and behaviors can sabotage team progress. Take a look at the following observations teams have made to see if your team can identify with them and take action before it becomes a bigger or longer term problem.
We have a lot of stories that are closed by DEV and then new stories for QA testing are created to test what Dev hands over.
Impact to the Team:
- Because the number of stories in the sprint steadily increase during the sprint, the burndown chart will likely look like the team is always behind schedule.
- Individual capacity is extremely difficult to plan during sprint planning because the number of stories at the beginning of the sprint will be lower than reality.
- Forecasting sprint plans and project schedules via velocity is useless here because the…
View original post 988 more words