Index_C


C

career advancement, 224–225

cause-and-effect diagram, 161

change (configuration) control board (CBB), 216

change management, 215–218

charters, project, 46–47, 121, 122, 156

checklists, risk management, 161, 163

closeout phase, 40, 245–254

activities of, 246–247

contract closeout in, 249

customer sign-off in, 248–249

file closing/archiving in, 251–252

financial audit in, 247–248

lessons learned analysis in, 250

loss of resources during, 245

office closeout in, 249–250

and personnel reassignment, 250–251

product completion/delivery in, 248

product maintenance preparation in, 252–253

scope verification in, 247

see also termination phase

Cockburn, Alistair, 241, 242

"code like hell" syndrome, 64, 133

communication plan, 143

communication skills, 101–102, 113

comparative ranking methods, 166–168

competitive analysis, 92

completion criteria, 67, 82

completion date, 93

Computerworld, 2

concept phase

project life cycle in, 43–47

systems development life cycle in, 48–52

configuration (change) control board (CBB), 216

constraints, 78–79, 93, 188

contingency plans, 140, 141, 180

contracts

closing, 249

documents required by, 157

files on, 251

requirements of (in project plan), 136–137

control, see monitoring and control

core project team, 112–113

cost performance index (CPI), 31–35, 208–211

costs

of errors, 74

project plan estimates of, 138–139

and schedule/performance, 195

in trade-off analysis, 58–60

validating estimates of, 145–148

cost variance (CV), 30–32, 35, 205–207, 209

CPI, see cost performance index

credibility (of project manager), 104

critical path, 55

cross-functional teams, 109

cross-referencing requirements matrix, 96–97

Crystal family (light methodologies), 241–242

customers

acceptance by, 67

changes initiated by, 215

closeout sign-off by, 248–249

following up with, 72

meetings required by, 138

plan sign-off by, 149–150

requirements established by, see requirements

customer service, 255–268

definition of, 256, 257

determining expectations for, 258, 261

measurement of, 257–259, 261, 263–267

obstacles to, 259–260

program elements for, 256, 257

refining/improving plan for, 267–268

service tactics for, 261, 262

customer service and system maintenance phase, 41, 70–73

customer surveys, 72, 263–267

CV, see cost variance




Managing Information Technology Projects
Managing Information Technology Projects: Applying Project Management Strategies to Software, Hardware, and Integration Initiatives
ISBN: 0814408117
EAN: 2147483647
Year: 2003
Pages: 129
Authors: James Taylor

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net