| What changes? | The planned release. Suits you best when the outcome has clear boundaries; if the roadmap is likely to keep shifting, we will recommend a dedicated team after scoping. | The product roadmap, sprint by sprint. Suits you best when priorities evolve over several releases; if you only need one bounded release, we will recommend fixed-price delivery after scoping. | Your own team's capacity. Suits you best when your engineers already have a roadmap and process and lack specific skills; if you also need delivery management, we will recommend another model after scoping. |
|---|
| Who plans? | You and Netofficials plan together against a statement of work covering scope, acceptance criteria and milestone schedule. Work outside it goes through a change request. | You and Netofficials plan the roadmap together and reprioritise at each Scrum sprint boundary | Your delivery leads set priorities and process, and our engineers work in your tools |
|---|
| What is agreed? | Scope, acceptance criteria, milestone schedule and total cost in a statement of work, with change requests for anything outside it | Team makeup, full-time capacity, sprint rhythm and communication window, with you owning the source code and IP from the start | The role, responsibilities, onboarding steps and communication window for each engineer joining your team |
|---|