About

The Governance Framework

In higher education, delivering a software platform on time and within budget is meaningless if the final product is heavily corrupted by uncontrolled customizations or rejected by its intended end-users. Project failures are often not strictly due to poor programming, but rather a breakdown in governance.

  • Scope Baseline Enforcement: Achieved through a dynamic Requirements Traceability Matrix (RTM).
  • Algorithmic Change Control: Replaces subjective "gut-feeling" decision-making with a matrix that evaluates technical complexity and operational disruption.
  • Evidence-Based Quality Gating: Establishes non-negotiable exit criteria before live deployment.

At Njala University, recent large-scale IT deployments, such as the Management Information System (MIS), have encountered severe user resistance, operational friction, and continuous ad-hoc feature demands. Administrative departments frequently resist standardized workflows, leading to mid-project scope volatility. Furthermore, software developers, pressured to meet strict academic calendar deadlines, routinely bypass critical handover protocols, resulting in systems being deployed before users are trained or disaster recovery plans are documented. This research proposes the GQGF to resolve this critical disconnect, acting as an administrative gateway that enforces a dual-module safeguard.

Explore Core Features

Algorithmically quantifies mid-project feature requests to prevent excessive, unstable customizations.

Processes requested modifications through a weighted matrix evaluating technical complexity and operational disruption.

  • Computes an aggregate Change Severity Score to automatically route feature requests based on their potential risk.
  • Replaces subjective decision-making with an Algorithmic Change Control matrix.
  • Intercepts scope creep to prevent the waste of institutional time and resources associated with endless software customizations.

This intake CRUD allows stakeholders to submit mid-project Change Requests, actively intercepting scope creep to prevent heavy custom coding that degrades standard architecture.

Computes an un-cheatable Release Readiness Index (RRI).

A computed percentage score generated by the GQGF that quantifies a project's preparedness for live deployment based on the submission of mandatory artifacts.

It applies hard system locks that block production deployment until the RRI reaches the 90% institutional threshold.

  • Ensures systems are not handed over informally without validated end-user training, avoiding staff resistance.
  • Safeguards the university's centralized database—critical to five campuses—against irreversible corruption.
  • Transitions software deployment from an informal process to a structured, defined standard.

Provides an asynchronous voting interface for designated CAB members.

A digital Change Advisory Board (CAB) workflow supporting asynchronous review and consensus voting for proposed scope modifications.

  • The CAB is a designated group responsible for reviewing, authorizing, or rejecting high-risk changes.
  • Enforces baselines effectively by centralizing change control, learning from macro-failures like Lidl's abandoned €500 million ERP transformation.

Requires administrative and technical stakeholders to govern internal IT projects.

Enforces a mandatory digital artifact repository before validation pillars can be approved.

A mandatory digital artifact repository workflow requiring distinct, strict approvals. Operational Sponsors must submit UAT and training logs for Sector Director clearance.

Project Managers must submit database backups and infrastructure recovery plans for DBA and CSO clearance.

  • Improves cross-departmental adoption by proving end-user training is complete through uploaded logs.
  • Mitigates data loss and downtime by mandating DBA/CSO-audited rollback scripts and infrastructure recovery plans before launch.
  • Removes ambiguity and establishes absolute accountability by demanding specific audits from administrative leadership before go-live.

Modules

Operational Capabilities

Administrative Gateway

Acts exclusively as an administrative and governance gateway to govern internal IT projects, optimized for Njala University stakeholders.

Requirements Traceability

Demands immutable functional requirements at project initiation through a dynamic Requirements Traceability Matrix (RTM).

Readiness Clearance Certificate

Generates un-editable PDF readiness certificates that map finalized deployments back to their authorized baseline scopes, proving all quality gates were passed.

Centralized Database Protection

Safeguards the centralized database serving the Njala, Bo, Freetown, Pujehun, and Bonthe campuses from corruption or data loss.

Quality Gating Checklists

Establishes non-negotiable exit criteria checklists that a project must pass before moving to live deployment.

Immutable Baseline Tracking

Integrates baseline project scopes to prevent continuous, uncontrolled changes or additions after initial setup.

Frequently Asked Questions

System Guidelines

The Release Readiness Index (RRI) is a computed percentage score generated by the GQGF that quantifies a project's preparedness for live deployment based on the submission of mandatory artifacts. The system applies a hard lock that blocks production server migration until the RRI reaches the 90% institutional threshold.

It replaces subjective decision-making with an Algorithmic Change Control matrix that evaluates technical complexity and operational disruption. This generates an aggregate Change Severity Score to automatically route feature requests based on their potential risk.

The system demands specific audits from administrative leadership. Mandatory artifacts include User Acceptance Testing (UAT) forms and training logs submitted by Operational Sponsors for Sector Director clearance, and database backups and infrastructure recovery plans submitted by Project Managers for DBA and CSO clearance.