Effective IT Project Management: Using Teams to Get Projects Completed on Time and Under Budget

R

references, vendor, 128 “129

release date, 167 “168

after competition s release, 168

estimated, 37

executive ˜ ˜fixing of, 50

released projects, maintenance of, 253 “255

Release Phase, 7, 229 “246

documents created during, 245 “246

functional responsibilities in, 229 “232

management recommendations for, 242 “243

presentation of, 235 “242

roles/responsibilities of team members in, 243 “245

tasks completed during, 233 “235

team recommendations for, 243

Release Plan, 159

in Beta Phase, 208, 226

confirming readiness of, 208

in Quality Assurance Phase, 172 “174, 192 “193

staging plan in, 173

releases (of new operating systems), 254 “255

required functionality (in PRD), 40

Resource Matrix, 20 “22

review committees

for beta, 198

for design, 66

reviews

beta, 198

design, 65 “67

development, 130 “131

General Availability, 249, 251

of project fit and maintenance costs, 249

yearly, 249 “252