Conby Information Technology Co., Ltd.

Thank you for considering to get started with CONBY. We have a well-established new project development process that will help you get started with a realistic schedule and an affordable budget. Our new project process involves the following steps:

REQUIREMENTS INTERVIEW

First we will want to know what you wish us to deliver -- the goal of the project. Typically, the goal is to develop a new software solution.

In the interview phase, we will gather as much information as possible to capture the big picture and the key details that define the project. The interview process will involve the stake holders on your side and can be as simple as a few phone interviews, face-to-face meetings, and/or web sessions of other existing products or services.

Typical Timeline: the interview process typically involves anywhere from 3 person days to 5 person days.

Deliverables: good mutual understanding of the project.

SCOPE OF WORK DEVELOPMENT

The Scope of Work (SOW) represents the most critical documents in the project. The SOW consists of the details of what we are supposed to produce per an established Software Requirements Specifications (SRS).

If you do not have an existing Software Requirements Specifications document, the SOW development phase will also include SRS development, without which no software should ever exists.

Typical Timeline: the typical SOW/SRS process can be anywhere from 5 person days (1 calendar week) to 10 person days (2 calendar weeks).

Deliverables:

Scope of Work Document
Software Requirements Specifications Document
Version 1.0 Base System Requirements (derived from SRS)

MILESTONE DELIVERY SCHEDULE

In this phase, we will develop a realistic schedule for the entire project with milestone deliverables and a team will be assigned for project management, development and quality assurance. A project site will be established to allow team communication to be tracked and directed as appropriate.

Typical Timeline: 3 person days

Deliverables:

Milestone Breakdown with Planned Schedule
Project Site
Team Roster
Communication and Reporting Procedure

The Planned Schedule will provide projected date for Alpha, Beta and software Release.

Note that the team assignments will include Project Manager (CONBY), Project Manager (Your organization), Software Architect, Development Team Members, and QA Team Members.

The communication and reporting procedure will include how development updates are reported (typically via project board, email lists, by-weekly phone or face-to-face meetings as appropriate).

INCREMENTAL ENGINEERING

This is the phase where actual software development takes place. Assigned engineering team will start developing a base version of the product.

Sample Project Estimations

Here you will find a few sample time estimates for typical small, medium and large projects we have dealt in the past.

The Minimal Project (2 wks ~ 1 month) Person Days

Requirements Interview
3

Scope of Work 5

Milestones & Delivery Schedule 3

Incremental Engineering Cycles 10

Total Person Days 21

The minimum man days are based on our minimum project size requirements. CONBY does not undertake projects that require less than two weeks of involvement to avoid business goal conflicts.

A Medium Size Project (3 ~ 4 months)

Person Days

Requirements Interview
3

Scope of Work 10

Milestones & Delivery Schedule 5

Incremental Engineering Cycles 40

Total Person Days 58

The medium size project runs for 3-4 months with a development team of 2-3 developers, 1 project manager, 1 architect and a 2 person QA team.

A Large Project (6 ~ 12 months)
Person Days

Requirements Interview
5

Scope of Work 20

Milestones & Delivery Schedule 10

Incremental Engineering Cycles 120

Total Person Days 155

The large project runs for 6-12 months with a development team of 5-10 developers, 1 project manager, 2 architects and a 3-5 person QA team.

CYCLE 1: DEVELOPMENT OF BASE SYSTEM

The software architect assigned to the project will develop a design document laying out how the base system will operate; what open source technologies will be used; how the system will be divided into the base modules. If the project requires a RDBM database, a database design will be done by the resident DBA. Once the high-level design decisions are made, the development team will start developing modules in parallel and the internal QA team will perform module-level quality assurance tests as appropriate.

In this phase, you will have access to the work in progress on a project demo site where latest builds are going to be placed for review.

Once the core functionality is available, the project managers will be given a walk-thru by the system architect. You and your reviewers will be provided a demo version on our server for further review and feedback.

Based on the review and feedback, a list of fixes and change orders will be established. Change orders will be considered new items and will require adoption in the Software Requirements Document.