Back office on Oracle for a tolling and mobility technology group
Tested back-office code delivered sprint by sprint against the client's acceptance criteria.
Stack and topics
| Industry | Intelligent transportation and tolling |
|---|---|
| Region | North America |
| Scale | 2 engineers |
Context
The client and the problem
A global tolling and mobility technology group needed senior Oracle engineers inside its own team to build and change its back-office system, working to its standards and its security rules.
What we built
What did we build?
Our Oracle PL/SQL engineers joined the client's Scrum team on the back office.
- Back-office code. Oracle PL/SQL changes to the back-office system, tested against acceptance criteria agreed before each sprint planning.
- Design specifications. Every addition or change to the application architecture came with a design specification.
- Test cases. Test cases for every user story, recorded in Jira.
How we worked
Team and process
The work followed the client's Scrum: two-week sprints with planning, daily scrums, a review to show the work to stakeholders and a retrospective.
Code followed the client's coding standards, and every engineer worked under the client's information security framework, based on ISO/IEC 27000.
Facts
Project facts
| Fact | Detail |
|---|---|
| Client | A global tolling and mobility technology group |
| Region | North America |
| Team | 2 Oracle PL/SQL engineers |
| Process | Client's Scrum, two-week sprints, Jira |
| Controls | Client's ISO/IEC 27000 based security policy |
Result
Where it stands
Tested back-office code delivered sprint by sprint against the client's acceptance criteria.
Next step
Building something similar?
A 30 minute call with Oleg. You leave with a clear view of scope, risks and the next step.
Oleg Pun
CEO, Vareger
