value breakdown structure vbs - how to really split epics features and stories

Experiment: value breakdown structure (vbs) Problem: There is a massive antipattern of people taking product features and using the epic/feature/story hierarchy to draft a work breakdown structure (WBS) of tasks. But that is not the intent of epics features and stories. They are supposed to be a value breakdown structure (VBS). Using a WBS will lead your teams to mimicking a waterfall team, significantly delay value delivery and give false velocity metrics. Hypothesis: If we learn to create a Value Breakdown Structure (VBS), our epics, features and story quality will go way up and our ability to deliver value early will go way up. Time Frame: 3 sprints, pivot or persevere after one Typical Outcomes: decrease time to value delivery, increase value delivery metrics accuracy Skill Growth Criteria: You have refactored your backlogs to be value delivery items instead of work breakdown items, you use enablers as a last resort splitting technique in favor of the eight value splitting techniques and you distinguish between product features, business features, enabler features and capacity features Shirt Today: carbon form