The Lean/Agile way to Manage Cross-Team Product Initiatives

Melissa Perri argues that when several product teams must deliver a shared cross-team integration, companies need a deliberate coordination model or the work stalls. She describes two strategies: dual responsibility, where each team owns its side as a separate roadmap item, and single responsibility, where one person owns the whole integration. She explains how to choose between parallel and sequential phasing, and why this structure supports rather than conflicts with Agile practices. The piece matters because integrations after mergers and acquisitions often fail from unclear ownership and poor dependency management rather than from technical difficulty.

01Key takeaways

• For large, strategic integrations spanning several teams, assign one owner to coordinate, communicate, and surface trade-offs.
• When teams share responsibility without a single owner, expect an everybody-or-nobody problem where progress stalls.
• Map dependencies explicitly, such as with a Gantt chart, so teams don't finish their side and then wait while code drifts out of compatibility.
• Scope down integrations to key fields or a lightweight version when resources are constrained to hit a critical market date.
• Plan integration work in phases, and define a phase as successful only when the working integration is functional end to end.
• Use good project management structure to make Agile practices easier, not harder, by clarifying dependencies and end states.

02Key sections

Dual responsibility

Each team takes a separate project for its side of the integration, with clear deliverables on its roadmap. Mismatched effort and timing can cause compatibility problems, so dependencies need visualizing and frequent communication.

Single responsibility

One person oversees the entire integration as the single point of contact, which avoids an everybody-or-nobody dynamic. That owner decides what runs in parallel, what must be sequential, and what can ship in a lightweight form.

Parallel versus sequential phasing

Parallel work can proceed through phases of simple APIs, connection testing, and robust expansion, while sequential work tackles one integration pair at a time. Phases need not be development work and can include beta testing or feedback.

Agility and large projects

A high-level integration plan is a skeleton that gets broken into smaller pieces, so the work stays Agile. Good project management clarifies dependencies and enables faster pivots.

Choosing the approach

Project size, available resources, number of teams, and the need for executive updates determine whether a single owner is needed or the teams can self-manage. A real M&A example shows a dedicated product manager aligning over 50 products.

03From the post

“Are you part of a company that has grown through mergers or acquisitions? Does your company have a portfolio of products they’ve built? If there is a horizontal strategy at play, then the executive leadership probably has intentions of integrating the different products to create a competitive advantage with a “best in suite” angle.”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.