A government software project in Malaysia usually moves through six stages: procurement, kick-off, requirements study, development, testing and go-live, followed by a warranty period. Knowing what each stage should produce helps an agency hold its vendor to account and helps a vendor price the work honestly.

Before the award

The agency publishes a specification and invites quotations or tenders. Which method applies depends on the contract value under current Treasury rules, so check the latest circular. Vendors answer with a price, a schedule, a technical proposal, team résumés and proof of registration with the Ministry of Finance.

The stages after award

  • Kick-off: scope, schedule, contacts and reporting are confirmed
  • Requirements study: the vendor documents how the service works today and what the system must do
  • Design: architecture and screen prototypes are approved before building
  • Development: built in stages, each one demonstrated to the agency
  • Testing: unit testing, then user acceptance testing by the agency's own officers, then security testing
  • Go-live, training and handover of documentation

What good testing looks like

User acceptance testing should start only when the system is already largely working, and it should be carried out by the officers who will use it. Critical and high-severity defects are closed before go-live. Development, testing, UAT, staging and production should be separate environments, so a test never touches live data.

After go-live

The warranty period, commonly twelve months, covers defects in what was delivered. Training and transfer of technology matter as much: the agency's team should be able to manage content, users and backups without calling the vendor.

Questions

How long does a government portal project take?

It depends on scope. A portal with public and internal modules, data migration and training is typically planned over several months to a year, with the schedule fixed in the specification.

What makes these projects fail?

Most often an unclear requirement that is discovered late. A thorough requirements study and early prototypes cost little and prevent most disputes.

Sources