Index_P

---

P

People issues, 232–33

Performance measurements

determining, 18–19

development, 18

information management, 19

lessons, 19

process steps, 18

Performance reporting, 5–8

benefits, 5–6

components, 6

defined, 5

example format, 7

report criteria, 7

report development, 7

use of, 6

Performance Requirements Specification (PRS), 86

PERT charts, 187

Pilot development work pattern, 174–75

Planning decisions, 37–38

development, 37–40

output, 38

project tools, 38

Postmortem meeting report, 160

Pressures, 196–97

Process management, 17

Product assurance signoff letter (PASL), 107

Product Assurance Test (PAT), 104–5

defined, 104

minimum components, 104–5

Product deliverables, 106

Product Requirements and Specifications (PRSpec), 80–82

analysis areas, 81–82

defined, 80

key specifications, 80

Product signoff, 106

Product stability/integrity best practices, 223–27

Program Manager, 2

Progress review meetings, 39

Project Budget (PB), 66–67

defined, 66

template, 67

Project Closeout, 157–61

actions, 159–60

close-out paperwork (COP), 160

defined, 157

Disposition phase, 158

Disposition Plan, 158–59

postmortem meeting report, 160

project archiving, 160

ritual, 161

roadmap, 157

Project Continuation Approval (PCA), 74

Project Coordinator, 181

defined, 3

responsibilities, 3

Project Definition Document Notebook (PDDN), 56

Project Definition Document (PDD), 55–56

defined, 55

items, 55–56

Project Framework Rules Document (PFRD), 37–43

best practices decisions, 40–41

defined, 37

planning decisions, 37–38

relationship decisions, 41–42

tracking decisions, 39–40

Project Initiation phase, 31–51

Core Team and, 34–36

form, 33

PFRD, 37–43

PPDG, 47–51

requirements gathering, 43–45

roadmap, 31

SEP guidelines, 31–51

URD, 45–47

Project management, 193–95

communications ground rules, 194–95

early warning detection, 194

“give and take,” 202–3

process focus, 193

resources, 237

theory into practice, 193–94

tools, 233–35

Project Manager (PM)

appointment letter, 33–34

Core Team work, 9

defined, 3

in issue status, 14

negative reaction and, 202

responsibilities, 3

Project Objective Statement (POS), 55

Project Planning and Documentation Guide (PPDG), 47–51

defined, 47

outline, 47–50

as project Bible, 51

structure, 47

Project plans

confidence building, 192–93

realistic, building, 179–80

saving, 185

with templates, 182–85

updating, 185

Project Resources, 4

Projects

archiving, 160

business reasons for, 163–65

customers, 165

deliverables, 64

effective approach to, 178

integrity best practices, 206–14

kickoff meeting, 35

objectives, 165–66

risk factors, 188–90

success factors, 163

tools, 38

WBS, 185–87

Project Schedule (PS), 68

Project Sponsor, 2

Project team review minutes (PTRM), 74

Project Transition Letter (PTL), 92–93

Project WBS, 186

---