WARNING: This service only available for after the contract is sign and project base

In order to have a better collaboration between our customer and us, we have split our project management using eXterme Programming (XP) methodology and standard SDLC depending on the complexity of the project.

Below would be some of the standard term that you will be hearing from us. They are

• Concept Check Point (CP)
• Value CP
• Commitment CP
• Release CP
• Closure CP

In order to give you a better understanding, we put how we map our CP against SDLC.

0. Concept Check Point 1. Asses Needs/Design - Value CP 2. Develop/test- Commitment CP 3. Implementation/Support - Release CP 4. Evaluate Performance - Closure CP

Concept CP overview

Concept CP is use for engaging new project/idea. This will allow the customer and GCR team to understand each other better and work towards a common goal. Some of the tool we use is brainstorming via rich picture (UML) or prototyping. Please do take note that if the customer already have the design in hand, we will skip this process.

Below would be some of key area that concept cp will cover

• Some proposal on how the system will work (if any)
• Resources that might needed during this particular project
• Identify the project approval and sponsor
• Covering in/out scope for the system
• Desire timing (more like a high level of the project)

Value CP overview

Value CP is use for finalizing the end goal to ensure the customer really want this project and it will help us to put into value why this project is so important for the customer. We don't wish to do a project that might put our customer into a delima where their project doesn't provide the final result that they need or the customer doesn't even know why this project is so important to them.

Below would be some of the key area that value cp will cover

• Commitment of the team over the planning phase
• Explain over some of the business transformation that the customer will see
• Provide some of solution that we have bring over from concept cp* and the decision that we propose
• Provide some dependency of the project to ensure no problem to the project
• Sharing the expectation of return of investment for this project
• Sharing over the potential risk that the project might face
• Assumption that we might have during our project that require customer to advice or agree
• Review on the time line with more details
• To gain the success criteria from the point of the project owner
• Resource require
• Should we proceed to the next CP?

Commitment CP

During this stage, everything is finalize and this is where the fun begin. We will check all the party (including our internal vendor) is ready to work on this project. With this, we will be able to ensure the project will not delay unless unforeseen risk occur. We will be covering from development till testing in the stage

• Solution approach
• Scope review
• High level design
• Final review over the all key player roles and responsible with their due date
• Access risk items
• Review the time line for the project in details (if there where changes or its not clear enough in earlier stage)
• Review over the release criteria
• Remind all the team over the success criteria
• Should we proceed to the next CP?

Release CP

After all the hardwork over the development and testing, its time to publish out the result for everyone to review and have the final say before we release it to the live system. During this time, we will also finalize over the success criteria after the project have been deploy. For some customer, we will pass the deployment package to the customer for them to test it out over their side.

• Review all the dependancy and commitment progress (should be all done or some issues occur)
• Review over the test result for the system.
• Review over the final success criteria for the project (there will be no changes over the success criteria after this)
• Review all the risk item
• Approve all the release criteria have been met for release down to production
• Should we proceed to the next CP?

Closure CP

Close CP usually happen after a month the system have been release into live system. This month will be known as stablization period. The customer will be brought in and have a review on the success indicator that have been set and give the scoring from outstanding to fail. This is crucial stage for both party to have understanding what could have gone wrong and right.

• Scoring on the success criteria
• Some feedback from customer on what we have done right or wrong
• Key learning that we have learn from GCR team
• Officially close the project