|
|
 |
|
|
|
Under Pressure and On Time
|
|
|
Author |
|
Ed Sullivan
|
|
|
Pages |
304
|
|
Disk |
N/A
|
|
Level |
Intermediate
|
|
Published |
04/04/2001
|
|
ISBN |
9780735611849
|
|
ISBN-10 |
0-7356-1184-X
|
|
Price(USD) |
$29.99
To see this book's discounted price, select a reseller below.
|
|
|
|
|
|
|
|
|
Index
A
accuracy of UI in early development, 174
adaptability, 9
airplane analogy, 206
alpha release, 195
alternating development leads, 161
analyzing performance, 93
applied research. See research
assessment grids, 149
assumptions about technology, 158, 164
attitude, 6
problems caused by ranking, 65
automation, improving, 253
automation engineers, 53
automation testing, 93
benefits of, 102
of builds, 128
importance of, 122, 134
of release candidates, 239, 245
of software configurations, 117
test beds, 52–53, 104
of UI elements, why not to use, 104
B
backing up, 79
balancing skill sets and
functional expertise, 59
base levels, 194
getting back on track after missing, 220
working overtime to meet, 216
behavior, changes in, 66
benefits, how to distribute, 64
beta program administrators, 58
beta releases, 196
beta sites
communicating with, 229–30
feedback from, 235
newsgroups for, 229
non-disclosure agreements with, 229
partners as, 228
recruiting, 228, 234
and release candidate testing, 240
rewarding, 232
sending software to, 230
sources for, 228
surveying, 231
testimonials from, 231
beta testing, 222. See also release candidate testing
adding features during, 200
benefits of, 113, 222
call-handling systems for, 229
common mistakes, 224
ending, 231
feedback from, 235
information management, 235
infrastructure for, 235
manager, 232
and marketing, 223
marketing betas, 225
measuring progress, 230
phases, 224
plan for, developing, 113
purpose of, 224
questions to ask, 226
scheduling, 200
sites (see beta sites)
staff augmentation with, 223
starting, 226
testing before, 234
time allocation, 235
bonuses, 36
planning, 64
referral, 16
breaking builds, 129
bug tracking, 85-92
bug-fixing
closure, 117
during testing, 112
responsibility for, 50
time to allow for, 108
verifying, 89, 92
build environment, 127
maintaining consistency of, 79, 84
responsibility for maintaining, 56, 124
in source code management systems, 79
building corporate culture, 67
building confidence, 158
building infrastructure, 253
build labs, 128
build machines, 127-28
builds, 125
breaking, 129
cycles, 133
daily, selling team on, 133
environments (see build environment)
evaluation of, 128
failure, notification of, 128
final (see release candidate testing; beta testing)
identifying specific, 127
importance of, 125
last known good (LKGB) directory, 128
machines for, 127
machines for, virus-checking software and, 128
metrics for, 129
most recent (MRB) directory, 128
notification of failure, 128
numbers of, 127
penalties for breaking, 129
smoke testing of, 128
streamlining, 126
target directories, 128
testing, 128
burnout, 161, 255
C
call-handling systems for beta testing, 229
candidates
ability to cooperate, 7
areas of expertise, 4
attitude, 6
behavior, 7
commitment, 6
deciding to hire, 32
defining criteria for, 4
evaluating, 23–24, 27
financial impact of hiring poorly-qualified, 10
finding (see finding candidates)
great vs. perfect, 8
poorly-qualified, 9
interviewing (see interviews)
making an offer, 33
requesting work samples, 31
screening by phone, 25
selling positions to, 31
testing abilities of, 30
cash bonuses, 251
celebrations, 249
centralized decision making, 45
change, managing, 88
change rates, 92
changes
in employee behavior, 66
implementing, 213
questions to ask before making, 215
requests for, assessing, 215
check-in testing, factors for success, 106
checking files in/out, 129
conflict over, 96
checkpoints, 208
external, 195
getting back on track after missing, 220
stabilization periods before, 196
working overtime to meet, 216
closer, 32
advantages of using, 38
closure
benefits of, 248
celebrations, 249
delivering the bits, 248
Easter eggs, 252
final e-mail, 249
post-mortem meetings, 252
preparing for next project, 252
private recognition, 251
public recognition, 250
rewards, 251
closure rates, vs. open rates, 90
code
checking in, 129
freezing, 225
integrity of, 76, 126
iteration in, 183
Code Write, 96
cold calling, 17
defending against, 18
colleges, recruiting at, 17
commitment, 6
committed dates, 192
common queries, 89
communication, 45
between development teams, 55
of success and failure, 212
company growth, keeping culture intact during, 74
company history as part of corporate culture, 68
compensation, 35, 64
bonuses, 36 (see also bonuses)
stock options, 36
competitors, catching up with, 150
complexity of projects, managing, 80
confidence
building, 158
from elitism, 68
configuration testing, 117
conflict over checked-out files, 96
consensus, 216
consistent build environment, 79, 84
consultants. See contractors
contractors
benefits of using, 19
how to use, 215
contributions, recognizing employee, 63
cooperation, 7
corporate culture, 66-68
building, 67
changing, 74
company history as part of, 68
defining values for, 68
elitism and, 68
good vs. bad, 67
growth, keeping intact during, 74
having fun as part of, 69
impact on employee performance, 67
importance of, 67
keeping intact during growth, 74
processes as part of, 70
testing as part of, 115
values for, defining, 68
cost/benefit ratio of new processes, 71
cultivating elitism, 68
customer feedback, identifying user problems with, 142
customers
anticipating needs of, 149
as beta testers, 228
development teams, interaction with 69
references from, 164
release candidates, signing off on, 243
D
daily builds, 133, 209. See also builds
daily smoke testing
of builds, 128
defined, 107
data integrity, 97
dates, committed, 192
de-installation procedures, 110
deadlines, 208
debuggers, 93
decision to hire, 32
decision-making, 213
centralized, 45
consensus and, 216
decline in employee performance, 66
defining cultural values, 68
defining roles and responsibilities, 59
delivering the bits, 248
delivery dates, 194
descent teams, 241–42
descriptions, job, 12
designated responsible individuals, 244
dev leads
alternating, 161
roles and responsibilities, 49
developers
burnout, avoiding, 161
how many to hire, vs. QA engineers, 59, 101
responsibilities during testing, 101, 115–16
developing UI prototypes, 166, 175
development
and research, 160
scheduling, 188
development leads, 45
alternating, 161
roles and responsibilities, 49
development processes
adding new, 71
evaluating, 71
for managing change, 152
new, 71
as part of corporate culture, 70
QA, 105–6
successful, characteristics of, 71
updating, 253
development teams. See also specific team names
augmenting with external teams, 214
communication between, 55
communication with project managers, 45
external teams, augmenting with, 214
importance of proper staffing, 42
interaction with customers, 69
interaction with project managers, 43
introducing processes to, 71
leadership by project manager, 48
leads (see development leads)
linking together, 48
processes, introducing to, 71
project manager and, 44
QA teams, separation from pros and cons, 51
release candidates, signing off on, 243
schedule ownership, 192
separation from QA teams, pros and cons, 51
staffing, importance of, 42
development tools. See specific tool names
documentation
human factors engineers and, 182
importance to UI, 174
responsibility for providing, 53
documenting
prototypes, 167
research, 162
E
Easter eggs, 252
eating your own dog food, 115
editing files simultaneously, 77
educational material, responsibility for providing, 53
elitism, cultivating, 68
employee organization. See ranking
employee performance
corporate culture, impact on, 67
decline, discussing, 66
defining expectations, 145
impact of corporate culture on, 67
when to analyze, 169
employee referrals, 15. See also referral programs
employees
augmenting with beta testing, 223
burnout, 161, 255
changed behavior in, 66
contributions, recognizing, 63
finding (see finding candidates)
hiring (see candidates; finding candidates)
new, how to rank, 63
performance decline, 66-67
retaining (see retaining employees)
ending interviews, 37
engineering
credibility, 193
functions of, 49
engineers
automation, 53
human factors (see human factors engineers)
release (see release engineers)
software, 50
technical support, 57, 243
entrepreneurial responsibility of project managers, 45
environment folder, 83
evaluating
processes, 71–72
prototypes, 167
technology, 163–64
exit interviews, 39
expertise
balancing with skill sets, 59
of candidates, 4
defined, 5
external milestones, 195
external teams, augmenting QA/development with, 214
extracurricular activities, 36
F
failure to deliver, 212
fairness in ranking, 73
favoritism, avoiding, 73
feature design, 50
feature implementation
and parallel testing, 189
responsibility for, 47, 50
feature leads, 50
feature testing, 108
responsibility for, 50
when to do, 108
features
adding, during beta testing, 200
adding, questions to ask before, 215
beta testing, adding during, 200
change requests, assessing, 215
cutting to make schedules, 215
defining tasks for, 194
design of, responsibility for, 50
focusing tasks on, 190
implementation, responsibility for, 50
removing, 19
installation procedures, adding to, 132
feedback, customer, 142
feedback from interviews, 29
file history, 76, 79
file version control, 76
finances, impact of bad hiring decision on, 10
finding candidates, 11, 18
by cold calling/targeting, 17
at colleges, 17
easiest methods of, 18
with employee referrals, 15
with professional recruiting firms, 16
on recruiting Web sites, 12
on short notice, 19
at trade shows, 17
by using company’s Web site, 13
fixed failed counts, 92
fixing bugs
closure, 117
during testing, 112
responsibility for, 50
time to allow for, 108
flight plan. See airplane analogy
focusing research, 162
follow-up on candidates who reject an offer, 33
functional expertise. See expertise
G
graphical materials, responsibility for creating, 181
grids and software requirements, 149
grouping files in source code management systems, 77
growth, keeping culture intact during, 74
H
having fun as part of corporate culture, 69
help, online, 182
hierarchical organization of employees. See ranking
hiring contractors, 19
hiring decision, 32. See also candidates
history of company, as part of corporate culture, 68
history, file, 76, 79
human factors, scheduling for, 189
human factors engineers, 180–82
and documentation, 182
and product packaging, 182
and project execution, 182
roles and responsibilities, 55, 180
and software presentation, 181
and UI prototypes, 180
human frailties, 220
I
identifying key tasks, 173, 176
implementing features, responsibility for, 47, 50
Imports folder, 84
incentives, 64
informing employees of ranking policy, 73
infrastructure, building up, 253
inner circle, 62
when to promote to, 66
innovation, inhibited by UI techniques, 184
installation procedures
adding features to, 132
building, 131
building/maintaining, responsibility for, 56
creation/validation, responsibility for, 109
de-installation, 110
importance of, 109, 130
kit, 132
maintaining, responsibility for, 124
prototypes for, 180
requirements, defining, 146
testing, 108–9
when to perform, 135
installation prototypes, 180
integration and stabilization testing
assessing results of, 112
defining, 111
evaluating, 112
example of, 112
focus of, 110
and milestones, 196
responsibility for, 114
integrity of data, 97
interviews
building a team, 26
closer, 32, 38
common problems, 37
deciding to hire, 32
defining available positions, 37
ending, 29, 37
evaluating candidates during, 23
evaluating candidate’s expertise, 27
evaluating results, 30
example questions, 27
exit, 39
feedback from, 29
follow-up with candidates who decline an offer, 33
giving feedback, 29
hiring decision, 32
key questions, 26, 28
making an offer, 33
moving quickly, 38
questions, 26, 28
resolving schedule conflicts, 26
selling the position to the candidate, 31, 37
testing candidate’s ability, 30
work samples, 31
issue and problem management software, 85
advanced uses of, 90
benefits of using, 88
change rates, 92
fixed failed counts, 92
functions of, 86
managing change with, 88
open rates vs. closure rates, 90
time-based prioritization and, 88
verifying that bugs are fixed, 89
what to include in, 85
iteration
in code, 183
of UI prototypes, 150, 179
J
job candidates. See candidates
job descriptions, 12
job-hopping, 22
K
keeping employees
common problems, 38
effective techniques, 36
identifying problems by using ranking, 65
key feature testing, 108
responsibility for, 50
when to do, 108
key tasks, identifying, 173-76
kick-off meeting, 44
kit, 132
L
labeling files in source code management systems, 77, 96
labs, 120, 128
last known good build (LKGB) directory, 128
lay-offs, hiring candidates from, 18
leads
development, alternating, 161
feature, 50
roles and responsibilities, 45
learning from the past, 252
licensing prototypes, 181
limited resources, distributing, 64
linking development teams together, 48
LKGB directory, 128
load testing, 111
M
Make utility, 127
Nmake, 84, 127
making an offer, 33, 38
management structure, 43
managers. See product managers; project managers
Managing By Walking Around, 211
managing change, 88
manual testing, 118
market trends, 162
marketing betas, 223, 225
marketing, product, 57, 182
master schedules, responsibility for, 47
MBWA, 211
meetings, 209–10
kick-off, 44
postmortem, 252
status, 209–10
merging changed files, 96
metrics of build breaks, 129
Microsoft Visual Source Safe, 80
middle circle, 63
milestones, 195
external, 195
getting back on track after missing, 220
stabilization periods before, 196
working overtime to meet, 216
mission statements, 141
modeling, 167
morale, poor candidate’s effect on, 9
most recent build (MRB) directory, 128
motivational techniques, 44
N
NDAs for beta sites, 229
new employees, how to rank, 63
newsgroups for beta sites, 229
Nmake, 84, 127
non-disclosure agreements for beta sites, 229
notification of build completion/failure, 128
O
online help, 182
online software libraries, 119
OOTB. See Out of the Box experience
open rates vs. closure rates, 90
organization of employees. See ranking
organizational structure. See also ranking
principles of, 44
team creation, 60
Out of the Box experience, 55
quick reference cards and, 181
responsibility for defining, 180
outer circle, 63
when to promote out of, 66
outlines of software requirements, 143
overhead, allowing for, 191
overtime, 19, 216
making enjoyable, 217
showing appreciation for, 218
too much, 217
ownership of resources, 44
P
packaging, 182
paper prototypes, 176
parallel testing, 100
benefits of, 102
scheduling, 189
timetable for, 100
partners as beta testers, 228
parts vs. products, 80
past, learning from, 252
performance. See employee performance
performance analysis tools, 93
performance reviews, 253
performance testing, 111
perks, distributing, 64
phases of beta testing, 224
phone screening, 25
pictures of the team, post release, 251
plans, project, 47
post-mortem meetings, 252
pressure, increasing, 216–17
prioritizing
issues, 88
software requirements, 151
privilege vs. responsibility, 65
problem management software. See issue and problem management software
problems, discussing, 214
procedures. See processes
process capabilities, 80
processes
adding new, 71
evaluating, 71
for managing change, 152
new, 71
as part of corporate culture, 70
QA, 105–6
successful, characteristics of, 71
updating, 253
product management and marketing teams, 57
product managers
partnership with project managers, 45
release candidates, signing off on, 243
product marketing, 57, 182
product readiness, 48
products vs. parts, 80
professional recruiting firms, 16
project closure. See closure
project design, 168
project managers
approachability, 213
communication with teams, 45, 212
decision-making ability, 45
entrepreneurial responsibility, 45
interaction with development teams, 43
leadership of development teams, 48
MBWA, 211
one-on-one time with, 212
ownership of resources, 44
product managers, partnership with, 45
and release candidate testing, 244
responsibility for project plans, 47
roles and responsibilities, 43, 46–47, 219
schedule creation, responsibility for, 47
small stuff, responsibility for solving, 219
project plans, 47
project structure, 80
managing, 95
template for, 82
projects
airplane analogy, 206
breadth vs. depth, 190
changing major elements, 213
completing (see closure)
documenting success/failure, 212
human factors engineers’ roles in, 182
human frailties, dealing with, 220
monitoring progress (see checkpoints)
performance, when to analyze, 169
pressure, increasing, 216–17
problems, discussing, 214
scalability, 59–60
scheduling (see schedules; scheduling)
target dates, 192
unpredictability of, 206
promoting from outer circle to inner circle, 66
prototypes
benefits of, 158, 172
developing, 166, 175–76
documenting, 167
evaluating, 167
existing technology and, 167
external input for, 183
and human factors engineers, 180
importance of, 165
for installation procedures, 180
iteration of, 150, 179
isolated, 169
licensing, 181
modeling, 167
paper, 175
RAD tools, creating with, 178
responsibility for defining, 180
results, evaluating, 167
risks, identifying for, 166
software requirements, defining with, 145
specifications, creating with, 178
stifling innovation with, 184
system-wide, importance of, 169
testing, 178
public recognition at closure, 250
pure research, 159
Q
QA
augmenting with external teams, 214
lack of resources for, 120
plan, developing, 108
processes, 105–6
requirements, defining, 146
scheduling, 188
testing (see testing)
QA engineers
how many to hire, vs. developers, 59, 101
responsibilities, 101
QA leads, 52, 114
QA specialists, roles and responsibilities, 53
QA teams
equipment necessary for, 118
roles and responsibilities, 51, 115–16
separation from development teams, pros and cons, 51
quality assurance. See QA
quality assurance teams. See QA teams
questions, interview, 26, 28
quick reference cards, 181
R
RAD tools, 178
ranking, 62
assigning levels, 62
avoiding favoritism in, 73
fairness in, 73
inappropriate use of, 65
informing employees of, 73
inner circle, 62, 66
middle circle, 63
moving employees between circles, 66, 73
outer circle, 63, 66
reasons to use, 63
typical distribution pattern, 66
Rapid Application Development tools, 178
recognizing employee contributions, 63, 250-51
recruiting, 18. See also finding candidates
recruiting beta sites, 228, 234
recruiting firms, 16
recruiting Web sites, 12
references from customers, 164
referral programs, 15
bonuses, 16
effective, 16
referrals, employee, 15
regression tests, responsibility for, 52
release candidate testing. See also beta testing
automation, 239, 245
benefits of, 113
and beta sites, 240
descent team, 241
designated responsible individual, 244
entrance criteria, 238
final build, 239
leadership, 244
manual, 240
plan for, developing, 113, 245
problems, addressing, 242
sign-off, 243
test plan, 113, 245
release candidates, 196
release engineering, scheduling, 189
release engineers
importance of, 125, 134
roles and responsibilities, 56, 124
release notes, 89
release-to-manufacturing date, 196
releases, research during minor, 160
removing features, 19
requirements. See software requirements
research, 159
benefits of, 158
and development, 160
documenting results, 162
during minor releases, 160
focusing, 162
leads, permanent, 161
pure, 159
resources
balancing with schedules, 187
limited, 19, 64
ownership of, 44
response to change, 9
responsible individuals, designating, 244
responsibility, balancing against privilege, 65
résumés
frequent job changes on, 22
limitations of, 25
reviewing, 22
writing skills on, 24
retaining employees, 34
common problems, 38
effective techniques, 36
identifying problems by usingranking, 65
reviewing résumés, 22
rewards, 251
risks, identifying, 166
roles and responsibilities, 59. See also individual job titles
RTM date, 196
S
salaries, 64
samples of work, 31
scalability of projects, 59–60
schedules
balancing with resources, 187
base levels, 194, 216, 220
for beta testing, 200
breadth vs. depth, 190
building, 193
changing pace, 216
committed dates, 192
convincing team to create, 201
creating, 158
example of, 196
inclusiveness, 188
master, 47
measuring progress (see checkpoints)
meeting, 208, 215
order of, 194
overhead, allowing for, 191
ownership of, 192
and parallel testing, 189
problems, allocating time for, 202
project manager’s responsibility for, 47
realistic, 192
sickness, allowing for, 191
sub-dividing, 201
synchronization periods, 202
target dates, 192
task assignment, 191
working overtime to meet, 216–18
scheduling
development, 188
human factors, 189
QA, 188
UI, importance to, 174
scripting tools, 93
sell message, 31
service packs, 124
sickness, scheduling for, 191
simultaneous editing of files, 77
skill sets, balancing with functional expertise, 59
small stuff, 219
smoke testing, 107, 128
SoftICE, 93
software
configurations, testing, 117
features (see features)
feedback on (see beta testing; release candidate testing)
installation (see installation procedures)
licensing prototypes, 181
presentation, 181
prototypes (see prototypes)
releasing (see release candidate testing)
requirements (see software requirements)
testing (see testing)
usability, 181
software development
and research, 160
scheduling, 188
software development teams
augmenting with external teams, 214
communication between, 55
communication with project managers, 45
external teams, augmenting with, 214
importance of proper staffing, 42
interaction with customers, 69
interaction with project managers, 43
introducing processes to, 71
leadership by project manager, 48
leads (see development leads)
linking together, 48
processes, introducing to, 71
project manager and, 44
QA teams, separation from pros and cons, 51
release candidates, signing off on, 243
schedule ownership, 192
separation from QA teams, pros and cons, 51
staffing, importance of, 42
software engineers, 50
software libraries, 119
software requirements, 140
and grids, 149
backward-looking vs. forward-looking, 148
categories of, 148
change, managing, 153
change review team, 153
creativity in, allowing for, 154
defining, 142, 145
detail, amount necessary, 146
fragmentation, 148
general, 143
general vs. specific, 140
management, 155
outlines for, 143
prioritizing, 151
reviewing, 147
scheduling for, 154
signing off on, 152
specific, 143
user problems, identifying, 142
vision statements, 141
solution software. See issue and problem management software
source code
checking in, 129
freezing, 225
integrity of, 76, 126
iteration in, 183
source code management systems
backing up with, 79
benefits of, 79
conflicts over checked-out files, 96
Environment folder, 83
file version control with, 76
functions of, 76
grouping files in, 77
Import folder, 84
including build environment in, 79
including unit tests in, 78
labeling files in, 77, 96
maintaining/administrating, responsibility for, 56
managing structure during growth, 95
merging changed files, 96
version control with, 76
unit tests in, 78
what to include in, 77, 95
source pool structures/usage, 81
specifications for UI prototypes, 178
stabilization testing. See integration and stabilization testing
staff. See employees
status meetings, 209
length of, 210
topics to discuss, 210
stock options
in compensation packages, 36
as rewards, 251
structuring projects, 80
template for, 82
strung out schedule, avoiding, 174
summary reports. See smoke testing
surveying beta sites, 231
synchronization periods, 202
T
target dates, 192
targeting, 17–18
tasks
assigning, 191
defining, 194
focusing on features, 190
integrating with schedules, 189
scheduling, 187, 194
team
creation, 60
history, as indicator of success, 105
pictures, after release, 251
teams, descent, 241–42
technical leads, 150
technical support, responsibility for, 58
technical support engineers
as developers, 214
release candidate sign-off, 243
roles and responsibilities, 57
technology
anticipating changes in, 149
assumptions about, 158, 164
evaluating, 163–64
prototyping with, 167
understanding, 163
templates
for Environment folder structure, 83
for Imports folder structure, 84
of product structure, 82
test automation tools, 93
test beds, automating, responsibility for, 52–53, 104
test labs, 120, 128
test plans, 52–53
testability, 104
testers. See QA engineers
testimonials from beta sites, 231
testing
as part of culture, 115
assessing results of, 112
automation (see automation testing)
automation test beds, responsibility for writing, 52–53, 104
automation tools, 93
beta (see beta testing; beta sites)
for beta release, 234
builds, 128
by internally using products, 115
check-in, 106
completing, 110
configuration (see configuration testing)
culture and, 115
dependence on UI, 174
developers’ responsibilities during, 101, 115–16
equipment necessary for, 118
example of, 112
features, 50, 108
in parallel (see parallel testing)
installation procedures, 108–9
integration (see integration and stabilization testing)
labs, 120
lack of execution/commitment during, 122
manual, 118
performance/load, 111
plan, developing, 113
preparation for, 121
QA responsibilities during, 116
real-world (see beta testing; release candidate testing)
release candidate (see beta testing; release candidate testing)
responsibility for, 50, 101, 114
smoke, 107, 128
stabilization/integration (see integration and stabilization testing)
touch, 105
UI dependence, 174
UI prototypes, 178
what, when, and how, 106
when to fix bugs during, 112
time, not enough, 19, 64
time off, 254
time-based prioritization, 88
tools, 94
touch testing, 105
tracking bugs. See issue and problem management software
tracking changes to files. See source code management systems
trade shows, 17
training, 253
trends, researching, 162
TrueCoverage, 93
TrueTime, 93
turnover, 39
U
UI
accuracy of, 174
documentation, importance to, 174
external input for, 183
key tasks for, 173, 176
prototypes (see UI prototypes)
review, final (see beta testing; release candidate testing)
scheduling, importance to, 174
specifications, developing prototypes with, 178
testing, 104, 174
UI prototypes, 172
benefits of, 158, 172
developing, 166, 175–76
documenting, 167
evaluating, 167
existing technology and, 167
external input for, 183
and human factors engineers, 180
for installation procedures, 180
iteration of, 150, 179
licensing, 181
modeling, 167
paper, 176
RAD tools, creating with, 178
responsibility for defining, 180
software requirements, defining with, 147
specifications, creating with, 178
stifling innovation with, 184
testing, 178
UI testing, 104
unit tests, including in source code management systems, 78
usability, 181
user education, scheduling, 188
user education leads, 53
user interface. See UI
user problems, identifying, 142
V
values for corporate culture, 68
vendors as beta testers, 228
verifying fixed bugs, 89, 92
version control, 76
virus-checking software on build machines, 128
vision statements, 141
Visual Slick Edit, 96
Visual Source Safe. See Microsoft Visual Source Safe
Visual Test, 94
VSS. See Microsoft Visual Source Safe
W
Web sites
important components of, 14
posting jobs on, 13
finding candidates with, 13
visitors, as beta testers, 228
winging it, 168
work samples, 31
working overtime, 19, 216–18
working with limited time/resources, 19, 64
workplace
extracurricular activities, 36
social environment of, 35
writing effective job descriptions, 12
Last Updated: Friday, July 6, 2001 |
