Client engagement process is vital to the success and effectiveness of successful relationship during development process. Rembros Corporation would like to present how we organize project development flow. Our goal is to make project development as effective as possible and make it as transparent and controllable for the customer as possible.

There are some basic steps of the project flow scheme:

First Contact and Input Information.
Starting a project with Rembros Corporation is fairly simple: just contact us and tell us your needs and expectations. Rembros business analysts and software architects will approach you to learn as much as possible about your business needs and requirements. Our potential customers are not required to provide exact requirements at once, although a formal structured Request for Proposal speeds the things up considerably. Just speak out your thoughts and expectations and it is quite enough for us to start analyzing your project. We will analyze your information, ask some questions, offer you more ideas and then formalize your answers in the form of project documentation.

Analysis.
Your benefit is that you gain a thorough analysis of your business needs by our specialists within a very short period of time.

Proposal.
We clearly describe the business requirements of the system so they are easy for you to study and evaluate. On the basis of the agreed business requirements, we prepare and propose an optimal technical solution. Our proposals can vary from a simple estimation of workload and cost of project up to a comprehensive suggestion regarding the architecture of the project, technologies analysis, total cost of ownership estimation, design suggestions, etc. Initial estimation of the project is free and is usually developed within a couple of days.

Confidentiality.
To protect your private information or intellectual property, we can sign a Non-Disclosure Agreement (NDA) before you deliver us any project-related information.

Inception.
Project start and initial requirements collection. Takes 5-10% of the project time.

Elaboration.
Requirements collection and analysis, planning, creation of design and architecture of the system take place in this phase. Takes 20-30% of the time.

Construction.
The biggest part, where most of the coding, development, and testing are performed. Takes 50-70% of time.

Transition.
Delivery of work results to the customer and the product installation. Takes about 10% of time. These four stages are an integral part of any project. But then, depending on the complexity of a project, its budget and customer goals, a project may or may not contain some parts, like user documentation preparation, extended technical documentation development, extra testing, etc.