Keep the product
moving forward.
A continuing relationship for teams that need application maintenance and regular product development in one visible working rhythm.
A useful fit
An existing mobile or web product with ongoing needs, a business owner for priorities and a backlog worth working through.
The shape of the scope
What we would
work through.
- An initial technical and product review
- A shared backlog and release plan
- Agreed maintenance and development capacity
- Regular reviews of delivery, risks and priorities
A shared view of what matters next.
The arrangement begins with the current product and its operating responsibilities. We review code access, environments, known issues and the existing release process before committing capacity.
Features, fixes and maintenance are prioritised together. The team can see what is in progress, what is blocked and which decisions need an owner.
A relationship with clear boundaries.
Capacity, working hours, support expectations and review points are written down. Larger changes are estimated separately when they exceed the agreed arrangement.
Documentation and source ownership remain part of the work. A continuing relationship should make the product easier to operate and evolve, including when another team needs to take over.
What to bring.
- A named product owner
- Access to code, environments and operating notes
- An initial backlog and business priorities
- Agreed capacity, coverage and release responsibilities
At handover
A maintained product backlog, working source, release history and operating documentation, with clear ownership if the relationship changes.
Begin with the situation.
Describe the app, the people who will use it and the task it should make easier.
Prepare a project outline