How We Take A Product From Idea To Launch
Six stages, each with a clear output. You see working software throughout, and nothing is a surprise at the end.
The Six Stages
- 1Stage 1
Discovery
We agree the goals, the users and the must-have features. The output is a written scope that both sides sign off, along with open questions and risks.
- 2Stage 2
Design
User journeys, wireframes and screen designs. You try a clickable prototype and ask for changes while changes are still cheap.
- 3Stage 3
Plan
The scope is broken into sprints. We agree the architecture, the environments and how work will be reviewed.
- 4Stage 4
Build In Sprints
Short cycles, each ending with working software you can try. Code is reviewed and kept in your repository from the first day.
- 5Stage 5
Test And Launch
Testing of the agreed journeys on real browsers and devices, then a planned release with a way to roll back.
- 6Stage 6
Support
Fixes and improvements after launch on agreed terms, or a documented handover to your own team.
What You See And When
You should never have to ask how the project is going.
Sprint Plan
What will be built in the coming sprint, agreed with you before it starts.
Sprint Demo
Working software shown at the end of each sprint, for you to try.
Written Updates
Progress, decisions made and anything that needs your input.
Your Repository
Every change visible in your own repository as it is made.
Who Is Responsible For What
Stated before work starts, so nothing falls between the two sides.
You
- Product goals and priorities
- Feedback on designs and demos
- Access to systems and subject experts
- Acceptance of delivered work
SyntecHire
- Design, development and testing
- Planning and progress reporting
- Code quality and review
- Documentation and handover
How We Keep Quality High
Code Review
Every change is read by a second engineer before it is merged.
Automated Tests
Checks run on every change, so a fix in one place does not break another.
Staging Environment
Changes are tried in a copy of production before they are released.
Documentation As We Go
Setup, architecture and decisions are written down during the work, not after it.
Security Basics
Named access, secrets kept out of code and dependencies kept up to date.
Rollback Plan
Every release has a tested way back.
What Is Yours At The End
Source Code
In your repository, with the full history.
Documentation
How it is built, how to run it and how to release a change.
Accounts
Hosting, domains and app store listings in your own accounts.
IP
Assigned to you by contract.
Process Questions
Usually one or two weeks. We agree the length with you at the planning stage and keep it the same through the project.
You review designs, attend a short demo at the end of each sprint and answer questions as they come up. We keep the time you need to give as low as the project allows.
Changes are normal. On a time and material engagement they are planned into the next sprint. On a fixed-scope engagement we write up the effect on time and cost and you approve it first.
We work in your tools if you have them. If not, we set up a board, a repository and a shared channel, and transfer them to you at the end.
Work is documented as it is done and code is reviewed by more than one engineer, so knowledge is shared. If someone changes, the handover is written and we cover the overlap.
Ready To Start With Discovery?
Tell us what you want to build. The first call carries no obligation and ends with clear next steps.