A Shift in Approach

In a previous role, I regularly met with a colleague from another department to discuss the dependencies between our projects. His sole responsibility was to manage these dependencies, which he was well-compensated for. We often deliberated on the timing of our respective workstreams and the importance of completing one task before the other.

However, my understanding of dependencies has evolved. I now prioritize eliminating dependencies or confining them to minimize their impact. I no longer invest excessive time on scheduling deliverables based on these dependencies or managing the individuals involved to ensure they meet their timelines.

Why this Change?

The reality is that many dependencies are often unnecessary constructs. Yes, you heard me correctly—constructs. At some point, someone has to identify these dependencies, often with the best intentions, but they can be misguided.

For instance, common phrases such as:

• "We need to complete the database before starting on X."
• "We need to roll out training videos before the launch."
• "We must wait for that API before proceeding."

These statements can create complications. While some dependencies may arise from genuine concerns, they are often naive in nature. The more actions that need to be synchronized, the less likely it is that any of them will be completed on time, increasing the associated risks. A single dependency can be detrimental; multiple dependencies can be catastrophic.

What Should be Done Instead?

Adopt the same principles for managing project and product dependencies as you would with architectural dependencies: strive for loose coupling or, better yet, decoupling.

If you're involved in product management and are unfamiliar with the concepts of loose and tight coupling, I encourage you to familiarize yourself with them. A great starting point is Martin Fowler's insightful articles on refactoring and software architecture principles. These concepts can lead you to approaches like microservices, which, when implemented correctly, can significantly reduce risk and complexity.

By applying the mindset of loose coupling, we can lower risk and enhance the likelihood of achieving timely project delivery, meeting product release schedules, and decreasing overhead through minimized interactions.

Strategies to Minimize Dependencies

In the world of Minimum Viable Products (MVPs), dependencies will emerge frequently. When they do, assess whether they are truly necessary. If a dependency cannot be avoided, work to limit its scope.

Let's re-evaluate the examples mentioned earlier with a focus on eliminating dependencies:

1. Database Completion Before Starting X

   If both the database and the user interface (UI) are essential components for the feature, consider what elements of the UI can be developed independently. Is there a way to release the UI quietly without exposing users to it? Tools like Launch Darkly or code toggles can facilitate this, allowing progress on the UI while the database work proceeds independently.

2. Training Videos for Customers

   Is training genuinely necessary? If the capability is intuitive, perhaps simpler alternatives like a few slides or key points in release notes would suffice. If your engineers are skilled, they might have solutions to enhance usability without the need for extensive training materials.

3. API Availability

   APIs serve specific functions, but there are often alternative methods to achieve the same outcomes. Can secure file transfers or ETL tools accomplish the task? Exploring manual processes as a temporary measure could also be beneficial.

Final Thoughts

In conclusion, it's essential to strive for the elimination or limitation of dependencies. The return on investment in managing dependencies effectively can lead to more timely and high-quality project outcomes. The MVP mindset should extend beyond mere functionality; it can also apply to managing the influences and requirements imposed by other departments such as Sales, Marketing, and Finance.

With these insights, I wish you success in tackling dependencies with an MVP approach. If you have your own experiences or ideas related to dependency management, I would love to hear from you. Thank you for reading.

The first video titled "How to Manage Dependencies on Agile Projects" delves into strategies for effectively handling dependencies in agile environments.

The second video, "How to Identify and Remove Dependencies," offers practical tips for Scrum Masters and Agile project managers on eliminating dependencies in their projects.