Overcoming Remote Agile Challenges: Lessons from a Localized R&D Team

Remote Team Challenges and Responses

Since the Chengdu Tianfu Engineering Institute of Qunhe Technology opened in October 2020, the R&D team has gradually shifted to a localized operation model. More than half of the staff now work locally, while a sizable portion still collaborates with remote teams.

Challenge 1: Limited Participation and Efficiency in Agile Activities

Remote members often join agile ceremonies via voice calls or messaging, leading to reduced involvement and lower efficiency. Over time, they may become detached, focusing only on their tasks, which harms team cohesion and overall output.

Example: A remote member reported poor network quality that made it hard to hear discussions, causing gradual disengagement and slower iteration speed.

Response: When business segmentation matured, a local agile squad was created with a comprehensive team charter and agile operating mechanisms, ensuring full‑stack participation from the start.

Challenge 2: High Communication and Collaboration Costs

Agile principles stress face‑to‑face communication, but distributed teams suffer from high costs, limited emotional exchange, and weaker team bonds, leading to coordination difficulties.

Example: A product owner struggled with misunderstandings when communicating with remote developers.

Response: In‑person meetings and team‑building trips were organized to strengthen relationships, and as local members increased, remote communication overhead decreased.

Challenge 3: Business Silos and Coupling

New teams entering cross‑site projects face steep learning curves for system knowledge, architecture, and documentation, while strong data coupling across modules raises coordination effort and risk of conflicts.

Response: Teams gradually decoupled business logic and introduced modular boundaries to reduce coupling and improve delivery speed.

Challenge 4: Inconsistent Agile Practices Across Locations

Differences in interpreting user stories and PRDs caused friction between remote and local product owners and technical leads.

Response: A PMO coach facilitated the creation of a unified team charter to align practices.

Challenge 5: Cross‑Site Dependency Tasks Slowing Delivery

Tasks that require coordination across sites and groups create scheduling conflicts and delay releases.

Response: The PMO introduced a tracking template for cross‑group dependencies, ensuring transparent communication and closed‑loop delivery.

Overall Strategy

To boost R&D efficiency and reduce cross‑site costs, the organization pursued progressive localization: concentrating more members in local, independent teams, establishing clear agile processes, and implementing concrete mechanisms such as checklists, communication protocols, iteration calendars, and dependency tracking.

Localized Agile Adoption Practices

Agile Squad Checklist: Defines required steps and timelines for forming a new squad.

Clarify Business Division to Reduce Coupling: Engage business owners early to define clear boundaries.

Refine Agile Operating Norms: Provide templates for common practices, Scrum events, testing standards, and acceptance procedures.

Establish Agile Iteration Calendar: Sets a fixed rhythm for all roles, reducing ad‑hoc changes.

Cross‑Group Dependency Communication Mechanism: Use a template for timely feedback, tracking, and closure.

Conclusion

These improvements have made the formation of new agile squads smoother, fostering a positive team experience and efficient operation while respecting the uniqueness of each business line and maintaining an open, learning‑oriented mindset.