Professional Documents
Culture Documents
Index
Index
Index
nonfinancial selection models, 40–43 implications for organizing projects, overhead costs, 145
checklist models, 40–41 86–88 direct, 145
multi-weighted scoring models, 41–43 nature of, 81–83 general and administrative (G&A), 145
nonproject factors, in project estimation, 131 in project estimation, 131 oversight. See project audit; project
Noreen, E., 302 relationship with project structure, 88 offices (POs)
normal closure, 516–517 organizational culture review overtime
normal conditions in project estimation, questionnaire, 528 in accelerating project completion,
132–133 Organizational Project Management 308, 310
norming stage of team development, 378 Maturity Model (OPM3), 529 cross-cultural attitudes toward, 560
Nortel Networks Corp., 547 organization breakdown structure (OBS), ownership, in team building, 399
Northridge earthquake (California), 308 109, 110, 113 oyster projects, 50
Norton, D. P., 56 integrating with organization,
not invented here (NIH), 379
Novell, Inc., 271
113, 114
time-phased budget and, 274–276 P
numbering activities, 179 organization politics pace of life, 555
project managers and, 361 padding estimates, 131
performance indexes, 476 position-related currencies, 346–347 classification of, 37–38, 43, 50
performance measurement. See project positive synergy, 375–377 defined, 6–7
monitoring information system Posner, B. Z., 125, 353, 360, 366, 367, everyday work versus, 7
performance reviews, 534–536 395, 409 examples of for college students, 5
individual, 535–536 post-implementation evaluation, 532–536 implementing organization through,
project manager, 534 individual reviews, 535–536 33–34
team member, 532–534 performance reviews, 534–536 program versus, 7
360-degree reviews, 535, 536 team evaluation, 532–534 size, 15
performing stage of team development, 378 360-degree reviews, 534–535, 536 project audits, 516, 521–532
Perkins, Dennis N. T., 354, 354n postproject retrospectives, 525–529 bigger picture of, 529–532
perpetual closure, 517 Powell, M., 93 data collection and analysis, 524
Perrow, L. A., 328 premature closure, 517 external consultants in, 525–526
personal integrity, 360 Pressman, R. S., 155 guidelines for conducting, 522–525
personal-related currencies, 347, 348 Price, M., 56 importance of, 521
PERT (program evaluation and review PricewaterhouseCoopers, 547 in-process, 521
technique), 140, 216, 240–244 Primavera, 385 initiating and staffing, 522–523
development of, 240 principled negotiation, 435 nature of, 521–522
hypothetical example of, 242–244 priorities postproject, 521
Pesch, E., 291 changed priority closing stage, 518 project maturity models in, 529–532
Peters, J. F., 538 leading by example, 353 project offices (POs) and, 522, 523
Peters, Lawrence H., 366, 389, 389n low-priority projects, 395 reporting, 524–525
Peters, L. S., 56 priority matrix, 107 retrospectives, 525–529
Peters, T., 20, 353, 366, 409 priority system in project selection, senior management in, 522
Pethokoukis, J. M., 583n 34, 36–37 Project Baseline Budget, 470–471
Pettegrew, A. M., 93 project reward systems, 391–392 project buffers, 296
phase estimating, for project times and responsibility for prioritizing projects, project charters, 11–12, 105–106,
costs, 141–143 47–48, 50 project classification
Philippines, 547, 549, 553 priority matrix, 107–108 in project selection, 43
physical characteristics, in organizational priority system, 34, 36–37, 47–48, 50 types of projects, 37–38, 50
culture, 84–85 priority team, 42 project closure, 516. See also closing stage
Pich, M. T., 232 proactive approach, 360 wrap-up closure activities, 516,
Pinto, J. K., 56, 102, 124, 129n, 130n, 154. probability analysis, in risk assessment, 518–521
232, 301, 302, 351n3, 367, 444 215–216 project code names, 49
Pippett, D. D., 538 problem identification, in group decision project communication plan, 119–121
Pitagorsky, G., 124 making, 393 project control process, 461–462
planned value (PV) problem solving project complexity, in project
costs included in, 467–468 in leading by example, 355 estimation, 130
defined, 276, 466 in recruiting project members, 382 project cost baselines, 273–278
in time-phased budgets, 276 process breakdown structure (PBS), 102, Project Cost–Duration Graph, 313–321
variance analysis, 468–469 116–117 crashing, 314–321
planning decisions, 384 procrastination (student syndrome), 296 determining activities to shorten,
planning horizon, in project Procter and Gamble, 27, 583 314–316
estimation, 130 procurement management project direct costs, 314
planning stage, 8. See also project estima- components of, 452 project indirect costs, 313–314
tion; resource scheduling Request for Proposal (RFP), 44, 45, simplified example, 316–318
of project life cycle, 8, 396 63–64, 452 time reduction decisions, 320–321
sources of conflict, 395–396 product backlog, 588–589 using, 318–319
PMBOK (Project Management Body of product life cycle, compression of, 12, 27 project definition. See defining stage
Knowledge), 223n, 232 product owner, 586–587 project duration, 305–323
PM Network, 538 program(s) acceleration options when resources
PMI. See Project Management defined, 7–8 are constrained, 310–312
Institute (PMI) project versus, 7 acceleration options when resources
PMI Standards Committee, 124 program evaluation and review technique are not constrained, 308–310
PMI Today, 4n (PERT), 140, 216, 240–244 cost as issue in, 321–323
Poli, M., 94 program goals, 8 lags and, 183–186
Porras, J. I., 88, 92 program management, 8 practical considerations, 318–321
portfolio management, 37–38 progress measurement. See project Project Cost–Duration Graph,
senior management input to, 48–49 monitoring information system 313–321
portfolio risks, balancing, 50–51 project(s), 6–12 in project estimation, 131
Portland General Electric Company, 480 characteristics of, 7 rationale for reducing, 306–307
654 Index
project estimation, 129–151. See also cost Project Management Body of Knowledge understanding strategy, 28
estimates; resource estimates; time (PMBOK), 223n, 232, 342, 594 work breakdown structure (WBS) and,
estimates project management career paths, 3–5 108–109
accuracy, 142 certification and training, 4 working in a multicultural environment,
adjusting estimates of specific tasks, examples of, 4–5, 10–11 555, 565–568
146–148 projects given to recent college project measurement. See project monitor-
error reduction, 134 graduates, 5 ing information system
factors influencing quality estimates, Project Management Consultants, 431 project meetings, 383–387
130–132 Project Management Institute (PMI), 4, 6, establishing ground rules, 384–385
guidelines for times, costs, and 20, 35, 35n5, 367, 465, 480, 529, project kick-off meeting, 383
resources, 132–133 532, 594 scrum, 587–589
importance of, 130 project management maturity, 529–532 subsequent meetings, 386–387
learning curves in, 139, 157–161 project management office (PMO), 532 team identity and, 387–388
level of detail, 143–144 Project Management Professional (PMP), project monitoring information system,
mega projects, 149–150, 152 4, 594 459–486
refining estimates, 146–148 project management software baseline changes, 483–484
time and cost databases, 148 Microsoft Project, 385, 478, 511–513 costs and problems of data acquisition,
top-down versus bottom-up, 134–143 Primavera, 385 485–486
types of costs, 144–146 project management structures, 68–81 critical-chain project management
project evaluation, 532–536 dedicated teams, 71–72, 79, 88 (CCPM) in, 300–301
in closing stage, 532–534 functional organization, 68–70 data collected in, 460–461, 485
statement of criteria, advantages and disadvantages, 69–70 earned value (EV) cost/schedule
project facilitators, 515, 525–529 matrix arrangement, 75–81, 88–89 system, 462, 464–469, 505–511
roles, 525–529 organization considerations, 79 examples of use, 464, 480
selecting, 525–526 project considerations, 79–81 forecasting final project cost, 479–481
project governance, 15–16 relationship with organizational indexes to monitor progress, 475–479
alignment of projects and culture, 88 Microsoft Project and, 478, 511–513
organizational strategy, 16 project managers, 339–362. See also process overview, 467
governance team in portfolio system, leadership; project teams project control process, 461–462
49–50 building trust, 357–359 reports and reporting in, 460–461,
nature of, 15–16 career paths. See project management 470–475
projectitis, 74 career paths scope creep, 483
projectized organization, 72–73, 79 certification and training, 4 status report, 470–475, 478, 481
project kick-off meeting, 383 as client account executives, 441 structure of, 460–461
project life cycle, 8–9 conductor metaphor and, 344 time performance, 462–464
defined, 8 dependencies of, 342–344 tracking Gantt, 462–463
project cycle times, 8 developing high-performance project project networks, 163–189
sources of conflict over, 395–396 teams, 381–399 activities in, 163–164, 166–170
stages of, 8–9. See also closing stage; ethics and, 356 activity numbering, 179
defining stage; executing stage; functional manager versus, 9 activity-on-arrow (AOA), 167–170
planning stage law of reciprocity and, 345–348 activity-on-node (AON), 167–170
project management. See also project leading at the edge, 354 activity-on-arrow (AOA) versus,
teams leading by example, 353–355 167–168
critical-chain project management “management by wandering around” backward pass, 173–175
(CCPM) and, 301 (MBWA), 350–351 forward pass, 171–173
current drivers of, 12–15 managing expectations, 351 backward pass-latest times in, 173–175
current examples of, 5, 13–14 managing upward relations, 351–353 basic rules for developing, 166
impact of, 4 motivating for extraordinary calendar dates, 182
importance of, 3–5 performance, 320 computers in developing, 179–182
integration of, 15–16 nature of, 9–10 concurrent engineering, 184–186
leadership versus, 339–341 performance reviews, 534–536 critical activities in, 176, 184
new-school thinking of, 28 professional training and certification, 4 critical path method (CPM), 163, 166,
old-fashioned view of, 344 project leadership versus, 340–341 167, 171, 175–177, 178, 187, 317
old-school thinking if, 28 project teams, 9, 11–12, 342 development
project size and, 15, 144, 147 qualities of effective, 359–362 basic rules, 166
socio-technical approach to, 17–18 role of, 9–10 computer use in, 179–182
sustainable practices and, 12–14 scrum masters as, 587 from work breakdown structure
Dell Children’s Medical Center, 14 skill set, 5 (WBS), 164–166
London Olympics (2012), 150 social network building, 348–355 yellow sticky approach to, 167
Studio Roosegaarde, 13 stakeholders and, 341–344 extended network techniques, 182–188
Index 655
release planning, 587 time-phased budget baseline, 251, risk response control, 225–226
religious factors, 551 273–278 change control management, 226–229
Relyea, Dave, 585 types of resource constraints, 254–255 risk register, 225–226
Remington, K., 56 resource smoothing, 252, 256–257 risk response development, 216–219
reports and reporting responsibilities avoiding risk, 217
change request forms and logs, client assumption of, 322 contingency funding, 223–225
227–229 governance team, 49 contingency planning, 219
errors, 226 in project estimation, 132 mitigating risk, 216–217
final project report, 516–518 in risk response control, 226 opportunity management, 223
in outsourcing, 428 top management, 47 retaining risk, 218
project monitoring information system, responsibility matrix (RM), 117–119 time buffers, 225
460–461, 470–475 retaining risk, 218 transferring risk, 217–218
by project offices (POs), 523 retrospectives in closing stage, 525–529. risk response matrix, 220
status report, 470–475, 478, 481 See also project audits risk retention, 218
Request for Proposal (RFP), 44, 45, 63–64, archiving, 529 risk severity matrix, 214
424–426, 452 independent facilitators, 525 risk transfer, 217–218
reserves, 224–225 lessons learned, 526, 527 Ritti, R. R., 392, 392n, 409
budget, 224 methodology, 526–529 River of Doubt (Millard), 552
management, 224–225 reviews, in outsourcing, 431–432 Rizova, Polly S., 89, 89n, 94
resource bottlenecks, 272, 296 reward systems, 391–392. See also Robb, D. J., 367
resource buffers, 296 incentives; project reward systems Rodriguez, P., 572
resource conflicts, 36–37 RFP (Request for Proposal), 44, 45, 63–64, Roemer, T. R., 328
resource-constrained projects, 252–253, 424–426, 452 Rogers, Will, 207
255, 257–269 Ricks, D. A., 573 Romanoff, T. K., 535, 538
computer demonstration, 262–269 RIM, 306 Rondon, Candido Mariano da Silva, 552
EMR project example, 262–269 risk Roosevelt, Theodore “Teddy,” 552
examples of, 254 avoiding, 217 Rosen, B., 408
impacts of, 266 defined, 207 Rosenblatt, A., 202
nature of, 255, 257–258 retaining, 218 Ross, Jerry, 539
parallel method of applying heuristics, sources of project, 209 Ross, M., 147, 154
258, 259 transferring, 217–218 Rothaermel, F. T., 443
resource allocation methods, 255–262 risk assessment, 210, 212–216 Rothengatter, W., 149, 154
resource conflicts and multitasking, Failure Mode and Effects Analysis Rourke, D. L., 154
36–37 (FMEA), 215 Rousculp, M. D., 232
resource estimates, 130–148 probability analysis, 215–216 Royer, I., 538
factors influencing quality of, in project estimation, 133 Rubinstein, J., 269, 291
130–132 risk severity matrix, 214 Ruekert, R. W., 93
guidelines for, 132–133 scenario analysis, 213–214 Russia, legal/political factors, 547
level of detail, 143–144 risk avoidance, 217 Ryan, Frank, 135n
phase estimating, 141–143 risk breakdown structure (RBS), 210–211
refining, 146–148
top-down versus bottom-up, 134–143
risk event graph, 209
risk identification, 210–212 S
resource pool project office, 80 risk management process, 208–230 “sacred cow,” 35, 42, 44
resource scheduling, 250–279 balancing portfolio risks, 50–51 Saffo, P., 408
assessing resource allocation, 262 components of, 209–210 Salehipour, A., 501
assigning project work, 271 cost of mismanaged risk, 207–209 Samsung, 306
benefits of, 270 examples of, 207–209, 218, 221 Samsung Galaxy 7, 306
critical-chain project management international projects and, 548 Sankaran, S., 366
(CCPM), 294–303 proactive approach, 209 Santayana, George, 515
to develop project cost baseline, 251, process overview, 210 Sashittal, H. C., 93
273–278 risk, defined, 207 Saudi Arabia, cross-cultural factors in,
multiproject resource schedules, risk assessment, 210, 212–216 560–561
272–273 risk identification, 210–212 Saunders, C., 573
process overview, 252–254 risk response control, 210, 225–226 Sayles, Leonard R., 351n2, 352n, 360, 367
resource-constrained projects, 252–253, risk response development, 210, scaling, 592–593
255, 257–269 216–219 scenario analysis, 213–214
resource smoothing in, 252, 256–257 sources of project risk, 209 schedule. See project schedules
splitting activities, 269 risk mitigation, 216–217 schedule performance index (SPI), 476
time-constrained projects, 255, risk profile, 211 schedule risks. See also resource scheduling
256–257 risk register, 225–226 in contingency planning, 222
Index 657