Which action is explicitly discouraged during a kickoff call?

• A. Allocate tasks and resources to specific stakeholders
• B. Set the roles and responsibilities across the team
• C. Bring up dependencies and blockers
• D. Confirm testing and deployment processes

Answer: (A)

Kickoff calls are about aligning on the project’s purpose, scope, goals, and a shared understanding of how the team will work together. They’re the moment to establish high-level roles, how you’ll communicate, the planned milestones, and to surface dependencies or potential blockers so everyone is on the same page.

Allocating tasks and resources to specific stakeholders at this stage is discouraged because it commits to work assignments before the plan is fully developed. It can lock in commitments too early, create misunderstandings if priorities evolve, and distract from establishing a clear, flexible governance approach and the overall timeline. By contrast, clarifying who is responsible at a high level, identifying dependencies and blockers, and agreeing on testing and deployment approaches are all appropriate to cover during kickoff, since they help teams coordinate and set expectations without locking in detailed work yet.