A. Greenfield Enterprises
Quality Principles
| |
* |
Always meet or exceed
client expectations and ensure satisfaction |
| |
|
o |
OTACE - On
time and above customer expectations |
| |
|
o |
Only promise
what can be delivered, and deliver what is promised |
| |
* |
Adding value - always
provide practical, client specific solutions, and hence deliver genuine
benefits and value-for-money to our clients |
| |
* |
Services to clients
- maintain & continually improve the quality of the services provided,
ensuring that these meet the specific & changing needs of clients |
| |
* |
Quality system - continuously
evaluate and improve our quality system, to ensure that it facilitates
the maintenance and continuous improvement of our services to clients |
| |
* |
First class communication |
| |
* |
Encouragement of creativity |
| |
* |
Aim to solve the problems
and resolve the issues |
B. Greenfield Enterprises
Quality Management System
| Start of project: |
| |
* |
Identify objectives,
aims and scope of the project with the client |
| |
* |
Break project down into
the three types - top, middle, bottom type |
| |
* |
Identify people –
consultant/contractor(s), client staff, other stakeholders - and resources. |
| |
|
o |
If required, identify
and keep track of those peopl who are responsible, accountable, consulted,
informed |
| |
* |
Identify and agree plan
showing agreed deliverables and timescales for the project |
| |
|
o |
Produce a timetable with agreed delivery
dates for each identifiable stage of the project |
| |
|
o |
Produce appropriate documentation
around the project plan |
| |
* |
Clearly determine and
communicate who does what and how they do it |
| |
* |
Identify and carry out
any training necessary for the success of the project |
| |
* |
Agree clear lines of
communication |
| |
|
o |
Identify and schedule periodic meetings
for the different persons. Meetings to be held on request by one person |
| |
* |
Create acceptable timetable
for reporting progress and measuring progress against agreed plans,
so all involved know how their work interacts with other project team
members |
| During project: |
| |
* |
Document the process, retain interim
analyses as part of audit trails - so relatively easy to return to
any point in the process and rework it or for there to be peer review |
| |
* |
Maintain clear communications
with the client, and within team |
| |
* |
Measure progress against plan |
| |
* |
Record all decisions made and
communicate necessary information to all concerned |
| Prior to project
delivery: |
| |
* |
Project Deliverables Principles
(especially relevant to modelling solutions). |
| |
|
o |
New routines are calibrated using test data
where the expected output is known in advance |
| |
|
o |
Clusters of data are sought that indicate
data inconsistencies or whether rare items are missing |
| |
|
o |
When feasible, alternative computing routines
are used to analyse data so any logical inconsistencies can be identified.
|
| |
* |
A partner or another to review
all final documentation/deliverables, check calculations, process
maps etc. before sending to client |
| Project end:
|
| |
* |
Request and receive customer feedback
i.e. questionnaires or measures of customers' satisfaction |
| |
* |
A partner or another to check
that all customers are asked for opinion on quality of work afterwards |
