tag:blogger.com,1999:blog-1814874240228543789.post4995052526900903004..comments2024-03-28T00:19:17.790-07:00Comments on Agile Adoption Roadmap: Requirements Tree: Focusing your efforts on the highest value work Mario Moreirahttp://www.blogger.com/profile/00969447879025623968noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1814874240228543789.post-76454772289263885582021-03-31T04:48:49.073-07:002021-03-31T04:48:49.073-07:00I had a question on how is this different from WBS...I had a question on how is this different from WBS. Here is my answer: They are really wholly different things. <br /><br />First, most WBS is specific to either idea or increment on down and don't connect direct to strategy. <br /><br />Second, Requirements Tree ensures that the connected work is based on the highest value work at each level. I've worked with WBS for years and there is often no associated value at each level. So you end up doing all of the tasks at the next level when the highest value may be all you need. <br /><br />Third, you align who works at each level and with what tools (e.g., at an idea level, a PM/PO might use a lean canvas, while at a user story level, the PO might use the user/action/reason structure). The WBS offers no such guidance and each level is often the same.Mario Moreirahttps://www.blogger.com/profile/00969447879025623968noreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-85291142993170432912021-03-31T04:47:30.380-07:002021-03-31T04:47:30.380-07:00Yes, it should visually show this challenge (some ...Yes, it should visually show this challenge (some requirements have dependencies on other items in other trees.). I've used this to help with understanding if we need more cross-functional teams or dependencies across teams. <br /><br />Yes if value and dependencies are appropriately indicated (do this first, then that, but with some idea of how the different ideas/features/items are related.)<br /><br />Thanks for sharing your thoughts!Mario Moreirahttps://www.blogger.com/profile/00969447879025623968noreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-59903625420326747752021-03-15T17:23:35.910-07:002021-03-15T17:23:35.910-07:00Requirements are not always linearly decomposable....Requirements are not always linearly decomposable. So some requirements wont' fit easily under a particular traversal of a tree.<br /><br />One might also need to consider that some requirements have dependencies on other items in other trees.<br /><br />So, in fact, the requirements tree then actually becomes more like a roadmap, do this first, then that, but with some idea of how the different ideas/features/items are related.fishzlehttps://www.blogger.com/profile/14048891374845950521noreply@blogger.com