Index_P


P

paper-integrated PERT schedule, 74
Patton, George S., on saving blood, 155
PCs, 17
penalty box (project team), 87 “88
people costs, 35 “36
performance goals (in PRD), 39 “40
PERT schedule, paper-integrated, 74
phase review presentations
in Beta Phase, 225
in End of Life Phase, 277
in General Availability Phase, 262
in Project Design Phase, 112
in Project Development Phase, 152
in Quality Assurance Phase, 193
in Release Phase, 245
phase sign-off
in Beta Phase, 225 “226
in End of Life Phase, 277
in General Availability Phase, 262
in Project Design Phase, 113
in Project Development Phase, 152 “153
in Quality Assurance Phase, 193
in Release Phase, 245 “246
PLC, see project life cycle
positioning, project vs. corporate, 169
Post-it Notes exercise, 72 “74
PRD, see Project Requirements Document
pregnant processes, 133, 135
prerequisites (in PRD), 40
presentation
of Beta Phase, 208 “221
of End of Life Phase, 270 “275
of General Availability Phase, 255 “260
of Project Concept Phase, 41 “49
of Project Design Phase, 92 “106
of Project Development Phase, 137 “148
of Quality Assurance Phase, 174 “187
of Release Phase, 235 “242
press kit development, 170
˜ ˜problem projects, xiii
problems, minimization of, 133 “135
Project Announcement Plan
advertising in, 172
in Beta Phase, 225
and contact with journalists , 170 “171
contents of, 168 “172
creation of, 165 “168
date for announcement in, 171
deliverables for, 171
message development in, 169 “170
press kit development in, 170
in Quality Assurance Phase, 192
Release Phase role of, 235
Project Concept Phase, 4 “5, 15 “53
Business Requirements Document in, 24 “32
deliverables by department in, 52 “53
evaluation of project feasibility in, 19 “23
Feature/Functionality report in, 33 “35
lead person for, 16
management recommendations for, 50 “52
objective of, 4 “5, 15
presentation of, 41 “49
Project Concept Plan in, 35 “38
Project Requirements Document in, 38 “41
review of project ideas in, 17 “19
and sources of concepts, 15 “16
steps in, 15, 16
project concept plan, 35 “38
Project Design Phase, 5, 57 “114
Baseline Cost Document creation in, 75 “84
design review in, 65 “67
documents created in, 112 “114
Feature/Functionality report update in, 70 “71
focusing/ channeling team energy in, 86 “92
functional roles in, 57 “60
integrated schedule creation in, 71 “75
IT s role in, 62 “65
management recommendations for, 106 “109
objective of, 5, 57
presentation of, 92 “106
Project Requirements Document up-
date in, 84 “86
project team creation in, 60 “61
project team roles in, 67 “70
summary of, 109 “114
Project Development Phase, 5, 117 “153
Baseline Cost Document update in, 136 “137
beta plan in, 122 “129
development review in, 130 “131
documents created during, 151 “153
functional roles in, 117 “120
integrated schedule update in, 136
management recommendations for, 148 “149
minimization of problems in, 133 “135
objective of, 5
presentation of, 137 “148
tasks completed during, 120 “122
team member tasks in, 149 “151
team recommendations for, 149
team responsibilities in, 131 “133



Effective IT Project Management
Effective IT Project Management: Using Teams to Get Projects Completed on Time and Under Budget
ISBN: B000VSMJSW
EAN: N/A
Year: 2004
Pages: 105
Authors: Anita Rosen

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