SPICE UP – Project ManagementOana FeidiContinental Automotive

10.11.2012

SPICE = Software Process Improvement and

Capability dEtermination

Introduction

a model that identifies a set of software best practices and shows how they fit together to create an improvement path for the software development process

international standard for SW process assessments

mainly used in Europe and Australia by the automotive industry Automotive SPICE launched in April 2006 (May 2010,

version 2.5) TESTSpice (December 2010, version 1.0)

Goal

To provide assessment results that are repeatable, objective, comparable

(me) structure the way of working (me) identify the main weakness within the development process and build improvement activities

(me) “link” between inputs & outputs

5 Steps to project successSeriously …

http://www.youtube.com/watch?v=GcR-wpSzr4Y

MAN.3 – Project ManagementThe purpose of the Project management process is to

identifyestablishplanco-ordinate, and monitor the activities, tasks, and resources

necessary for a project to produce a product and/or service, in the context of the project’s requirements and constraints.

BP1. Define the scope of work

Define the work to be undertaken by the project, and confirm that the goals of the project are feasible with available resources and constraints.

BP2. Define project life cycle

Define the life cycle for the project, which is appropriate to the scope, context, magnitude and complexity of the project.

Rule #1

BP3. Determine and maintain estimates for project attributes

Define and maintain baselines for project attributes:1)business and quality goals for the project,2)resources for the project and 3)project effort, schedule and budget.

BP4. Define project activities

Plan project activities according to defined project life cycle and estimations, define and monitor dependencies between activities.

BP5. Define skill needs

Identify required skills needed for theproject and allocate them to individuals and teams.

Rule #4

BP6. Define and maintain project schedule

Rule #3

Allocate resources to activities and determine schedule for each activity and for the whole project.

BP7. Identify and monitor project interfaces

http://www.stakeholdermap.com/stakeholder-analysis.html

Identify and agree interfaces of the project with other (sub-) projects, organizational units and other stakeholders and monitor agreed commitments.

BP8. Establish project plan

QA Plan

CM Plan

ProjectOrganization

Risk Mgmt

WBS

TargetsProjectscope

Collect and maintain project master plan and other relevant plans to document the project scope and goals, resources, infrastructure, interfaces and communication mechanisms.

BP9. Implement the project plan

BP10. Monitor project attributes

Monitor the defined project attributes and document significant deviations of them against the project plan.

BP11. Review and report progress

Regularly report and review the status of the project against the project plans to all affected parties. Regularly evaluate the performance of the project.

Rule #5

BP12. Act to correct deviations

Take action when project goals are not achieved, correct deviations from plan and prevent recurrence of problems identified in the project.

Update project plans accordingly.

BP1. Define the scope of workBP2. Define project life cycle

BP3. Determine and maintain estimates for project attributesBP4. Define project activitiesBP5. Define skill needs

BP6. Define and maintain project scheduleBP7. Identify and monitor project interfaces

BP8. Establish project planBP9. Implement the project planBP10. Monitor project attributesBP11. Review and report progressBP12. Act to correct deviations

Plan the work BP.1, BP.2, BP.3, BP.4, BP.5, BP.6,

BP.7, BP.8

and then work the plan!

BP.9, BP.10, BP.11, BP12

SPICE Level 2 for MAN.3 can be achieved also in

AGILE projects!

Please fill in the evaluation forms!

Thank you!

Diamond Sponsors

Platinum Sponsors Gold Sponsors

Training Partners Media Partners Other Partners