[rev_slider alias=”quality-policy” /]

DevBatch Private limited is committed to satisfy our customers by building trust through hard work and responsibility. We, at DevBatch believe that consistent satisfaction of customer needs with highest possible quality is essential to business survival. Focusing on the technological services, we want to make sure that we remain best in the field by establishing the following Quality policy statements.

Requirement Documents

All projects shall set up an SRS to depict the functions, execution and the interface prerequisites of the product items.

Planning

Software Project Management Plan needs to be created for all projects.

Management

Project managers would produce project performance reports at intervals agreed with the project stakeholders. Project managers shall be responsible for ensuring the team members are aware of their quality maintenance responsibilities and are adequately trained to perform their assigned tasks.

Architectural design

All projects shall conduct a Design Input Review to assure that the design inputs such as Software Requirements Specifications are vivid, complete and correct and possess sufficient quality to support the development of a designed solution.

Coding

Projects shall develop software in compliance with the predefined coding standards. Coding standards shall be updated to reflect any project specific practices meticulously.

Testing & Quality Management

All projects shall describe the approach of testing in a Software Test Plan. The STP shall describe the project’s approach to unit, integration and acceptance testing.

All projects shall plan and perform the Software Quality Management activities required to ensure the customer’s stated and implied needs be met and that the software product is developed in compliance with the best recognized practices.

CMMI Level 2 Checklist

DevBatch, being a CMMI Level 2 Company, will make sure that we are aligned with the following guidelines.

Requirements Gathering

Goal: Manage all the requirements of a project.

Practices to follow:

  • Obtain an Understanding of Requirements
  • Develop Commitment to Requirements
  • Establish the Required Changes (Change Requests)
  • Maintain Requirement Traceability Metrics
  • Identify Differences between Project Work and Requirements

Project Planning

Goal: Establish Estimates

Practices to follow

  • Estimate the Scope of the Project
  • Establish Estimates of Work Product and Task Attributes
  • Define Project Life-Cycle
  • Determine Effort and Cost Estimation

Goal: Develop a Project Plan

Practices to follow

  • Plan the Budget and Schedule
  • Do a thorough Risk Assessment
  • Design Data Management
  • Resource Management
  • Plan for Needed Knowledge and Skills
  • Prepare a Client Engagement Plan
  • Establish the Project Plan

Goal: Obtain Commitment to the Plan

Practices to follow

  • Review of the Plan
  • Reconcile Work and Resource Levels
  • Obtain Plan Commitments

Project Monitoring and Control

Goal: Monitor Project against Plan

  • Monitor Project Planning Parameters which includes Monitoring Commitments, Project Risks, Data Management, Client Engagement
  • Conduct Progress Reviews
  • Conduct Milestone Reviews

Goal: Manage Corrective Action to Closure

  • Analyze Issues
  • Take Appropriate Action
  • Implement Planned Actions

Process and Product Quality Assurance

Goal: Objectively Evaluate Process and Product

  • Communicate and Ensure Resolution of non-Compliance Issues
  • Ensure both Process and Products are aligned with the Products’ requirements
  • Establish Records Accurately.