DOI: 10.1007/978-3-540-69566-0_13
|View full text |Cite
|
Sign up to set email alerts
|

From CMMI to SPICE – Experiences on How to Survive a SPICE Assessment Having Already Implemented CMMI

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Publication Types

Select...
2
2
2

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(2 citation statements)
references
References 2 publications
0
2
0
Order By: Relevance
“…Many suppliers and even some OEMs haven't completely familiarized themselves with pro cess models such as the CMMI Model Framework and the Software Process Improvement and Capability Determi nation (Spice, ISO/IEC 15504) model. 6 Such models recommend best practices…”
Section: Immature Maintenance Practicesmentioning
confidence: 99%
“…Many suppliers and even some OEMs haven't completely familiarized themselves with pro cess models such as the CMMI Model Framework and the Software Process Improvement and Capability Determi nation (Spice, ISO/IEC 15504) model. 6 Such models recommend best practices…”
Section: Immature Maintenance Practicesmentioning
confidence: 99%
“…However, project-level processes in software development can be divisible, and project teams can customize their processes by selecting and combining elements from multiple plan-based and agile normative frameworks (Fitzgerald et al 2006;Napier et al 2008). Practitioner reports from the field also suggest that firms are increasingly adopting multiple process frameworks for their projects and embracing software process diversity (Anderson 2005;Bella et al 2008). Software process diversity refers to the condition of project-level processes being composed of elements drawn from multiple normative software process frameworks that could differ in their underlying attributes and philosophies (Lindvall and Rus 2000;Deck 2002).…”
Section: Introductionmentioning
confidence: 99%