VDA_6.3_EN_Yellow_Volume_.pdf.pdf - 第51页

49 P2.3 Has project management been implemented and is there a project plan that has been agreed upon with the customer? Minimum requirements relevant for assessment Examples for implementation The project plan meets the…

P2.2* Are all resources required for project implementation planned and avail-

able, and are changes reported?

Minimum requirements relevant for assessment

Examples for implementation

The resource planning takes the customer require-

ments into account and is based on the project

agreement.

Resource planning for project team members has

been established and implemented. The staff work-

load is taken into account.

A review and (where necessary) an adjustment of

the resource planning is carried out when changes

occur (deadlines, scope of development performance

etc.). The critical path is given special consideration

within the resource planning.

The necessary project budget for personnel and

equipment is planned and released.

Changes to the project organization (interface with

customer) are reported.

The resources for software-specific activities have

been planned.

• Evidence of resource plan-

ning (taking other projects

into account)

• Resource planning for

equipment (e.g. develop-

ment test stand, inspection

and laboratory facilities)

• Resource planning by the

Scrum Master

• Resource planning for inte-

gration and tests

P2.3 Has project management been implemented and is there a project plan

that has been agreed upon with the customer?

Minimum requirements relevant for assessment

Examples for implementation

The project plan meets the specific customer re-

quirements.

All internal and customer defined milestones are

fully incorporated in the project plan.

A review is carried out at the milestones defined in

the project plan to check that all planned activities

are carried out and that the required maturity level

is reached.

If a statutory authorization procedure for a product

is specifically required, the duration of this proce-

dure is included in the project plan.

In-house communication is ensured when changes

are made to the project plan. Changes to the pro-

ject plan which affect the customer are coordinated

with the customer.

Project changes that have an impact on the overall

schedule have been taken in account in the escala-

tion process (risk management).

The critical path is generated from the project plan

and takes account of the associated delivery items.

Quality-related project activities as well as procure-

ment activities must be part of the project plan. A

separate, detailed plan can be referred to in the

project plan.

The plans must take prototypes and pre-launch

parts into account.

The scope of software required at the respective

times has been planned.

• Project plan with milestones

• Specific customer require-

ments regarding technologies

xand/or product groups

• Customer project plan

• Customer deadlines

• Customer milestones

• Targets set by the customer

(measurements within the in-

dividual milestones)

• Milestone assessments (re-

views)

• QM plan (e.g. from VDA MLA

or APQP)

• Country-specific certification

requirements (ECE, SAE,

DOT, CCC, INMETRO, KBA

etc.)

• Legal and regulatory approval

processes relating to critical

systems (environmental re-

quirements, among other

things)

• Release planning regarding

basic functions and mile-

stones

• Software project plan

• Software milestones

• Basic Rollout Plan

(BROP)

• Feature Rollout Plan

(FROP)

• Planning of the ASPICE as-

sessment, including the defi-

nition of levels and the scope

in accordance with the

agreed customer require-

ments

P2.4 Have the quality-related project activities been planned, and are they

monitored for compliance?

Minimum requirements relevant for assessment

Examples for implementation

The quality-related project activities meet the spe-

cific customer requirements.

Both product and process assurance measures are

part of the quality-related activities.

Verification and validation of the product and pro-

cess requirements are included in the planning.

The planning also addresses critical components

and supply items (internal and external suppliers).

The planning is regularly monitored for compliance

and for target achievement.

The quality-related activities relevant to software

have been taken into account.

• Project plan

• Customer milestones

• Customer requirements with

regard to quality plans

• Quality plan (audits, reviews

and VDA MLA)

• Customer specifications

• Specific software milestones

• Reviews, e.g. of code and

models

• Test case creation and

validation (verification?)

• KPIs relevant to software

(metrics, test coverage, level

of test automation, rate of er-

ror reduction etc.)

• Software-specific assessment

planning and assessment lev-

els

• SW-Q release

• Risk assessments (special

characteristics, cyber secu-

rity)

P2.5 Are the procurement activities of the project included in the project

planning?

Minimum requirements relevant for assessment

Examples for implementation

The supplier selection process and the target dates

for contract awards are contained in the project

plan for all types of suppliers.

The suppliers of plants, machines, tools, measuring

and inspection systems as well as the service pro-

viders are integrated in the planning.

• Project plan

• Milestone plan

• Make-or-buy decision

• Service providers (e.g. devel-

opment, laboratories, mainte-

nance, software)