5/3/2023 0 Comments Agile product backlog template![]() For better or worse, products themselves tend to take on the characteristics of the organizational structures that create them. One workaround is to complement this method with heavy use of release tagging for goal setting. What happens when we organize by team is that user stories become orphaned from big picture goals or strategy. ![]() Such an arrangement makes it much easier to communicate and resolve dependencies. When they can see their backlogs side by side, teams with strong dependencies among each other suddenly have some visibility they didn’t have before. ![]() Or Team Yellow and Team Blue, as above.Ī few things happen when we structure this way: A backlog structured around team organization does just that: Its hierarchy is shaped by the shape of the organization - by the different teams working on the product.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |