Follow an established Governance Model

Our past experience in the governance model has proved that we can ensure complete visibility and flexibility in operations and realize strategic objectives for Customers. The Governance Model has evolved from our best practices of a variety of software project management approaches in the past and experience gained over the years. Our model spreads across every meaningful level of the Customer’s organization and is aimed at addressing all the services requested – Relationship Management Services, Application Testing Services, and Cross-Functional Services, besides prioritizing the development of technical and functional capabilities Our model establishes and documents the methods, techniques, tools, standards, and procedures that will be applied throughout the life of the program. It spells out the management and control activities that are critical from a coordination and control perspective

Our Governance Structure approach

  • Enable monitoring of development in our relationship with Customers so that it is mutually beneficial.
  • Provide a forum for strategic direction setting for projects delivery and beyond, viz., Technology direction, and Risk Mitigation
  • Provide a forum for day-to-day tactical handling of issues and measurement of progress with respect to actual (Program Management)
  • Provide a pre-defined escalation path for effective decision-making with respect to issue management, risk management, and dispute resolution (Escalation)
  • Monitor compliance with contractual, legal, and operating risk (Audit)

Our governance processes will be designed to provide special emphasis on every major component of Customer engagement. The core structure has the following identified roles and individuals at each level:

  1. Steering Committee meetings will be held every quarter and is responsible for
  • Creating the roadmap for the program execution and setting targets
  • Reviewing performance providing overall directions
  • Manage Relationship
  • Review Contract and Performance Assessment
  • Contract Ownership
  • Final Escalation Point
  1. The relationship Team or Program Review Committee will be held every month and is responsible for
  • Build and Review Master plan and Forecast
  • Change Control, Contract, and Governance
  • Review of Performance, SLA estimation, Integrity of Delivery
  • Cost reviews
  • Commercial Negotiation
  • Escalation Process

Besides responsible for the following key functions:

  • Overall program governance
  • Customer Delight
  • Planning
  • Directions
  • Benefit realization
  1. Delivery Team (Technical Managers, Project/Process Managers, Infrastructure, Team Members, Domain Experts) is held every week and responsible for
  • Discuss Application Development and Maintenance plans, rollouts upgrades
  • Application Development & Maintenance
  • Resource Management
  • Project Status and Tracking
  • SLA Metrics & Tracking
  • Operational Issues, Delivery Co-ordination
  • Issue consolidation and Tracking
  • Risk and Change Management

The benefits to Customers from such a model are:

  1. Account planning is fully visible and transparent to the customer
  2. Evaluation and improvement through governance processes, lessons learned workshops
  3. Consistency and high quality of all deliverables
  4. Fine-tuning of the key parameters of business processes and technologies
  5. Effective management of cost, risk, and productivity parameters