DELIVERY MANAGEMENT

Analytics driven delivery process accelerated by complete transparency

Rebaca competes in a specialized industry with a capable engineering team. Although, our technical skills gives us the credibility to procure new customers, it is not enough to sustain long term customer satisfaction. Applying the agile development principles allows accurate analysis and delivery of customer requirements on schedule, within budget and with fewer dependencies. To further improve our delivery process we run regular analytics to test the project health and generate reports which are shared with our customers.

Delivery of software with competent results

Our progress management track customer requirements by defining them as KEY GOALs that need to be achieved. These GOALS are dichotomized into OUTPUTS (testable software functionalities or reviewable document sections) that record the effort and schedule details before being shipped to the customer for acceptance. The customer feedback is categorized as a change request or deliverable bug and brought to resolution.

Through validation and verification of deliverables

Before shipping the outputs, the software functionalities are validated and verified in two stages. At the first level, the development engineers, who produce the outputs, perform unit tests using the use case driven approach. Static Code Analyis (SCA) tools are also used to align the code with the programming standards. At the second level, the designated test engineers, validates these outputs and the subsequent use cases which are made available to them via our enterprise wiki. The defects found in the second level are logged in our defect management system(JIRA) and ammended by the developers. After internal validation is complete these outputs are delivered for customer feedback and acceptance.

Collaborative Engineering

At Rebaca our engineers work on cloud computing platforms to accurately update all changes made to the code and documents, shared within the delivery teams. All projects have a separate space in SVN and Confluence, created upon induction, which is used for continuous collaboration. Build management systems are frequently scheduled to automatically validate the SVN builds. SVN and Confluence are both backed up and shipped regularly to prevent any expensive loss of changes.

Capture and consume customer complaints through analytics

At Rebaca we use Analytics to keep our customers happy. All our delivery plans are data based and are recorded in online systems viz. JIRA, Confluence and OAS. We have developed several KCIs (key capability indicators) that measure the health of the delivery engine viz. product velocity(developer productivity), resource velocity(utilization of resources), validation velocity(tester productivity), customer defect, median age of defects etc. These KCIs are updated relugarly on Confluence where all the stake holders monitor them via graphs to collaborate, identify and address potential customer complains thus improving overall productivity.