Rebaca follows agile process management methodology to maintain quality standards of software delivery for all projects. The agile methodology gives Rebaca flexibility in assigning & reprioritizing the tasks based on project requirement and to meet the deliverables.

Rebaca’s process starts right from Project proposal phase.  Proposals are created taking client into confidence. This happens via series of technical discussion with the client. This enables Rebaca to put forward a complete solution which is supposed to meet client expectation.

Once a project is awarded, detailed project plan is created, milestone / deliverables are defined and resources are being allocated to the project. The entire project management is being done through JIRA. In JIRA Milestones / deliverables are entered and is being monitored. At the start of the project two weeks sprints are defined which contain the tasks that need to be completed in each sprint or week. At any point of time only two sprints are present; one sprint for the present week and one sprint for the next week. Any tasks that are being delayed are moved to next week’s sprint with a comment from Project Lead. In a sprint there should not be any task which is more than 2 days long. In every week there will be two scrum meetings to discuss on the progress of each task, any blocking issue, any task that needs to be reprioritized, any dependency from customer side etc. As a part of risk management, Project lead takes up the customer related issues with the customer for a resolution.

A weekly status report is automatically generated from JIRA and it includes tasks completed in the week under review, tasks to be done in the next week, list of delayed tasks, customer issues if any. This is being shared with the customer before the weekly conference call and is being discussed during the weekly conference call.

Typical quality measures that are being followed in the entire life cycle of the project are:

• Design review – Review of High level design & Low level design done during the design finalization phase. Design documents are then shared with the customer for review and feedback.

• Code review & analysis – Code review and analysis done at regular intervals using available tools, e.g. Visual Studio 2008 Code Analyzer or LINT, Find bugs, FxCop etc.

• SQA phase is planned for every milestone delivery.

Rebaca’s process is flexible enough to use either customer specified design template and coding standard or Rebaca’s own design template and coding standard. For Source control management CVS / SVN / VSS are used.

QA is involved in the project right from beginning of the project. Test plan is prepared once the design documents are created. After the test plan is reviewed the test cases are created.

In case of any change request from customer, change request is analyzed and its impact on project schedule is identified. Project plan / deliverables are modified accordingly to accommodate the changes. The change request cycle includes design change / design update, design review, test plan / test case creation for the suggested changes, its implementation & testing.

Every month a Program Review meeting is organized with customer to discuss on the progress of the project, milestones achieved, status of the project w.r.t to original timeline, and customer specific issues or any issue that Customer wants to discuss with Rebaca Management.

On completion of the project, a project closure meeting with the customer is convened to conduct a customer review and to get a customer feedback on the project