A project manager is overseeing a multisprint data integration project involving internal developers and an outsourced analytics team. Midway through…

In Agile and hybrid environments, the sprint retrospective is the primary mechanism for continuous improvement and process adaptation. The scenario highlights a lack of formal feedback mechanisms alongside deteriorating team engagement and collaboration between internal and outsourced teams. By facilitating a retrospective, the project manager empowers the team to safely discuss communication breakdowns, uncover the root causes of missed handoffs, and collaboratively develop actionable solutions. This aligns with the Agile principles of self-organization and inspecting and adapting, ensuring the team takes ownership of improving their working relationships rather than relying on top-down directives.

Option A: Scheduling one-on-one calls with leads is a command-and-control tactic that undermines team self-organization and fails to address cross-team collaboration issues collectively.
Option C: Circulating meeting summaries is a passive administrative action that does not actively engage the team to identify or resolve the root causes of their communication breakdowns.
Option D: Escalating the issue to the sponsor is premature and violates the Agile principle of empowering the team to resolve their own internal process and collaboration issues.

1. Project Management Institute (PMI). (2017). Agile Practice Guide. Section 5.2.1 (Retrospectives), pp. 50-51. (Details how retrospectives allow teams to learn, improve, and adapt their processes to resolve collaboration issues).

2. Project Management Institute (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Section 2.2 (Team Performance Domain), pp. 16-22; Section 2.7.2. (Measurement Domain - Team Performance), p. 101. (Discusses establishing team culture, safe environments for feedback, and measuring team engagement).

3. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Section: Sprint Retrospective. (Defines the retrospective as the formal event to inspect how the last sprint went with regards to individuals, interactions, processes, and tools).