Index_T

---

S

Sales entry module, 28

Sales management, 23

Salespeople, 168

dealing with customers, 219

managing objections, 222-225

SAN (storage area network), 173

Satellite video, 103

Schedules, 107-110; see also Status of projects

adjusting, 141-143

changes in, 230

documenting, 151, 152

drafting, 115-117

elements of, 122

handling challenges to, 140

logic, 123

objections to, 222

planning tools, 124-125

Scope, 5-8; see also Requirements; Specifications

Apollo Program, 7

and budget management, 168-169

documenting, 151

implementing, 257-259

progress to design specifications, 6

vs. requirements, 7-8, 27-28, 258

and risks, 17

vs. specifications, 7-8

Scope creep, 89

managing, 232

in project accounting, 161

reacting to, 230-232

recognizing, 229-230

Second road, in airport construction project, 35-36

Security, 203

in budgetary laundry list, 172

handoffs, 195

and slippage of project, 141

Self-confidence of project managers, 295-296

Self-promotion, 206

Senior managers, 241

communications skills of, 252

conflict avoidance, 249-250

grasp of theory and details, 251-252

management style of, 244-245

political tendencies of, 247-248

problem-solving skills of, 245-247

procrastination of, 248-249

risk aversion, 250-251

September 11 attacks, 96

Servers

in budgetary laundry list, 172

changing, 144

delay in testing of, 147

migration, 58

monitoring tools, 51

Service bureau, 79-80

Service level agreement, see SLA

Service levels, 235-236

Shared directories, 53

Shortfalls in budget, 173-174

Shrink-wrapped software, 180

Shutdown processes, 202

Silicon chips, 7

Simple Network Management Protocol (SNMP), 203

Single-deliverable projects, 257

Site availability, 15

Six Sigma, 19, 78, 283, 284

Skillsets, 20

SLA (service level agreement), 19

components of, 236

and contract budget, 80

Slippage, 264; see also Schedules

date-constrained tasks affected by, 142

factors in, 141

SNMP (Simple Network Management Protocol), 203

Soft metrics, 19

Software

in budgetary laundry list, 172

information, 202

releases, 15

Software development manager, 12

Solicitation skills, of project managers, 287-289

SONET, 46

Source data in budget management, 164-169

Sources of information, 22

SouthPointe project, 138

lessons learned in, 271-273

meeting agenda, 158

SOW (support of work), 107, 113, 116

Specifications, 6; see also Requirements; Scope

Apollo Program, 7

documenting, 151

progress from scope to, 6

vs. requirements and scope, 7

turning requirements into, 40-42

Speeds and needs approach, 220-222

Sponsors, 12

Staff

augmentation of, 180

change in, 230

headcount, 20

Stakeholders, 3

assessing critical paths with, 118

inducing buy-ins from, 31

sharing assumptions with, 37

Standardization of nomenclature, 19

Standards, in design assumptions, 163

Starting points, 261-262

Start-up processes, 202

Status of projects, 127; see also Projects

adjusting schedules, 141-143

Answer Man, 130-132

and boss management, 251

checking against project plan, 135-137

documenting, 152

generic reactions to, 140-141

guidelines, 140

handling challenges to schedules, 140

issues list, 143-146

late, 146-147

monitoring tool, 136

politics of bad news and escalation, 128-130

and quality of deliverables, 147-148

reports, 137-139

rules of engagement, 127-128

Storage area network (SAN), 173, 183

Storage management, 203

Stress test, 61

Success metrics, 18-20

Superman factor, 297-298

Supervisors, 242-243

communications skills of, 252

conflict avoidance, 249-250

grasp of theory and details, 251-252

management style of, 244-245

political tendencies of, 247-248

problem-solving skills of, 245-247

procrastination of, 248-249

risk aversion, 250-251

Suppliers, and slippage of project, 141

Support, 20-21

for legacy systems, 14

of vendors, 180

Support groups, 145

Support requirements, 198-201

Swing space, 87

Switches, 21, 46, 112

System design and architecture, 30, 61

---