Back to resources

Managing and Eliminating Cross-Team Dependencies

Strategy
Stakeholders
Team Processes
Cross-Functional Collaboration

11 February, 2022

Ricardo Aravena
Ricardo Aravena

Infrastructure Engineering Manager at TruEra

Ricardo Aravena, Infrastructure Engineering Manager at Rakuten Rewards, shares some of the best practices of dealing with the cost of cross team dependencies.

The Good, the Bad & the Ugly Sides of Team Dependencies

Working in a cross-functional environment, team dependencies are inevitable. When I was working cross-functionally, the team was working on a monolith and we were releasing features in a slow cadence. If we brought in a small change, all the other teams needed to be informed. It led to missed deadlines, chaotic context switching, non-stop meetings and some other undesirable effects.

A Heuristic for Managing Dependencies

Soon enough we knew that we needed to be more pragmatic, and instead of blocking individuals' way, we implemented strategic, uninterrupted initiatives.

As we moved to a microservices architecture, we created an automated framework to test them. Every time the team had to release something, they no longer had to rely on manual testing. Additionally, the framework also helped our team in breaking down our monolith components into more distributed parts. We were also leveraging GitHub actions to deploy applications to Kubernetes AWS Lambda.

Manage People Based On Their Seniority

  • People working in teams usually have different skill levels. Senior engineers are likely to be needing high-level coaching to get a hold of everything, while juniors they would need to be more trained thoroughly. Understand the differences between these two.
  • Allow your team to provide their input and then to make changes in the process.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Hosting a successful internal hackathon with < $6k budget

6 February

Internal Hackathons invite team spirit and collaboration which are critical whether an engineering org is co-located or operating remotely spread across 20 times zones. Hackathons give employees the opportunity to connect and network while they solve fun & relevant challenges.

Company Culture
Team Processes
Balki Kodarapu

Balki Kodarapu

Senior Director of Engineering at SupportLogic

A Day in the Life of a Product Lead in FinTech – A Series

31 January

Discover the daily struggles, challenges, and moments of delight encountered when delivering banking products around the world. I will share my story candidly and honestly, without filter as much as I am allowed, and offer insights into my approach while providing retrospectives of the results.

Strategy
Embracing Failures
Cultural Differences
Career Path
Loussaief Fayssal

Loussaief Fayssal

Director of CX at FLF PRODUCT DESIGN

Myth Busting

10 December

Supporting principles on why being data led (not driven) helps with the story telling.

Alignment
Managing Expectations
Building A Team
Leadership
Collaboration
Productivity
Feedback
Psychological Safety
Stakeholders
Vikash Chhaganlal

Vikash Chhaganlal

Head of Engineering at Xero

The Not-So-Easy Guide on How to grow and develop an Amazing A-Team

5 December

Your Org Team may as well be a Sports team. Let's explore how this cohesive, multi-skilled team can be optimized for Great Group Playoff.

Alignment
Building A Team
Company Culture
Sharing The Vision
Embracing Failures
Team Processes
Jaroslav Pantsjoha

Jaroslav Pantsjoha

Google Cloud Practice lead at Contino

DevSecOps: Why, Benefits and Culture Shift

29 November

Why DevSecOps matter and what's really in it for you, the team and the organisation?

Innovation / Experiment
Building A Team
Leadership
Ownership
Stakeholders
Cross-Functional Collaboration
Vikash Chhaganlal

Vikash Chhaganlal

Head of Engineering at Xero