I have multiple user stories for each feature which clutters up the backlog and is difficult to keep the stories aligned to the project they are linked to. Exposing the features on the Kan ban board as a way to group the user stories and allow the features to open in the backlog would allow the Scrum Master to control the backlog with groupings of user stories aligned to projects. A team member would go to the project feature, expand the folder/directory and pull their user story out onto the Kan ban board when they were ready to work that project. This would give some order to the backlog and make it easier to prioritize user stories according to which project the team was working that sprint. If the features were filtered for team specific user stories there would be no cross team issues.

Comments