Governance
Delivery governance and responsibilities
Defined roles and clear responsibilities govern every project, from scope approval to operations and support.
Project roles
Who does what across the project cycle
Each role is assigned to a named owner in the project plan, and the team size follows the system's scope and sensitivity.
Project lead
The institution's first point of contact and owner of the work plan. Keeps decisions, risks and scope changes visible from start to finish.
- Project plan and phases
- Tracking decisions and risks
- Managing scope change requests
- Progress reports to the institution
Business analysis
Turns the institution's procedures into requirements that can be built and tested. Works with users to confirm the design before development.
- Documented procedures and roles
- Requirements and acceptance criteria
- Permission matrix
- Design review with users
Engineering & development
Designs the data, architecture and integrations, and builds the modules. Technical decisions are documented for maintenance.
- Data model and architecture
- Modules and integrations
- Code review
- Technical documentation
Quality assurance
Verifies that every release matches the requirements before it reaches the institution. Feedback is tracked until it is closed.
- Test plans and scenarios
- Functional and permission testing
- Tracking feedback to closure
- Checks before and after each release
Operations & support
Prepares the production environment and follows the system after launch. Trains users and administrators so the institution can run it.
- Hosting, backup and recovery
- Monitoring and alerts
- Receiving and resolving issue reports
- User and administrator training
Governance rules
How we protect scope, quality and the institution's decisions
Fixed rules we apply in every project, whatever its size.
- Implementation starts only after scope and acceptance outputs are approved.
- Every significant scope change is documented and its impact assessed before approval.
- Data and permissions are reviewed as core requirements, not add-ons.
- Every release is tested before it reaches production.
- Handover includes documentation and training, not code alone.
- Each project's status is shown as it is on the projects page.
Need a role structure for an institutional project?
We propose the roles and governance based on the project size, data sensitivity and your acceptance parties.