Overview | Quality
Journey | Quality Policy & Organization | Best
Practices
Aricent
has a well-documented quality policy.
Under this policy Aricent commits itself to:
- Strive for the highest level of customer satisfaction:
- By constantly listening to the customer
- By providing on time, error free and fit for use products
and services
- Provide a work environment and culture, which promotes
initiative, innovation and teamwork.
- Practice processes, which are defined and measurable
Process Documentation Structure
Aricent follows a 4-tier process documentation structure, which
ensures that the processes are followed consistently across
all projects.

Fig 1. Process Documentation Structure
Quality Policy Manual: This details the high-level
quality policies with respect to the complete order fulfillment
life cycle, and it fully conforms to the requirements of ISO
9001:2000 and SEI CMMI Level 5.
Software Development Management Process Manual: This
details the software development lifecycle phases, the entry
and exit criteria for each phase, mandatory and optional deliverables
made during every phase and the responsibility for carrying
out various tasks.
Software Development Procedures- SDPs (20): These
detail the actions, and responsibilities involved in each
of the above stages as well as in each supporting process
like configuration control that runs across all stages. The
list of procedures includes, among others:
| Project Planning |
Project Tracking |
Risk Management |
| Requirements |
Design |
Code and Unit Test |
| Testing |
Configuration Management |
Document Control |
| Training |
Defect Management |
Project Closure |
|
Project Plans: A detailed project plan is made for
every project to include the scope of the work, team organization,
milestones, deliverables, risks and dependencies, resource
requirements, other support plans for SQA, CM and training
activities. These also cover customer-specific quality requirements
that must be complied within any given project. Work instructions
are also made where applicable to give step-by-step procedure
for carrying out routine activities like making a build, etc.
An independent Quality Group that reports directly to the
Chief Operating Officer ensures the deployment of the Aricent
Quality Policy in the organization. Software Process Engineering
Group that meets at least once a week to review software engineering
processes and evolve, deploy and monitor process improvements
supports this group.
In addition, each Engineering manager holds individual and
group quality targets that form the basis of his or her performance
appraisals.
Last updated :
December 19, 2005
|