Specialist sprints: one mission, one timebox, one exit
A specialist sprint brings in expertise your team lacks for one named mission, such as recovering a compromised store, migrating a platform or reviewing an architecture. Before work starts you agree the mission, the timebox, the written deliverable and the exit condition. When the condition is met, the sprint ends, whether or not more work could be found.
Submit a project Scope a technical audit sprintReviewed by David Nguyen (CEO) · Updated 28 Sep 2026
OutsourcingVN is operated by Netbase JSC. Netbase leads with fixed-scope projects agreed after discovery, with milestone-based arrangements also available, and offers dedicated development teams, on-demand support and fully managed delivery as secondary options. A specialist sprint is the smallest bounded form of that offer: a short project with a single purpose, not a seat on your team.
When is a sprint the right shape?
Choose a sprint when the gap is expertise, not headcount, and the mission can be described in one sentence with an end state. "Find out why the store is serving malware and give us a recovery plan" works. "Help the team with security" does not, because nobody can tell when it is finished. If the need is a larger build, a project under Custom Product Engineering fits better; if it is continuing improvement of a live system, see managed outcomes. The engagement models page compares every model Netbase offers.
What does a sprint charter contain?
-
Mission
- What to write
- One sentence with an end state
- Example
- Produce an infected-file report and a recovery plan
-
Timebox
- What to write
- Working days, fixed before start
- Example
- Ten working days
-
Deliverable
- What to write
- The artefact you keep
- Example
- Written report, plan, migrated system
-
Exit condition
- What to write
- The test that ends the sprint
- Example
- Report accepted, or timebox reached with findings documented
-
Access
- What to write
- What the specialist may touch, and until when
- Example
- Read-only production logs, ending on the last day
-
Follow-on rule
- What to write
- How further work is decided
- Example
- Scoped separately, after the deliverable is accepted
The technical audit sprint is one ready-made charter of this kind: a bounded review that ends in a written report.
What do the Netbase records show?
For an existing client store, Netbase scoped a three-phase recovery of a compromised Magento site: investigation with an infected-file report and recovery plan, then cleaning and system recovery, then file restore, recoding and hardening. The whole recovery typically takes 6 to 13 days depending on the damage, and it carries no guarantee of full recovery. The Magento recovery and hardening record shows a mission with a phase-by-phase exit.
For Netztech, Netbase delivered a Magento 1 to Magento 2 Commerce migration in 35 working days, including migrating 11 extensions with installation, configuration, customization and data transfer. The Netztech migration record shows a longer mission that still had a fixed scope and a clear end.
Both records are bounded platform missions. Netbase has no published record of a sprint in other specialisms, so this page describes how such sprints are chartered rather than a history of them.
Worked example: a payments review before a launch
A subscription business plans to switch payment providers in six weeks and has no one in-house who has done it. The charter reads: review the current checkout and webhook handling, list what must change for the new provider, and deliver a migration plan with risks rated. Timebox: eight working days. Exit: the plan is accepted by the CTO. On day five the specialist finds an undocumented refund job that depends on the old provider. It goes into the plan as the highest-rated risk rather than being fixed on the spot. The sprint ends on day eight; building the migration becomes a separate, scoped project that the business can give to anyone.
What about specialist leadership rather than a task?
Some gaps are about direction, not delivery. Netbase provides fractional or interim CTO, CIO and Chief Digital or Transformation Officer services, including an AI transformation lead, and independent technology advisors who sit with a client's executive team, advisory board or board of directors. These are structured as agreed days each month over a 3 to 12 month term, with written objectives and a handover to a permanent hire. This is an offer, not a track record, and no advisor or mandate is named here. Where an advisor recommends Netbase delivery teams, that interest is disclosed, the client decides, and the advisory role can be contracted separately from delivery.
Questions to ask any specialist provider
- What is the exit condition, in one sentence? If it cannot be written, the sprint is not ready.
- What will I hold on the last day that I did not hold on the first?
- Who exactly will do the work, and what have they done of this kind?
- What access do you need, and when does it end?
- If you find more work, how is it proposed, and can someone else do it?
What goes wrong with specialist sprints?
-
The mission drifts into staffing
Signal: the specialist is added to daily stand-ups and picks up tickets. Owner: your sponsor, who holds the charter.
-
Findings fixed inside the review
Signal: the reviewer starts changing code. Owner: the provider, who reports first and fixes only under a separate scope.
-
Timebox extended by habit
Signal: "just one more week" without a new charter. Owner: both sides, who either close or recharter in writing.
-
Access outlives the sprint
Signal: credentials still active a month later. Owner: your system owner, who revokes access on the exit date.
Common questions
As long as the mission needs and no longer. The Magento recovery Netbase scoped typically takes 6 to 13 days depending on the damage, while the Netztech migration took 35 working days. The timebox is fixed in the charter before work starts and changes only by written agreement.
No. Staff augmentation adds a person to your team under your direction for as long as you need them. A specialist sprint is a small project with its own deliverable and exit, and the provider stays accountable for the result. The project outsourcing versus staff augmentation guide explains the wider difference.
Yes, but only as a separate decision after the deliverable is accepted. The sprint report should be usable by any provider, so you can take the follow-on work elsewhere or do it in-house without losing what the sprint produced.
It uses the same written cadence as any Netbase engagement, compressed: a start-of-sprint agreement, short written updates, and a closing review against the exit condition. The remote delivery governance guide covers cadence and escalation in more depth.
Netbase stays accountable for every sprint. Delivery is remote-first, and teams may combine Netbase staff, approved specialists or disclosed partners; the charter names who will do the work; global delivery explains how distributed teams are composed.
Name the mission
Describe the gap, the end state you need and the date it matters. OutsourcingVN is Netbase's own outsourcing-services platform; submit a project and a person will reply with a draft charter or a reason a sprint is the wrong shape.