Development Process

The ultimate goal of the project development process is to obtain the project quality, efficiency and reliability.

In a specific project, the differences of developing content, project nature, project team, customer demands, etc, will influence the development process selections. We absorbed a mature theory of the development process, combined with our own experiences; implement the deep analysis of each project, and negotiate with client to determine the appropriate development process that make sure to meet project’s demands.

Agile

CMMI5

Agile

We apply the Agile module in many development processes. becaruse variety project requierments, we need to maximum our "Flexibility". In order to confront the rapid changes, we cannot be allowed stick to tedious, but have to respond quickly to the changes.

As to The Agile Module implementation, it is not only to follow the trend, even not for quick respond to the agile, however, Agile Module comes from the real demands. Here, we write the following Declaration:

- Individuals and interactions over processes and tools

- Working software over comprehensive documentation

- Customer collaboration over contract negotiation

- Responding to change over follwing a plan

Different from the traditional engineering approach, our Agile Module, at the initial team establishment stage, focuses on staff capability. That is, build the best team;arrange appropriate skill Collocation to face the different project demands, rather than over-reliance on the heavy processes. Meanwhile, the strict plans will be replaced by the flexible adaptations. During the changing environment, project team has to take the advantage of its own abilities to adopt changes.

Our Agile practice as following:

Product backlog - all the tasks will be listed in accordance with the priority, and to establish product development program baseline.

Quick Demo - develop the Demo rapidly and implement the verification, then get the customer feedback within the shortest possible time.

Sprint - usually define as 3 to 4 weeks to complete iteration.

Multi - disciplinary team--person is the most important aspect in Agile Module, our team constituted by capacitive and aggressive staff.

Daily meeting - the simple meeting will be hold every day, in order to inspect and solve problems.

Close cooperation - the team member will be work in the same office as much as possible.

Communication - face to face/phone communication will be encouraged, try to reduce email, to emphasize the communication density.

Frequently submission - deliver the operational software as far as possible, which to get more clients' feedbacks.

Appropriate amount of documentation- not entirely abandon the document, but present the must and core document.

The Agile projects typically have the following characteristices:

- The scale of the project team is around 10 persons.

- The project key person get ready, and meets the demands.

- Demands changes frequently.

- Client unable to provide the written, high quality requirement specification.

- The business model is usually Time and Material model.

CMMI5

Based on the CMMI5 theory, we define our own development process:

Techome china highly conforms to this developing process specification in most of our projects, in all aspects of a project life cycle including requirement gathering, analysis, high level design, detailed design, coding, unit/integration/ system/UAT testing. Along with each phase, the following formal deliverables will be produced.

- Requirement Gathering Phase

Entry point: The project proposal is approved.

Exit point: Product Requirement Specification (Abbreviated as PRS) has been finished, reviewed and approved.

Documents: PRS including some critical Use Cases.

- Requirement Analysis Phase

Entry point: The original PRS is approved.

Exit point: The Use Case Formula has been finished, reviewed and approved; the Requirement Tracking Matrix has been set up and approved.

Documents: Use Case Formula, Requirement Tracking Matrix, and Requirement Changing Tracking.

Delivery: Use Case Formula, Requirement Changing Tracking.

- High Level Design Phase

Entry point: All the documents (Project Schedule, PRS, Use Case Formula, and Requirement Changing List) produced in the requirement phase are approved, or iterative process of requirements is approved for projects with several phases.

Exit point: High Level Design (Abbreviated as HLD), GUI Prototype and Test Plan have been finished, reviewed and approved, or the iterative process of HLD has been approved.

Delivery: High Level Design, GUI Prototype and Test Plan

- Detailed Design Phase

Entry point: HLD is approved or the critical part is approved.

Exit point: Detailed Design (Abbreviated as DD), Test Cases have been finished, reviewed and approved, or the iterative process of DDs has been approved.

Delivery: Detailed Design, Test Cases.

- Coding Phase

Entry point: Detailed Design is approved.

Exit point: Requirement coverage reaches 100%, the coverage for code review, unit testing are up to 100%; all the defects are resolved and verified.

Delivery: Bi-weekly Build, Build Notes.


- Unit Testing/Integration Testing/System Testing Phase

Entry point: Coding phase is finished; Test Plan and Test Cases are approved. System testing can be started after integration testing is finished, which requires unit testing being passed.

Exit point: Requirement coverage reaches 100%, all of the defects with major/critical/normal level are resolved and verified.

Delivery: Source Build, Bug List, Test report, Release Notes.

- Deployment

Entry point: Once the system testing is finished and passed criteria set in test plan. Deployment Plan has been approved. Data preparation work is finished

Exit point: System goes live

Delivery: Deployment Plan, system goes live report

- Project Closing

Entry point: System goes live

Exit point: Finish end user training, system runs smoothly for 1 month and generate reports correctly.

Delivery: Training report, User Manual, Administrator Manual

- Maintenance

Entry point: System is transferred to customer, UAT is complete

Delivery: Maintenance report, troubleshooting report