S
Schedules, 127 “129, 146
in CMMI process improvements, 92
and project failure, 126
Senior managers, 55 , 109 , xxv
Senior staff meetings, 33
Service Request (SR), 157
Shifting the burden archetype , 144 “147
SIMUL8 (simulation software), 169
Six Sigma, 16
business strategy and goal perspectives, 17
vs. Capability Maturity Model Integration (CMMI), 21
Slash-and-burn approach, 6 “9
Software Capability Evaluation (SCE), 82
Software Change Request (SCR), 157
Software delivery problems, 146
Software design documents, 13
Software developers, 57, 63
Software development plan (SDP), 31
Software engineering, 255 “256
Software Engineering Institute (SEI), 122, 166, 258 “259, xxi
Software Problem Action Report (SPAR), 157
Software Problem Report (SPR), 157
Solutions providers, 217
acquiring services of, 218 “220
evaluation of, 226 “227
relationship with clients , 223 “225
selection criteria, 228 “229
Stakeholders, 48 “49, xxvi
in CMMI process improvements, 105 “106, 107 “109
communication, decision, and responsibility matrix, 110
defining, 197 “198
involvement of, 29
Standard Capability Appraisal Method for Process Improvement (SCAMPI SM ), 3
appraisals in, 81
direct and indirect evidences in, 88
myth and methodology, 259 “260
Standards, 27 “31
in CMMI process improvements, 176 “177
development life cycle for, 30
language in, 27
steps in, 30 “31
Supplier Agreement Management (SAM), 64 , 163 , 187 “188
System change practices, 156
System Change Request (SCR), 157
System delivery problems, 146
System engineering, 13, 36 , 194 “195
System engineers, 60 , 63 , 65
System Enhancement Proposal (SEP), 157
System life cycle, 111 “112
System Problem Report (SPR), 157
System quality assurance, 57
System requirements updates, 13
Systems, 147, 194 “195, 199
Systems project managers, xxvi