Project management

Communication Management

• All engineers communication with the client directly if necessary email, instant message tool;
• Regular meeting (between team members or with the client) by Gotomeeting, phone call, remote desktop;
• In ODC model, daily report of every team members is required (report function is available in PMS);

Plan Management

• Iteration development plan
  The plan will contain not only the implementation tasks but all the activities required for achieving the iteration objectives; for instance, quality assurance activity, training, etc. Once iteration begins, it is project manager’s duty to track task status continuously. If change on original development plan is inevitable due to unexpected difficulty, project manager will discuss and re-evaluate current status with the client immediately, then make adjustment decision together.
• Milestone development plan (we could help to make if necessary)
  It may contain several iterations. Closer iterations have clearer goals and detailed plan.
• Product development roadmap (we could help to make if necessary)
  It may contain several milestones. Closer milestones have clearer goals and detailed plan.

Risk Management

Our iterative process enables the team to manage project risks in a very effective way. With the development process, some new risks may be found and some old risks would be resolved. (By old risks, we mean those ones identified in earlier iterations.) After analyzing the risks at the end of iteration, the risk list could be updated. Normally a top-ten risk list is efficient for the team to monitor and control the significant ris

Item	Description
ID	The identify of the risk
Description	Describe the risk in brief
Impact	What the impact will be if the risk takes place
Severity	The severity of the risk, can be High, Medium, Low
Probability	The probability the risk can occur
Priority	The priority in which the risk should be planned to resolve
Mitigation Plan	How the risk will be mitigated
Contingency Plan	What should be done if the risk really occurs

Requirement Management

The right understanding comes from sufficient communication. And priority policy must be adopted in requirement management. The followings will be considered in change control:

• Technical evaluation;
• Work amount re-evaluation based on historical record of PMS;
• Cost re-evaluation;
• Risk re-evaluation;
• Requirement priority re-evaluation (Make sure high priority tasks always receive the most attention and will be completed first.);
• Discuss with the client our adjustment plan and get approval.

HR Management

We have a large talent pool in house. And we also keep constant contact with potential talents with particular technology background. They may join us with short notice if some project needs. To built win-win relationship between Shinetech and the employees, a self-grow atmosphere is created for them by:

• Our engineers get the best offer in the software industry in China.
• Staff's holding shares policy.
• Career promotion roadmap.
• Welfare increase plan. (including insurance package, dining compensation, comfort working environment, annual paid leave).
• Training and education opportunity.

In 2007, our overall staff turnover is 8.33%, which is much lower than the average in the industry.

Configuration Management

Configuration Management (CM) Plan describes all Configuration and Change Control Management (CCM) activities that are performed during the course of the product or project lifecycle. It details the schedule of activities, the assigned responsibilities, and the required resources, including staff, tools, and computer facilities.

To know more about Shinetech, please download here:
How we guarantee code quality
Methodology and technical approach
Shinetech QA process management whitepaper

back