
How we engage
How we work with you
Three ways to start, clear commitments on both sides, and working software you can try every sprint.
Why we work this way
Most custom projects don't fail on technology. They fail when the people who will use the system are left out of building it.
- 01
Built with your users
A specification records assumptions. Your users show us how the work is really done, so the system fits from the first release.
- 02
AI proven on your data
We measure accuracy on your own test set before roll-out. No document can promise it in advance.
- 03
Judged on business results
We agree outcomes such as cost, speed and service quality up front, and measure the work against them rather than a feature list.
- 04
Decisions at every sprint
You review working software every sprint, while changes are still cheap, instead of finding gaps at the end.
Three ways to start
Clients usually come to us with one of these three situations. Each has its own contract and its own way of working.
“We know exactly what we need.”
Fixed-scope project
Your requirements are clear and stable, such as a defined integration or a standard web system.
You get
- A fixed price and delivery date, agreed before we start
- Acceptance criteria you sign off against
We'll need from you
- Agreed requirements and acceptance criteria
- One contact for questions and acceptance
Contract: Fixed-scope contract (請負)
“We need something built around how we work.”
Agile partnership
You need a tailored system and your team can take part in every sprint.
You get
- A system shaped with your real users that keeps fitting as you grow
- Shared targets tied to your business results
- Working software every sprint, with an open backlog
We'll need from you
- A product owner who can make decisions
- Your users at sprint reviews
- Access to masked or sample data
Contract: Agile quasi-mandate (準委任)
“We want to see if it works first.”
Proof of concept
Your idea is promising but unproven, or you aren't ready to commit a team yet.
You get
- Evidence on your own data within weeks
- A fixed time box and price
- A clear go / no-go decision and a plan for what comes next
We'll need from you
- The question the PoC should answer
- Sample data and someone to review results
Contract: Paid, time-boxed PoC
Many partnerships begin as a proof of concept or a fixed-scope project, then grow once both sides have seen results.
What each side commits to
In an agile partnership both teams are accountable, and both commitments are written into the agreement.
Your team
Our team
Results
Your team
Business results: sales or usage, operating cost and service quality.
Our team
Delivery results: handling time, accuracy on an agreed test set, and a working release every sprint.
People
Your team
A product owner, the operators and end users who will use the system, and a data contact. Your IT team if needed.
Our team
A solution architect, cloud and AI engineers, development and DevOps, QA and security testing. Design and infrastructure if needed.
Every sprint
Your team
Decisions within the agreed number of days, attendance at the sprint review, and feedback recorded in the backlog.
Our team
A working release, an open backlog, a written record of every change, and training so your team can run the system.
Targets are set together, measured against your own starting point.
If either side falls behind
Neither of us keeps spending on a project that has gone off track. The same clause applies to both sides.
On your side
- Decisions overdue past the agreed days
- Sprint reviews missed two sprints running
- Data or user access not provided
On our side
- Sprint commitments missed twice
- The agreed team not available
- Quality checks failed repeatedly
What happens next
- 01Written notice to pause
- 02A new plan within agreed days
- 03Resume, change scope or close
How a project runs
Every project is a set of cycles inside cycles. Each highlighted step opens into the level below, from the whole engagement down to a single change.
1Engagement
One agreement, delivered phase by phase
You commit one phase at a time, and decide at each gate whether to continue, adjust or stop.
- Agreement
- Phase 1
- Gate
- Phase 2
- Gate
- Next phases
- Agreement
- Phase 1
- Gate
- Phase 2
- Gate
- Next phases
Inside Phase 1
2Phase
Requirements, sprints, delivery
Requirements get better with real use instead of being frozen on day one.
- Requirements
- Sprint 1
- Sprint 2
- Sprint 3
- Sprint 4
- Delivery
- Requirements
- Sprint 1
- Sprint 2
- Sprint 3
- Sprint 4
- Delivery
Inside Sprint 2
3Sprint
One plan-do-check-act cycle
Working software to try at the end of every sprint, with your feedback deciding what comes next.
- Plan togetherPlan
- Build and releaseDo
- Review with usersCheck
- Learn and adaptAct
- Plan togetherPlan
- Build and releaseDo
- Review with usersCheck
- Learn and adaptAct
Inside every build
4Change
Every change, checked before your users see it
Fewer defects reach your users, releases become routine, and problems are caught early.
- Task
- Pull request
- Code review
- Tests and security
- Merge
- Staging and QA
- Production
- Monitoring
- Code to merge
- Task
- Pull request
- Code review
- Tests and security
- Merge
- Release and monitoring
- Staging and QA
- Production
- Monitoring
Already use PDCA, Lean or OODA? Our sprint follows the same four steps.+
| Our sprint | PDCA | Lean Startup | OODA |
|---|---|---|---|
| Plan together | Plan | Ideas | Decide |
| Build and release | Do | Build | Act |
| Review with users | Check | Measure | Observe |
| Learn and adapt | Act | Learn | Orient |

Get started
Start building smart
with Oriental Nippon today
Book a 30-minute call. We'll suggest a team, an engagement model and a first milestone.
Book a call