Delivery and Migration17% of the exam
Engagement phases, workstreams and Slack project channels
How a Slack services engagement is run: the five project phases and what the client does in each, the four workstreams and where migration sits, first-week governance and SOW review, delivering the project in a Slack Connect channel, and the platform versus enablement launch readiness check.
Understand Slack delivery best practices.
~8 min read · 10 practice questions ·
What the exam expects
- Place an activity in the right project phase (Prepare, Understand, Design, Launch, Transition) and say what the client does in that phase.
- Assign a deliverable, including migration work, to one of the four workstreams.
- Pick the first-week governance actions and explain why the SOW is reviewed with the client's core team before kickoff.
- Set up "Slack delivered in Slack": a Slack Connect project channel, an internal-only team channel, topic, description, pins and bookmarks, user groups and asynchronous check-ins.
- Separate platform readiness from enablement readiness when assessing a launch.
Key terms:
- Phase: a time-boxed stage of the engagement with its own activities and deliverables.
- Workstream: one of four parallel tracks (delivery, experience, platform, learning and enablement) with its own roles and deliverables.
- Slack Connect channel: a channel shared between organizations, each staying in its own Slack environment.
- Launch readiness: the pre-launch check split into platform readiness and enablement readiness.
Key facts
Five phases
- Detail
- Prepare, Understand, Design, Launch, Transition
Client configures Slack
- Detail
- In the Design phase, after the setup is planned
Migration deliverables
- Detail
- Delivery workstream: overview, pre-migration planning, cleanup, execution
Week-one action items
- Detail
- Stakeholders, client constraints, shared document repository, hours vs budget
SOW review
- Detail
- With the core client team, before kickoff
Partner configuration access
- Detail
- Never, unless the SOW states otherwise
Project channel timing
- Detail
- Slack Connect channel set up before kickoff; private if the client has security concerns
User groups and externals
- Detail
- Guests and Slack Connect people can't be added to your user groups
Enablement readiness
- Detail
- Support model, training, communications and awareness
Sources for this section (5)
- Slack Project Plantrailhead.salesforce.com (opens in a new tab)
- Design a Statement of Worktrailhead.salesforce.com (opens in a new tab)
- Assemble a Delivery Teamtrailhead.salesforce.com (opens in a new tab)
- Deliver Slack with Slacktrailhead.salesforce.com (opens in a new tab)
- User groupsslack.com (opens in a new tab)
- Why should the Slack Connect project channel exist before the kickoff meeting?
- When does the client configure Slack to match the agreed grid, channels and settings?
- Which workstream owns pre-migration cleanup?
- Why can't a Partner user group include the client's stakeholders?
- Which three areas make up enablement readiness?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Slack Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 38 lessons of the Slack Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (10 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams