3. SPICE =
Software Process
Improvement and
Capability dEtermination
4. Introduction
a model that identifies a set of sof tware 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)
5. 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
6.
7.
8. 5 Steps to project success
Seriously …
http://www.youtube.com/watch?v=GcR-wpSzr4Y
9. MAN.3 – Project Management
The purpose of the Project management
process is to
identif y
establish
plan
co-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.
15. 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.
21. Allocate resources to activities and
determine schedule for each activity and
for the whole project.
22. BP7. Identif y and monitor
project inter faces
http://www.stakeholdermap.com/stakeholder-analysis.html
23. Identify and agree interfaces of the project
with other (sub-) projects, organizational
units and other stakeholders and monitor
agreed commitments.
24. Risk Mgmt
CM Plan
Project WBS
Organization
Project
QA Plan Targets
scope
BP8. Establish project plan
25. Collect and maintain project master plan
and other relevant plans to document the
project scope and goals, resources,
infrastructure, interfaces and
communication mechanisms.
30. 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
32. 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.
33. BP1. Define the scope of work
BP2. Define project life cycle
BP3. Determine and maintain estimates for project attributes
BP4. Define project activities
BP5. Define skill needs
BP6. Define and maintain project schedule
BP7. Identify and monitor project interfaces
BP8. Establish project plan
BP9. Implement the project plan
BP10. Monitor project attributes
BP11. Review and report progress
BP12. Act to correct deviations
34.
35. 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
36. SPICE Level 2 for MAN.3
can be achieved also in
AGILE projects!