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

P

paradigm shift, 254

parametric modeling of costs, 142-143

Pareto diagram, 285-286, 286

payback period in business case summary, 54

PC technicians, documentation for, 290

PDM (precedence diagramming method), 107

performance according to plan, 244-247

data collection, 244-246

progress against baselines, 246-247

performance feedback for team members , 237-238

performance indicators, 217, 280

performance monitoring, 237-239

performance reporting, 278, 296-307

driving stakeholder action, 302-307

canceling project, 305

communicating performance deviations, 302-303

trade-off management, 303-305

earned value, 298-302

basics, 299-300

indexes (ratios), 301-302

variances, 301

estimate at completion, 298

exam essentials, 307-308

trend analysis, 297

variance analysis, 297

performing stage of team development, 234

person- hour estimate, 144

pilot test, 6

planned value, 299

planning components

comprehensive review of, 326

in project plan, 210-213

planning phase in SDLC, 345

planning processes, 15. See also scope of project

brainstorming, 81

exam essentials, 197-198

importance, 71

platform wars, 255-256

PMI (Project Management Institute), 9

PMO (project management office), 55, 55, 135

PMP (Project Management Professional) certification, 9

postponed project, 322

precedence diagramming method (PDM), 107

predecessor task, 106

preliminary investigation, 16

prevention costs, 178-179

preventive action to avoid risk, 184, 293

probability of risk, 183

problem solving, 12-13

in team meetings, 250

process diagrams, 177, 178

processes, adjustments, 288

procurement planning, 166, 190-194

case study, 197

contract types, 191-192

make or buy analysis, 190-191

statement of work (SOW), 192

vendor selection criteria, 193-194

vendor solicitation, 192-193

product description in scope statement, 73

case study, 91

sample, 76

production environment, 139

program, defining, 2

program management office (PMO), 148

programmers

junior-level, 174

typical day, 118

programming language, platform wars, 255-256

progress reports , 244-245

project closure

administrative closure, 323-332

comprehensive review, 325-329

formal acceptance, 324-325

project archive, 324

project turnover , 329-331

release of team members, 331-332

case study, 330-331

contract closeout, 323

exam essentials, 333

types, 322-323

project concept documentation, 18-19

project definition, 2-9

for IT project, 3-6

automated systems, 5-6

considerations, 6

datacenter creation, 4

Enterprise Resource Planning (ERP), 5

infrastructure, 4

server/system deployment, 4-5

software development, 3

storage area network (SAN), 5

project description

in charter, 52

for IT project, 52

project execution. See execution of project

project justification in scope statement, 72-73

case study, 91

sample, 76

project kickoff, 234-237

project life cycles, 16-19

project management, 9

defining, 9-10

exam essentials, 22-23

Project Management Institute (PMI), 9

Project Management Knowledge Areas, 10

project management office (PMO), 55, 55, 135

Project Management Professional (PMP) certification, 9

project management software, 115, 154

cost planning with, 154-155

training for, 155

project manager, 45. See also IT project manager

caught between sponsor and vendor, 258-259

charter identification of, 52-53

communication

of constraints impact, 74

of schedule delays, 304

with stakeholders, 217

expectations in kickoff meeting, 235

project organization chart, 171, 172

project overview in kickoff meeting, 235

project plan

case study, 218-221

components, 209-214

administrative, 210

appendix, 213

planning, 210-213

references, 213

templates and checklists, 213

consolidation

organizing and writing, 214-215

planning phase closeout, 216-217

review, 216

updates, 215-216

development after-the-fact, 214

purpose and benefits, 209

what it is, 208-209

project processes, 14, 14-15

project reviews, 250-252

project team. See team

project turnover, 329-331

projectized organization, 21, 21-22

projects

canceling, 305

decision to move forward, 217

distractions from, 117

at risk of failure, 296

proof of concept, 322