Index_I

I

idealists, team members as, 395

ideas, selling to management, 79 “80

IFB (Invitation for Bid) document, purpose of, 218

if-then statements, using in contingency plans, 55

Imaginary Leader personality type, dealing with, 210

implementation tracking, using PNDs for, 250

in the red versus in the black, 293

independent contractor, working as, 492 “494

inflexible constraints in Microsoft Project, explanation of, 265

informal acceptance of projects, explanation of, 430

initiating phase of project management, significance of, 362 “363

integrators. See vendors

internal skills, assessing for potential project teams , 192 “196

Internet, performing research on, 59 “60

interviews

with Anne Walker, 335 “339

with Bill Farnsworth, 221 “226

developing questions for, 204 “205

with Eric Chermely, 57 “60

with Greg Kirkland, 124 “127

with Greg Zimmerman, 377 “379

with Jason Duigou, 299 “303

with Jennifer Arndt, 95 “98

with Kevin Kocis, 21 “25

with Niral Modi, 266 “270

of potential project team members, 202 “205, 223

of potential vendors, 216 “220

with Rob Adams, 437 “441

with Tom Robinette, 405 “409

investment versus value, 49 “51

Iron Triangle

relationship to change from external forces, 327

role in creating strategy for quality, 374 “375

issue management meetings, holding, 329 “330

IT budgets . See budgets

IT Project+ exam objectives

Domain 1.0: IT Project Initiation and Scope Definition, 453 “458

Domain 2.0: IT Project Planning, 459 “468

Domain 3.0: IT Project Execution, Control, and Coordination, 468 “477

Domain 4.0: Project Closure, Acceptance, and Support, 477

overview of, 452

response limits, 452 “453

IT Project+ exam test-passing tips

for 39 project management processes, 483

for answering questions, 481 “483

for communication facts, 489

for days before the exam, 480

everything you must know, 483 “490

for EVM formulas, 484 “485

for formulas, 484

for human resource facts, 488

for organization structures, 484

practice testing process, 480 “481

for procurement facts, 490

for project cost facts, 486 “487

for project scope facts, 485 “486

for project time facts, 486

for quality management facts, 487 “488

for risk management facts, 489 “490

for WBS (Work Breakdown Structure) facts, 485

IT project management

advantages of, 57 “58, 95, 124, 221

benefits of, 21

is not a democracy , 208 “210

quality phases of, 362 “364

statistics on, 14

traps related to, 24, 60, 98, 225 “226

IT project management process, determining quality of, 358 “362

IT project managers

advice for, 25, 92 “93, 98, 226, 270, 303, 339, 379, 409, 441

advice on researching new technologies, 60

attributes of, 407

decision-making responsibilities of, 392 “394

five powers of, 74

guidelines for working with management, 84 “85

powers related to developing project teams, 197 “198

prioritization responsibilities of, 44 “45

providing inspiration to teams, 406

relationship to teams, 392

responsibilities of, 3, 7

skills required of, 360 “361, 392, 398 “399

IT vendors. See vendors