Two Leads, One Integration Test Window
Your cybersecurity platform deployment has a ten-day integration test window that cannot move because the client's data center is booked. The systems integration lead, Marcus, has 12 engineers and insists that all security testing must wait until functional integration is complete, because earlier security scans caused false positives and rework on the last project. The security lead, Dana, has 9 engineers and refuses to sign the integration exit criteria unless penetration testing runs in parallel with the last three days of functional testing. She has data showing that a sequential approach will exceed the window by four days. The two leads have exchanged increasingly sharp emails, and Marcus copied the client's technical director on his last message. Two integration windows have already slipped, and team members are choosing sides. Your sponsor is traveling and has told you to "sort it out."
1. Which conflict-handling approach is most appropriate, and what steps would you take in the next 48 hours?
Read the worked answer
The appropriate approach is collaboration, with some compromise on sequencing if the technical evidence supports it. Both leads have legitimate interests: Marcus wants stable functional integration and fewer false positives; Dana wants enough parallel testing to fit a fixed window and to satisfy security acceptance. The conflict is interdependent, not a zero-sum personality clash, and the project cannot afford a forcing decision that leaves one lead disengaged.
In the next 48 hours, separate the people from the problem. Meet each lead individually to hear the underlying interests and to stop the email escalation. Then convene a joint working session with both leads and a small number of engineers, using objective criteria: the test dependency matrix, the false-positive data from the last project, the window constraints, and the client's acceptance criteria. Ask them to design a sequenced-parallel option-for example, security testing on stable interfaces while functional testing continues on unstable ones-and document the entry and exit criteria for each. Do not decide the technical sequence yourself unless they deadlock; your role is to structure the decision and ensure the client sees a unified plan. Separately address the cc to the client: acknowledge the client's concern, confirm that the team is resolving the sequence, and avoid blaming Marcus publicly.
2. What communication and escalation actions should follow once the technical plan is agreed?
Read the worked answer
Once the technical plan is agreed, document it in a short signed-off test sequence and acceptance criteria, with named owners and dates. Hold a joint kickoff with both teams so the agreement is public and not just a bilateral understanding. Update the stakeholder engagement plan: the client's technical director should receive a concise status note explaining the agreed parallel approach and the residual risk, without exposing the internal conflict. The sponsor should receive a brief escalation summary only if the agreement changes scope, cost, or the fixed window; otherwise, report it through normal governance.
Follow-up matters as much as the meeting. Schedule daily 15-minute test stand-ups for the ten-day window, with a single decision log and a rule that technical disputes are resolved by evidence, not by email. Watch for residual coalition-building among team members; if it persists, address it in a team ground-rules session. If the leads later deadlock on a specific defect, escalate that issue-not the relationship-to the sponsor with options and a recommendation. The goal is to restore a working relationship while protecting the test window, not to declare a winner.