Index_S

S

SAN (storage area network), 5

schedule baseline, progress reporting against, 246-247

schedule control, 278, 280-281

schedule performance index, 301

schedule planning

activity definition, 104-105

activity duration estimates, 108-110

estimating techniques, 109-110

activity sequence, 105-107

dependency types, 106

network diagram, 107, 107

task dependency relationships, 106-107

exam essentials, 122-123

need for, 104

schedule development, 110-116

baseline, 116

critical path method (CPM), 111-114

duration compression, 114-115

milestones, 115-116

project management software, 115

time juggling in real world, 116-120

trade-offs, 303-305

phased delay, 304

schedule variance, 301

scope change control, 278, 279-280

scope creep, 78, 279

scope evaluation for IT project, 85-95

definitions for testing elements, 90, 95

deliverables, 86-87

loss of senior project technician, 89-90

mini-project consultant/vendor

relationships, 88-89

project crosses IT shops , 90

sidebar systems and undisclosed process

elements, 88

size of IT shop, 85-86

success criteria, 88

working with business clients , 87

scope of project

cost trade-offs and, 305

exam essentials, 95-96

management plan, 71, 77-79

overview, 71-85

planning, 71-72

trade-offs, 303

verification, 247

wineries e-mail and intranet systems, case

study, 91-94

scope statement, 71, 72-77

assumptions, 75

completion criteria, 74

constraints, 75

major deliverables, 73

and milestones, 247

product description, 73

project justification, 72-73

in project plan, 210-211

sample, 219

review and consensus, 77

sample, 76-77

success criteria, 73

time and cost estimates, 74

scoring model for project selection decision, 42

SDLC. See Systems Development Life Cycle (SDLC)

SDS (system design specification), 17-18, 347-348

security analysts, 49

security for project documentation, 215

SEI (Software Engineering Institute), 292

selection of project, 40-43

expert judgment, 43

selection criteria, 41-43

techniques, 41

sensitivity analysis, 183

sequence for activities in schedule planning, 82, 105-107

dependency types, 106

network diagram, 107, 107

task dependency relationships, 106-107

server administrators, 48

documentation for, 289

typical day, 118

server/system deployment, 4-5

severity of risk, 183

sidebar systems, 88

real world scenario, 89

sign-off on deliverables, 247

single business unit project, stakeholders for, 46

site acceptance testing, 284-285

Six Sigma, 176

'belts', 292

skills inventory worksheet template, 361, 361

SMS (Systems Management Server), 291

social interaction in kickoff meeting, 236-237

software

development, 3

life cycle, 8, 16

for project management, 115

software developer, 48

Software Engineering Institute (SEI), 292

sole-source documentation, 193

solicitation of vendors , 192-193

SOW. See statement of work (SOW)

spending, data collection on, 246

sponsor, 44

changing commitment of, 242-243

involvement in jeopardized project, 296

project manager caught between vendor and, 258-259

project plan review by, 216

project review for, 251

and vendor delays, 256

SQL Server, converting Access database to, 119

stability of scope, 78

staffing. See human resources planning

stakeholders

buy-in to charter, 54

communication with, 86, 188-189, 189

on milestones, 116

driving action, 43-51, 302-307

canceling project, 305

communicating performance deviations, 302-303

trade-off management, 303-305

final review by, 324-325

for IT project, 46-50

list in project plan, 211

sample, 219

matrix, 51

plan review by, 217

relationships, 241-244

client, 241-242

functional managers, 243-244

sponsor, 44, 242-243

and vendor delays, 256

standards

for IT quality control, 290-291

organizations for, 291

start to finish relationship, 107

start to start relationship, 107

statement of work (SOW), 38, 192, 257

progress report from vendors in, 253

statistical analysis, monitoring quality outputs through, 292

statistical sampling, 287

status date for earned value, 299

status reports , 250

storage area network (SAN), 5

storming stage of team development, 234

strategist, IT project manager as, 7

success criteria, 88

in scope statement, 73

case study, 91-92

sample, 76

successor task, 106

suppliers. See vendors

support plan in project plan, 213

sample, 221

system architects , 49

system deployment, 4-5

system testing, 284

systems analysis, 8, 17

systems analysts, 6, 49

systems design, 17-18

systems design specification (SDS), 17-18, 347-348

Systems Development Life Cycle (SDLC), 344-352

analysis phase, 345-347

design phase, 347-348

vs. Guide to the PMBOK, 350-352

implementation phase, 348-349

operations and support phase, 349-351

planning phase, 345

systems evaluation, 18, 348

systems implementation phase, 18

Systems Management Server (SMS), 291

systems operation and support, 18

systems planning phase, 16

systems request, 16

systems requirements document, 17, 347