GCT Taiwan Project Management

GCT Project Management

We follow a rigorous quotation and project specification procedure. We plan out in detail how we will handle the job - breaking it down into component parts and quoting for each. We go over this project specification with the client, enabling the client to see how, when and at what price we will proceed. We only begin work once the client has signed off on the project specification.
This level of transparency eliminates disagreements and frustration. Both the client and ourselves know exactly what will be done, in what time and at what price. The client is protected against hidden or unexpected cost overruns, and everyone is protected from disagreements about what we are expected to accomplish.
Below is a sample flowchart of our processes for a medium-sized job. Quality assurance (QA) is built into the structure at every turn - we've learned getting it right the first time saves everyone time and money!

Phase 1 - Planning Project

MEET CLIENT
ascertain client needs

PM PLANS PROJECT
creation of project spec

MEET CLIENT
project spec explained

SPEC REVISION
any changes requested by client added to project spec

MEET CLIENT
project spec presented for final sign-off: Job begins

Phase 2 - Interface Design

DESIGN INTERFACE
expert design team produces beta version of interface

QA: PM INTERFACE CHECK
PM looks over interface

QA: DESIGN REVISIONS
PM requested revisions made

MEET CLIENT
design revision phase #1

QA: DESIGN REVISIONS #1
client revisions made

MEET CLIENT
design revision phase #2

QA: DESIGN REVISIONS #2
client revisions made

MEET CLIENT
completion sign-off for design

Phase 3 - Functionality

FUNCTIONALITY CODING
software coders begin work

QA: 2nd CODER CHECK
a second coder in office checks for quality

QA: CODE REVISIONS #1
revisions made & re-check by 2nd coder

QA: OUTSIDE CODE CHECK
a coder from another GCT office checks quality

QA: CODE REVISIONS #2
revisions made & re-check by outside coder

QA: PM INTENSIVE CHECK
PM does a comprehensive final check of all functionality

QA: CODE REVISIONS #3
revisions made & re-check by PM

MEET CLIENT
present to client

FAQ & Glossary:
Project Specification (Spec): A detailed and comprehensive plan laid out for the entire project. This is by far the most important part of any project - good planning eliminates problems later.

Project Manager (PM): The PM liases with the client, creates the project spec and manages the entire completion process.

Quality Assurance (QA): These are the processes and steps used to check the quality matches the clients needs. We build QA into every stage of development.

What are revision phases? These are stages in the development for correcting errors, bugs or implementing improvements.

Why a 2nd coder and an outside coder for QA? The 2nd coder is in the office, and hence more likely to keep any critical assessment limited to obvious bugs. The coder from another GCT office is not someone with a personal relationship to the original coder - allowing for more impartial critical assessment.

home > project management