Over a million developers have joined DZone.

Top 3 Dependency Types

DZone's Guide to

Top 3 Dependency Types

When trying to achieve true enterprise agility, you should focus first on the fundamentals of Agile delivery while systematically and methodically breaking dependencies.

· Agile Zone
Free Resource

Speed up delivery cycles and improve software quality with TestComplete. Discover the most robust automated testing tool for end-to-end desktop, mobile, and web testing. Try TestComplete Free.

True agility comes from breaking dependencies between teams across the organization. It all begins by defining a rational system of delivery for the enterprise. After that, healthy culture and solid practices should emerge within that rational delivery framework. For those who wish to transform their organizations, solving the issues that get in the way of effectively practicing Agile is what should guide you. Focus first on the fundamentals of Agile delivery while systematically and methodically breaking dependencies. In this way, we can achieve true enterprise agility.

So, what are the dependency types we should be looking out for?

3 dependency types

1. Business Dependencies

Business dependencies may emerge when the backlog does not sufficiently meet the definition of ready, when there is too much work in process, or when requirements are being shared across teams. Often, multiple teams can be dependent on each other to deliver a single feature.

2. Structural Dependencies

Structural dependencies may originate from having a highly matrixed organization, not having instantly available people, or having limited access to SMEs (subject matter experts). Though companies try to keep people busy, sharing people between teams often results in delays.

3. Technical Dependencies

Technical dependencies may originate from large products with diverse technology, too much technical debt or defects, or low cohesion and tight coupling.

Where Dependencies Come From

Dependencies may come from a lack of clarity. Your system of delivery needs to be well understood. Your backlog must be clear and ready. There must be a shared understanding of governance.

Dependencies can also be caused by a lack of accountability. People must know what they are responsible or accountable for. Ensure that you have the proper organizational structure.

Lastly, dependencies can result from a lack of progress. You need metrics and tools to measure the system of delivery. At scale, a physical team board is not enough to provide real-time progress. Make sure you are leveraging the proper metrics to ensure you can see value flowing through the system of delivery and there is a balance between capacity and demand.

Release quality software faster with TestComplete. Discover how to decrease testing times and expand test coverage with the most robust automated UI testing tool. Try free for 30 days.

agile ,dependencies ,work culture ,enterprise

Published at DZone with permission of Derek Huether. See the original article here.

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}