How we work
A project with InterEdu moves through five phases: clarifying the problem, agreeing scope and success measures, phased development with something usable each cycle, testing against a realistic operating scenario, and handover with documentation and training.
Five phases
Each phase ends with something you receive, not with a meeting.
- 01
Clarify the problem
A conversation to understand the context, the users, and the constraints. You do not need a finished requirements document for this.
You receive: A problem summary and the open questions - 02
Agree scope
Define the first-phase scope, how success will be measured, the engagement model, and the delivery milestones.
You receive: Scope, timeline, and contract model - 03
Phased development
Work in cycles, each producing something runnable for you to review, rather than one delivery at the end.
You receive: A working build each cycle - 04
Test against the real scenario
For an assessment system, testing has to model the real session: the expected candidate count, the actual device mix, and the situations that come up.
You receive: A test report against the agreed scenario - 05
Handover and transfer
Source code, operating documentation, and technical documentation, with training for the receiving team and a support period.
You receive: Source code, bilingual documentation, and training
What goes in the contract
These are agreed in writing before work starts rather than left as verbal understanding.
- Source code and intellectual property ownership
- Data access scope and security rules
- How each phase will be measured
- Termination terms and the handover plan
- Working language and overlap hours
Start at phase one.
All you need to bring is the context. The rest of the process is agreed together.