Operate & Improve
Iterative Product Development
The thing is live and now it needs to keep changing.
Continuing development of a system that already exists, run as a sequence of agreed increments rather than a single project: prioritisation, build, release and review.
Suited to products that are live and earning, where the next thing to build is a decision taken repeatedly rather than once at the start.
Scope and commitment are set in the written agreement for the engagement.
What this covers
- Iterative product development
What you get
- Prioritised backlog
- Included
- Maintained with you rather than handed over.
- Agreed increments
- Included
- Built, reviewed and released.
- Release notes
- Included
- What changed, each time.
- Review cycle
- Included
- A point at which direction is reconsidered.
How it runs, and what it asks of you
The six stages are the same on every Gridsmith engagement. Where your own time is listed, it is the part of a project that is worth knowing before it starts.
- Consultation
- We look at the current system, who maintains it, where it is hosted and what actually needs to change.
- Planning & Scope
- Scope is written as what the system will do, what it will not do, and who owns each account and environment at the end.
- Approval & Start
- Work starts once scope is agreed. Repository, environment and access arrangements are settled first, on the terms the written agreement sets out.
- Design, Development & Updates
- Built in reviewable increments on an environment you can see, rather than revealed at the end.
- Delivery
- Handover covers the running system, written documentation of how it is deployed, and the source-code and account arrangements the written agreement sets out.
- Support (if applicable)
- Maintenance, monitoring and further development are scoped separately rather than assumed — as further work or as an ongoing engagement.