IT Project+ Study Guide, 2nd Edition (PKO-002)

C

calendar days, vs. work days, 108

canceling project, 305, 322

Capability Maturity Model (CMM) analysis, 292

CASE (computer aided software engineering) tools, 348

case scenarios, 17

case study

wineries e-mail and intranet systems, 57-58

closeout, 330-331

communications plan, 195

cost planning, 152-154

evaluating, 306

finalized plan, 218-221

procurement planning, 197

project execution, 260-261

quality plan, 196

risk assessment, 196

scope document, 91-94

work breakdown structure (WBS), 120-121

CD-ROM, templates, 252, 354-362

champion. See sponsor

change control, 278-283, 325

cost control, 281-282

exam essentials, 307-308

other changes, 282-283

schedule control, 280-281

scope change control, 279-280

management plan for, 78

charter, 51-58

business case, 53-54

formal approval, 54-58

goals and objectives, 53

matching to project team, real world scenario, 50

project description, 52

team, 52-53

checklists

in project plan, 213

for quality, 180

checkpoints, 19

client, 45

project plan review by, 216

project review for, 251

relationship management with, 241-242

working with, 87

closeout

of planning phase, 216-217

of project. See project closure

closing processes, 15

CMM (Capability Maturity Model) analysis, 292

COCOMO (COnstructive COst MOdel), 143

collaborating style for conflict management, 238

collaboration, online, 167

Commercial Off The Shelf (COTS) program, 4

communications, 11-12, 248-252. See also documentation

about cost estimates, 146

among IT job roles, 9

with client, 86, 241-242

of milestones, 116

of performance deviations, 302-303

planning, 166, 185-189

case study, 195

example, 187

with project team members , 188

with stakeholders, 188-189

strategy, 186-187

in project plan, 212

sample, 221

project reviews, 250-252

status reports , 250

within team, 249

team meetings, 248-250

with vendor, 256, 257-260

preparation before, 259

communicator, IT project manager as, 7

competing style for conflict management, 238

completion criteria, in scope statement, 74

comprehensive project plan. See project plan

compromising style for conflict management, 238

computer aided software engineering (CASE) tools, 348

confidence level for project estimates, 74

configuration, changes, 283

conflict, styles for dealing with, 237-238

consensus

with client, 242

for scope statement, 77

constrained optimization decision models, 43

constraints

in project plan, 211

sample, 220

in scope statement, 75

case study, 92

sample, 77

COnstructive COst MOdel (COCOMO), 143

consultants , relationship with, 88-89

contingency action

for risk, 185, 295

and schedule control, 294

contingency fund, 149, 154

contract closeout, 323

contract workers, 175, 191

for testing, 180

contracts, types, 191-192

control charts , 287, 287

controlling processes, 15. See also change control; quality control

comprehensive review of, 327

exam essentials, 307-308

corrective action

for cost overruns, 282

in schedule control, 280

for scope creep, 279

cost baseline, 151

cost-benefit analysis, 42, 177

cost control, 278, 281-282

cost estimates, 141-148

revised, 281

in scope statement, 74

techniques, 142-145

analogous estimating, 142

definitive estimates, 143-145

parametric modeling, 142-143

tips, 145-148

cost of quality, 178-179

cost performance index, 301

cost planning. See also cost estimates

case study, 152-154

cost budgeting, 148-155

baseline, 151

budget creation, 149-151

budget targets, 151-152

exam essentials, 155-156

with project management software, 154-155

real world scenario, 140

resource planning, 134-141

requirements definition, 137, 137-141

types, 135-137

trade-offs, 305

cost reimbursable contracts, 191-192

cost variances, 152, 301

costs

in business case summary, 53-54

data collection on, 246

evaluating, 247

vendor payment process, 256-257

COTS (Commercial Off The Shelf) program, 4

crashing, 114

critical path method (CPM), 111-114

and schedule control, 280, 281

customer. See client