Education platforms
Anonymized client caseEducation Management Recovery
Recovery and rebuild of a New Zealand student management system after a failed outsourcing attempt, with renewed roadmap control, government-aligned requirements, QA support, and long-term product delivery.
Delivery evidence
What this example shows about delivery.
The evidence type is stated clearly so readers can distinguish anonymized client work from a reusable architecture practice or representative delivery example.
Anonymized client case
New Zealand student management system
Failed 2017 build and lost source-code continuity
System launch and Ministry of Education verification
Client Context
A student management platform needed to support the full operating life of a school.
The source case describes a student management system for schools in New Zealand. It covered staff, student registration, curriculum, timetable, learning plans, attendance, finance, pastoral care, assessment, reporting, and configurable templates.
Because schools could receive private platform accounts after paying for the service, the system needed to be flexible enough for different school settings while still meeting education-sector requirements.
Problem
The first outsourcing attempt created a recovery project, not a normal handover.
- Initial requirements were unclear and some expectations were unrealistic.
- The original scope attempted to support New Zealand and Australia too quickly.
- Most UI pages were completed, but the back-end code was not finished.
- No source-code management was used, creating serious continuity problems after the deadline was missed.
Recovery Work
Shinetech helped turn the project back into a controlled roadmap.
After the failed 2017 build, the client reformulated the roadmap in March 2018 and began working with Shinetech. The team restored the old website, helped complete mockups, and discussed the business requirements in detail before rebuilding.
The team also reviewed New Zealand education authority documents to understand how the system should align with government requirements and interact with public-sector education systems.
Delivery Model
A four-person team combined .NET delivery, QA, and agile collaboration.
- Three .NET developers and one QA worked closely with the client's project leaders.
- AngularJS, ASP.NET Core, Azure SQL, and Azure Redis were used in the technology stack.
- Email, video calls, messaging, and on-site visits supported daily collaboration.
- Agile delivery helped reduce bottlenecks and respond to changing business needs.
Result
The platform moved from rescue mode into an approved operating system.
The Shinetech team successfully launched the system, and the case material notes that it was verified by the Ministry of Education. The client relationship continued into future features, which is the clearest sign that delivery trust had been restored.
Reusable lessons
What a similar engagement should clarify early.
- Map the business workflow and the roles that need different visibility.
- Confirm the data and access boundary before implementation.
- Choose a first release small enough to review and real enough to prove fit.
- Keep QA, documentation, handover, and ownership visible from the beginning.