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

48 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 c…

7.2 Project management (P2)

Process element P2: Project management

P2.1 Has a project management strategy (including a project organization)

been established?

Minimum requirements relevant for assessment

Examples for implementation

There is a project management process.

An interdisciplinary project organization is specified.

The responsibilities and authorizations of the pro-

ject leader and team members are defined.

The customer and the supplier have been informed

who the contact persons are.

The project organization and the associated escala-

tion management meet the customer requirements.

Escalation criteria (including escalation in supplier

management) have been specified, and measures

are derived in case of non-compliance with the

specifications.

Roles are defined in accordance with the develop-

ment method or collaboration model (agile or not

agile).

Experiences (especially lessons learned) from on-

going or previous projects with a comparable scope

of products are taken into account.

Project risks have been identified, assessed, and

have been mitigated by means of appropriate

measures.

• The roles, tasks, compe-

tences and responsibilities of

the project manager/technical

experts have been defined

• Project interfaces in multi-site

projects

• Organizational chart for the

project

• Composition of the project

team

• Evidence of qualifications

• Special customer require-

ments regarding project man-

agement

• In case of an agile approach:

Definition of the escalation

mechanism (e.g. the Scrum

Master escalates to the Prod-

uct Owner)

• Contact persons/decision-

makers in the escalation pro-

cess have been defined

• Records of milestone assess-

ments, including measures

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