01. The brief sets the finish line.
Help the person organizing staff training understand the course and request a relevant proposal. The approved offer is the starting point. A general brand strategy is outside this Sprint.
| Deliverable | Included in this example | Accepted when |
|---|---|---|
| Campaign landing page | Course context, audience, practical information and one inquiry route. | The course expert approves factual content; the coordinator approves the page and mobile flow. |
| Inquiry form | Agreed fields, delivery destination and confirmation. | A test inquiry reaches the agreed destination and the visitor sees confirmation. |
| Campaign assets | Three approved message angles, each adapted to square, portrait feed and vertical placements. | All nine exports match the approved message, format and placement requirements. |
This example excludes ad spend, ongoing campaign management and a full website rebuild. Actual scope may be narrower or wider.
02. Feedback has a place in the schedule.
The coordinator gathers one set of feedback at each agreed review. The course expert validates accuracy. NOT MORE. connects copy, design and implementation and records the decisions.
Before production
Confirm the offer, source materials, access and the person who can approve. Record unanswered questions before they become rework.
At the prototype
Review the message and page structure before producing all formats. Resolve conflicting comments through the named decision-maker.
Before launch
Check the inquiry journey, final content and exports. An extra course or new audience is assessed as a scope change.
The proposal defines review rounds and response windows. This illustrative four-week schedule is not a promise for every project.
03. The handover is a working inventory.
The receiving team can find the files, understand their purpose and see who handles the next step.
| Item | What accompanies it | Next owner |
|---|---|---|
| Published page and form | Approved copy, component notes, destination settings and the agreed test record. | Client website owner |
| Creative files | Nine labeled exports, agreed editable files and notes on their intended placements. | Client media team or appointed agency |
| Access and dependencies | Access transferred securely, asset/license conditions and any items still pending. | Client coordinator |
| Launch checklist | Checks completed, unresolved items and the review date specified in the proposal. | Named project leads |
A completed technical test confirms the implementation works in the tested conditions. It does not establish how many inquiries the campaign will generate.
04. Completion and performance are different checks.
In this example, the Sprint is complete when the agreed page, form and assets meet the acceptance criteria and the handover is finished. Commercial evaluation follows once the campaign has suitable traffic and sales feedback.
If the form fails
Record and address the defect through the support arrangement in the proposal.
If inquiries are unsuitable
Review the message, audience, offer and sales feedback before deciding the next intervention.
If the client adds a course
Assess the extra content, formats, approvals and timing, then agree on the change before producing it.
Support duration, revisions and later optimization are agreed for the actual project. They are not implied by this example.
A useful handover tells the receiving team what is ready, how to use it, what still depends on someone else and who takes the next step.