The normal dogma of agile execution is to avoid dependencies as they are perceived to disrupt flow and the ability to act with agility. But, why avoid a dependency that creates business value such as reusing customer information across products? Why add yet another framework which would increase the technical debt when there is one suitable already there? This workshop will provide and refine a framework and practices to identify and manage the dependencies that truly create value while avoiding those that don't. This will ensure a more constructive way of dealing with dependencies.