All projects

01 · Asset Management · Government

Asset Management System for a Regional Government Entity

Scope, schedule, risk tracking, and release coordination across technical and functional teams.

Domain

Asset Management

Client type

Regional government entity (anonymized)

Duration

9-12 months

Role

PM

Problem

Multiple teams worked on application modules, database setup, and infrastructure at the same time, so milestones, client approvals, and scope changes needed one owner.

What I did

  • Built the project schedule and tracked weekly tasks across BA, UI/UX, Developer, DevOps, DBA, and infrastructure.
  • Kept risk logs, issue logs, status reports, and meeting minutes current after each client sync.
  • Reviewed incoming change requests to estimate timeline and effort impact before asking the client for approval.
FIG 01 · End-to-End Delivery Lifecycle9-12 months · 7 phases
  1. 01Initiation
    Scope & kickoff
  2. 02Requirements
    BRD, FSD & flows
  3. 03Build
    Dev & QA tracks
  4. 04SIT
    Integration test
  5. 05UAT
    Client sign-off
  6. 06Go-live
    Cutover & launch
  7. 07Support
    Handover & care
Client approval / milestone gatePrimary delivery track

Documents produced

  • Project Plan & Schedule
  • Risk & Issue Log
  • Weekly Status Reports & Meeting Minutes
  • Change Request Impact Notes

SIT, UAT & go-live

Coordinated SIT completion, client UAT scheduling, go-live preparation, and post-release support.

Outcome

Delivered the agreed project scope through regular milestone checks, documented change approvals, and coordinated release handoff. TODO(owner): Add verified outcome metrics or approved highlights.

Takeaway

Writing down the schedule impact of a change request early makes client sign-off conversations straightforward.