PMP · Question #815
A company is launching a new product and decides to transition from a predictive to an agile approach. During the third sprint, the project manager notices that the team is not working as a cohesive u
The correct answer is A. Work together daily as a team. B. Strive toward continuous improvement.. To enhance team cohesion in an agile transition, the project manager should instill rules emphasizing daily collaboration and a mindset of continuous improvement.
Question
A company is launching a new product and decides to transition from a predictive to an agile approach. During the third sprint, the project manager notices that the team is not working as a cohesive unit. Which two rules are appropriate for the project manager to instill in the team? (Choose two.)
Options
- AWork together daily as a team.
- BStrive toward continuous improvement.
- CSend communications to the entire team.
- DFollow the sprint planning.
- EOnly share suggestions at the end of the sprint.
How the community answered
(17 responses)- A82% (14)
- D12% (2)
- E6% (1)
Why each option
To enhance team cohesion in an agile transition, the project manager should instill rules emphasizing daily collaboration and a mindset of continuous improvement.
Agile principles highly emphasize daily interaction and self-organizing teams working together; daily collaboration builds rapport, facilitates quick problem-solving, and fosters a sense of shared responsibility, which is crucial for team cohesion.
Continuous improvement is a core tenet of agile, encouraging the team to regularly reflect on their processes and find ways to become more effective and productive, which helps improve team dynamics and overall performance.
While good communication is vital, 'Send communications to the entire team' is a general practice rather than a specific rule for instilling cohesion in an agile context, and agile often favors direct, face-to-face communication over broadcast emails.
Following sprint planning is expected in agile, but it's a procedural requirement rather than a rule directly focused on building cohesion as an underlying team behavior.
Limiting suggestions to the end of the sprint contradicts the agile principle of continuous feedback and adaptability, which encourages frequent communication and immediate resolution of issues.
Concept tested: Agile principles and team building
Source: https://agilemanifesto.org/principles.html
Topics
Community Discussion
6
Ola B.Jun 2, 2026A and B are the right picks. If you want to see this in action, spin up a quick two-week sprint lab with a few peers and watch how daily collaboration and continuous improvement naturally pull a disjointed team together, whereas end-of-sprint suggestions just bottle up the tension.
Mateus R.Apr 30, 2026Think of a band learning to jam together daily, not just at rehearsals. Why does continuous improvement matter mid-sprint?
Orla P.May 15, 2026D is a lock here because when a team is transitioning from predictive to agile, anchoring them to the sprint plan gives everyone a shared commitment and stops the drift. The structure of sprint planning is exactly what pulls a fractured group into a cohesive unit.
Mateus R.May 16, 2026Orla, I'd flip to A and B here. Think of it like a ranch hand moving from horseback to an ATV: you don't teach them to ride by handing them the keys and a route map, you let them sit on it, feel the throttle, and steer around the corral a few times. A and B capture that hands-on learning and iterative adaptation, which is what actually carries a team across the predictive-to-agile threshold, whereas D just hands them the new vehicle's manual.
Wesley A.May 23, 2026I am going with B and E here. During my first attempt I overthought the team dynamics stuff and paid for it. Continuous improvement in B is a no brainer for agile teams, and E makes sense because you do not want people derailing the sprint with constant suggestions mid iteration. Saving feedback for the end keeps the team focused on the current sprint goal and prevents scope creep from well meaning input. That cohesion problem the scenario describes usually comes from too much chatter during the sprint, so E directly addresses the root cause.
Ola B.May 26, 2026A and B is correct. Wesley, E actually hurts agile teams because feedback should flow throughout the sprint, not get bottled up until the end. Spin up a quick board in Azure DevOps and watch how mid-sprint feedback in the daily standup keeps the team aligned instead of derailing anything.