Onboarding & Teamwork
Run a Project Kickoff That Resolves Scope, Risks, and Ways of Working
A completed fictional cross-team fixture migration kickoff package resolves discovery scope, documents dependencies and accepted capacity, and retains access/ownership gates and the uncommitted cutover date.
A useful project kickoff ends with an agreed starting point: the outcome being pursued, the work included and excluded, the people who can make decisions, the dependencies that still need confirmation, and the team's working agreements. Use the meeting to resolve specific differences and assign open questions. A shared presentation is preparation; it is not proof that the project is ready to execute or release.
The record should tell participants what they may start, what they must wait for, and where a new scope request goes. This LandOffer.ai guide uses a fully fictional cross-team migration project. No real files, repositories, access permissions, accounts, calendar invitations or migration operations were inspected or changed.

Prepare decisions rather than repeat the project slides
Atlassian's project-kickoff play describes a kickoff after initial project definition, with purpose, roles and success markers clarified together. It distinguishes sponsor, leader, facilitator, core team and stakeholders, while allowing the agenda to be adapted. Use that starting point to identify the decisions the team still needs, rather than read an already distributed proposal aloud.
Before the session, ask the sponsor and delivery participants to review a short brief. Mark facts, estimates, proposed boundaries and unresolved approvals separately. Include the intended outcome, why the project matters, a first definition of done, known dependencies, available capacity and the decisions requested at kickoff.
Invite people whose work or authority is needed. Someone attending as a stakeholder does not automatically commit their whole team. If a required reviewer cannot attend, obtain their input through an agreed route or record that decision as pending. A facilitator records the question and its decision owner so participants know whose confirmation they still need.
In the fictional example, project lead Yara is coordinating a move of internal demo fixtures from a shared drive toward a versioned repository. The goal is to make fixture ownership and revision history inspectable. Sponsor Asha has approved discovery from January 7 through the January 18 readiness review. That date is not a migration or cutover commitment.
The initial inventory is expected to contain twelve fixture sets. This is an invented planning assumption, not a completed audit. The kickoff must settle whether the first phase covers all twelve in detail or defines a smaller rehearsal package, and what approvals are needed before any actual copying.
Complete the kickoff brief with scope and authority
Yara shares the draft brief on January 5. Fixture owner Ben, platform engineer Zain and consumer lead Nell add questions in advance. Asha confirms the discovery allocation. Required access reviewer Ivo cannot join the kickoff, so approval of the target access plan remains outstanding.
The filled package below is the version accepted at the end of the fictional January 7 meeting. It documents a planning agreement, not completed migration work.
| Brief item | Agreed entry |
|---|---|
| Purpose | Prepare a reviewable migration approach that preserves fixture ownership, provenance and the expectations of two internal consuming teams |
| Phase outcome | A checked inventory, a four-fixture rehearsal specification, a proposed repository structure and an access-review decision for the proposed target |
| In scope | Inventory the expected twelve sets; choose four representative sets for detailed planning; describe identifiers, ownership and consumer references; draft acceptance checks |
| Out of scope | Copying real fixtures, changing permissions, switching consumer references, deleting shared-drive content, committing a cutover date, or declaring the target ready |
| Success markers for January 18 | Each inventoried set has an owner or a visible ownership gap; the four-fixture plan covers its selected variants; reviewers can identify unresolved access and consumer issues |
| Decision authority | Asha owns discovery scope and capacity; Ben confirms fixture meaning and ownership; Zain recommends repository structure; Nell coordinates consumer requirements; Ivo's required access decision remains pending |
| Project roles | Yara leads and facilitates; Ben, Zain and Nell perform the allocated work; affected consumer teams receive the record and can flag missing dependencies |
| Change route | New requests include purpose, effort and displaced work; Yara records them and Asha accepts or declines any discovery-scope change |
Notice that the phase outcome includes a decision, while the success markers permit visible unresolved issues. If Ivo rejects the proposed access plan, the discovery can still produce a useful readiness review. It cannot claim that the access gate passed or that implementation may proceed.
Keep this distinction explicit. “We agreed to define a rehearsal” is different from “the rehearsal passed.” An owner listed against a fixture does not establish that its data is suitable to copy or that another team's references will continue to work.
Resolve the first disagreement and map dependencies
At the kickoff, Nell asks for all twelve fixture sets to be migrated by January 18. Ben has capacity to investigate four representative sets in detail during this phase, alongside a broader ownership inventory. Yara records the two requested outcomes and asks Asha to choose the authorized phase boundary.
The completed fictional exchange is brief:
Yara: “The approved phase is discovery. Nell's requested outcome is a full migration by January 18; Ben's available work supports an inventory and four detailed specifications. Which outcome are we authorizing?”
Asha: “The discovery package. We will not promise copying or consumer cutover on January 18. Nell, which variants matter most for choosing the four?”
Nell: “One fixture used by both teams, one with a renamed identifier, one with a large attachment and one with a stale consumer reference. I accept that selection for planning, but still need a later date for full migration.”
Ben: “I accept investigating those four within the allocated time. If the inventory reveals another distinct variant, I will flag the gap before claiming the set is representative.”
Yara records the narrower phase decision and Nell's unmet scheduling need. There is no implied agreement about the eventual migration date.
Atlassian's dependency-mapping play recommends identifying affected systems, their owners and impacts, then linking risks to mitigations and feedback arrangements. Apply that method to the work the phase actually authorizes. A list of dependencies becomes useful when someone knows who must confirm what and when.
| Dependency or risk | Named owner and needed confirmation | Response agreed at kickoff |
|---|---|---|
| Target repository access model | Ivo must review the proposed readers, contributors and approval route | Zain drafts the plan; Yara requests Ivo's availability and capacity; no approval is inferred from silence |
| Consumers refer to old fixture identifiers | Nell obtains both consumer teams' reference requirements | Keep an identifier mapping in the specification; no links are switched during discovery |
| Shared fixture ownership is ambiguous | Ben records the relevant team contacts and seeks confirmation | Mark an ownership gap rather than assign it to the last person who edited a file |
| The selected four omit a meaningful variant | Ben identifies any additional variant; Asha decides added scope | Report the gap with the effort and displaced work before expanding detailed planning |
| Shared-drive deletion or retention expectations are unknown | Yara must identify who can decide retention and deletion requirements for the later implementation phase | No deletion is planned or authorized by this kickoff; retain the unresolved issue for readiness review |
These are decisions about managing dependencies. None establishes that the technical or policy questions have already been answered.
Agree how the teams will work and raise changes
Atlassian's working-agreements play covers communication channels, escalation, meeting plans and later revision of the agreements. Its particular workshop preferences are not universal requirements. The useful output is an arrangement the team can follow within its actual availability.
The fictional team accepts one project page as the source for scope, decisions, dependencies and actions. A project chat carries coordination questions and links back to decisions; a private message does not change the agreed scope by itself. Each action owner posts a short status before the January 11 and January 16 checkpoints, including blockers and the next evidence expected.
A fifteen-minute checkpoint is reserved for unresolved decisions, not reading every status aloud. Yara offers written input for people who cannot attend. Asha is the discovery-scope escalation owner, while Ivo retains the access-review decision; asking Asha to prioritize the project does not replace that specialist review.
For ordinary questions, the team plans a response within the next working day in the recipient's agreed hours. Acknowledgement can identify when an answer will follow; it does not have to settle the question immediately. The arrangement is a project choice, not an always-on expectation or a universal service level.
If an assigned task cannot fit, its owner names the remaining work and consequence before accepting more scope. Asha decides whether to reduce the package, change the review date or explicitly reallocate capacity. The team will revisit these working agreements at the January 18 review, or earlier if the agreed channels or response window prove unusable.

