Index_S


S

schedule at completion (SAC), 33, 35

schedule-oriented practices, 236–239

schedule performance index (SPI), 31–35, 208–211

schedules, 55

and cost/performance, 195

for deliverables, 130–131

development of, 21–22, 55

early, 23, 24

EV as measure of, 30

late, 23–25

master, 55

network analysis for determining, 54–55, see also network analysis

and planned/actual costs, 29

in project plan, 137

in project plan appendix, 132

techniques for developing, 10

validating estimates of, 145–148

schedule variance (SV), 30–31, 35, 207, 209

scope

product, 48, 50, 51

project, 44, 45, 48, 51, 159

SOW section for, 88

verification of, 247

SDLC, see software development life cycle; systems development life cycle

self-awareness, 108

self-management, 108

sign-off

by customer, 67, 248–249

design, 63

on project plan, 149–150

skills

interpersonal, 106, 107, 109

of project manager, 100–105, 113

of project team members, 223–224

slack, 25

software development, 3, 220, see also rapid development

software development cycles, 5

software development life cycle (SDLC), 8, 41, 42

SOWs, see statements of work

special customer conditions, 93–94

specifications, product, 143, 191

speed, development, see rapid development

speed-oriented practices, 236–238

SPI, see schedule performance index

staffing, project team, 111–112

stakeholder analysis, 119–121

stakeholder management, 116–125

and definition of stakeholder, 117–118

evaluation of response in, 124–125

identification of stakeholders in, 118–119

stakeholder analysis in, 119–121

strategies for, 121–125

stakeholders, 12, 117–118

agendas of, 129

analysis of, 119–121

identifying, 118–119

informing on status of, 124

lack of buy-in from, 228

negative reactions of, 123

plan sign-off by, 149

standards, 12–13, 94

statements of work (SOWs), 82–89

combination, 85–86

design and detailed specification, 83–84

format for, 86–89

as governing document, 95

for internal projects, 96

level-of-effort, 84–85

for maintenance phase, 68

performance-based, 85

writing, 80–82, 86

status reports, 213–214

subfunctions, allocation of, 187–188

subsystems, testing, 65

subsystems level, 17

subtasks, 17–18

success, 1, 106

surveys, 72, 263–267

SV, see schedule variance

synthesis procedure, 188–189

systems

construction of, 64

delivery of, 66

effectiveness of, 58, 60

installation of, 70

IT, 3

testing of, 70

systems architecture, 51–52, 188–189

systems definition, 184–185

systems development life cycle (SDLC), 39, 41–43

in concept phase, 48–52

in customer service and system maintenance phase, 72–73

in planning phase, 57–66

relationship of project life cycle to, 41–43

in termination phase, 70

systems engineering, 183–200

allocation of functions in, 187–188

architectural design in, 188–189

functional analysis in, 187

management plan for, 143

management techniques for, 191–193

optimization in, 189–191

philosophy of, 194–197

and project management, 183–184, 197–199

requirements analysis in, 185–187

specification generation in, 191

systematic and repeatable process in, 185




Managing Information Technology Projects
Managing Information Technology Projects: Applying Project Management Strategies to Software, Hardware, and Integration Initiatives
ISBN: 0814408117
EAN: 2147483647
Year: 2003
Pages: 129
Authors: James Taylor

Similar book on Amazon

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