Page 314 -
P. 314
project plan (continued) requirements, software (see software
estimates, 25 requirements)
resource list, 23, 25 resource list, project plan and, 23
risk plan, 23, 25–28 resources
schedule, 23, 25 allocation
SOW (state of work), 23 over-allocation, 61
SOW (statement of work), 24 to tasks, 54
WBS (work breakdown structure), 23 overhead, 55
project planning project plan, 25
introduction, 16 responsibility, managers and, 232–236
problems review of design, 133–134
engineering team, 31 reviews
leadership, 30 code review, 87
mid-course correction, 31 checklist, 90
project schedule (see schedule) code sample selection, 87–90
projects, multiple (see multiple projects) deskchecks, 84
diagnosing problems
R hero, 95
late found problems, 94
Rational Unified Process, iterative meetings, 95
development and, 128 importance of, 4
refactoring, 149–155 inspections
benefits, 154 acceptance, 81–84
code reviews and, 89 author expectations, 80
Decompose Conditional method, 152 commitment management, 92
existing projects, 167 implementation, 75
Extract Method, 151 meeting script, 78
Introduce Explaining Variable moderator selection, 76
method, 153 overview, 74
Replace Magic Number with Symbolic team selection, 75
Constant method, 152 work product inspection, 78
regression tests, 178 milestone reviews, 59
relationships outsourced projects, 271
distrust, padded estimates and, 50 overview, 74
engineering team, 31 pair programming, 91
leadership, 30 progress reviews, 59
project manager and schedule building and, 59
main stakeholder, 18 vision and scope document, 23
release readiness walkthroughs, 86
change control and, 123 risks
releases, phased release, vision and scope brainstorming, 26
document, 22 impact estimate, 27
Replace Magic Number with Symbolic mitigation plan, 27
Constant refactoring method, 152 project plan, 23, 25–28
reports, 179 risk planning script, 26
defect reports, 179 vision and scope document, 21
postmortem, 186–189 RUP (Rational Unified Process), software
repository process improvement and, 291
Subversion
creation, 141 S
sharing, 143
URL, access via, 140 sandbox model of version control, 138
version control system, 134 schedule, 23
requirements elicitation, 98 buffers, 62
discussion summary, 102–104 building, 54–66
observation, 101 commitment management, 69
use cases, 105–109 CPI (cost performance index), 65
306 INDEX
This is the Title of the Book, eMatter Edition
Copyright © 2009 O’Reilly & Associates, Inc. All rights reserved.