Publish the first-week record with accepted work and open gates
Yara finishes the January 7 record with the following accepted actions. Asha and the delivery owners confirm the allocations in this fictional case. Hours are planning allocations, not verified execution times or a claim that migration will fit inside them.
| First-week action | Accepted owner, capacity and date | Evidence expected |
|---|---|---|
| Check the twelve-set inventory and identify the four planning variants | Ben; four hours replacing optional example cleanup; January 8 | Inventory with ownership confirmations or gaps, plus reasons for the four-set selection |
| Draft repository structure and target access proposal | Zain; six hours replacing an optional developer-tool benchmark; January 10 | Reviewable structure and access proposal, clearly unapproved until Ivo's response |
| Gather both consumer teams' reference requirements | Nell; two hours replacing optional FAQ reorganization; January 11 | Confirmed requirements, or named unanswered questions and contacts |
| Consolidate decisions and request the access-review slot | Yara; two hours within the existing discovery coordination allocation; January 9 | Updated page, review request and an explicit acknowledgement or pending status |
The access review is a dependency, not an accepted assignment on Ivo's behalf. At meeting close, its owner availability is unknown. Asha's approval of the project does not supply Ivo's capacity.
In a fictional January 9 update, Ivo acknowledges the request and Ivo's manager Jo confirms one hour on January 11, replacing an optional platform-documentation review. Ivo accepts that review slot. Yara updates the dependency from “availability unconfirmed” to “review scheduled; decision pending.” The kickoff has helped resolve who can do the review, without pretending the proposed access model has been approved.
Ben’s January 8 note contains twelve inventory entries with eleven confirmed owners and one ownership gap. Yara retains that gap for follow-up; consumer answers also remain pending in the January 9 update. The four variants are a planning selection, not a claim of comprehensive test coverage. Yara keeps Nell's request for a full migration date visible for January 18; the record makes no promise about that date or the later release.
Close with a record someone can challenge
Before ending the kickoff, read back the included and excluded work, accepted owners, unresolved gates and next review. Ask participants to confirm their commitments or correct the record, and mark unacknowledged assignments as pending. Attendance or silence does not prove that an absent owner accepted a task, and a smooth meeting does not prove that dependencies are resolved.
For your next project, prepare one concise package around the decisions still needed. Finish with the first week's accepted work, the evidence each action should produce, and the questions that must return to a named owner. Return to LandOffer.ai for more workplace guides; the immediate result is a shared starting point that can be checked and revised as execution reveals new information.
Sources and Further Reading
- Atlassian: Project Kickoff — project purpose, roles, success markers and a retained kickoff outcome.
- Atlassian: Dependency Mapping — affected systems, ownership, risks and feedback arrangements.
- Atlassian: Working Agreements — channels, escalation, collaboration routines and revisiting agreements.


