On the client's side of the table
When a vendor delivers your software, someone needs to represent you: owning scope, testing and acceptance. That is often our role.
GABCO field practice

Technology projects rarely fail on technology. They fail on unclear scope, missed decisions and vendors nobody is managing. A named project lead keeps all three under control and reports honestly on progress.
A project charter with objectives, scope, budget, roles and success measures, agreed before work starts.
A schedule with dependencies and milestones, a budget, and a risk and issue log.
Progress tracked, changes controlled through a simple approval process and risks managed before they become issues.
Suppliers held to the plan, their dependencies managed and their work accepted only against agreed criteria.
Regular status reports with an honest view of progress, risks and decisions needed.
Acceptance, handover to support, lessons learned and a closed budget.
Charter, scope and success measures agreed.
Schedule, budget, risks and resources set.
Work controlled, changes approved and progress reported.
Acceptance, handover and lessons learned.
When a vendor delivers your software, someone needs to represent you: owning scope, testing and acceptance. That is often our role.
GABCO field practice
From a single system upgrade to multi vendor programmes. The method scales; a small project gets a light version of the same controls.
Yes. We start with a short review of scope, plan, budget and vendor position, then agree a recovery plan with you.
Our approach draws on PMI and PRINCE2 practice, scaled to the size and risk of each project.
Tell us what you're working on. We'll listen, ask the right questions and recommend a practical next step. No obligation.