Professional Team Foundation Server
CAL (client access license), 413
<CANNOTLOSEVALUE /> field rule, 282
Capability Maturity Model Integration (CMMI) certification, 148
Capability Maturity Model Integration process improvement. See CMMI process improvement
capacity planning
enterprise deployment, 10–11
performance and scope, 9–10
scenarios, 9
small-to-medium deployments, 10
Carnegie Mellon SEI (Software Engineering Institute), 148
_catalogs folder, 266
CCVs (common cause variations), 158
centralized information, communication and, 380
Chambers, Davis S. (Understanding Statistical Process Control), 164
change request, 277
chaos, CMMI process improvement, 163
Check phase, quality management, 161
check-in/check-out
best practices, 335
custom policies, 337–340
TFVC, 309–312
Chinese (People's Republic of China) language support, 417
Choose Team Project button, 352
CI (continuous integration), 84–85
classification
Conchango Scrum Process Template, 173
folders, ProcessTemplate.xml, 171
TFCS service, 229
ClearQuest workflow, 24
client
build server, installing, 93
Team Explorer, 13–14
Team Foundation Server components, 5–6
Team Foundation Server editions, 13
Team Foundation Server Proxy, 401–403
Team System, illustrated, 4
client access license (CAL), 413
CMMI (Capability Maturity Model Integration) certification, 148
CMMI (Capability Maturity Model Integration) process improvement
failure rate of software projects, 155–156
Level 3 process maturity, 157–161
progress, tracking
brink of chaos, 163
bug rates, 166
chaos, 163
cumulative flow diagram, 164
ideal state, 162
quality indicators, 166–167
remaining work report, 164–165
threshold state, 163
triage report, 165–166
unplanned work, 167–168
velocity chart, 165
Wheeler's diagram, 163–164
Project Retrospective, 448
release management activities, 444–446
risk and issues, managing, 168–169
work item types, 277
Codd, Dr. Edgar F. (relational database model inventor), 421–422
code
analysis, 372
check-in integration, 373
source, documenting, 7
CodePlex, 65
Microsoft community site, 395
Team Foundation Administration Tool under development, 65
Cognizant Feature Driven Development process, 169
collection
of fields, 280
of work flow states and transitions, 280
command line
groups
adding users to, 64, 110
creating new with, 106–107
security permissions, setting, 112–113
Team Explorer tools, 63–65
test automation, 373–375
common build drop site, 91–92
common cause variations (CCVs), 158
communication, team
challenges, 377–378
disadvantages of current methods
described, 378–379
e-mail, 379
file shares, 379–380
telephone, 379
Team Foundation Server
flow, improving, 382–384
instant messaging, receiving tasks via, 384–389
Microsoft Groove 2007, 392
multiple platforms, 381–382
status, tracking via Outlook, 389–392
tools, 380–381
Community Technology Preview (CTP) 3, 199
company governance documents, 9
completed work, 362
Completed Work field, 363–364
completing software projects
documenting improvements and best practices, 450–451
finalizing projects in Team System
postmortems, 448–450
project artifacts, exporting and saving, 448
new project, setting up
assets, migrating other, 459
new team project, 456–457
version control migration, 457–458
workflow, 458
release management
within MSF, 443–446
tasks in Team System, 446–447
removing project from server
deleting team project, 451–453
TfsDeleteProject Commands, 453–454
uninstalling Team System, 454–456
ComponentWare's Converter, 22
Conchango Scrum Process Template
classification, 173
described, 172
downloading, 169
groups and permissions, 173–175
process templates, 172–179
connecting Team Explorer to Team Foundation Server, 60
connection strings, 142–143
constraints, 158
continuous integration, 74, 414
continuous integration (CI), 84–85
copy-modify-merge model, 310
cost overruns, 148
CPU requirements
Team Foundation Build, 16
Team Foundation Server, 15
Visual Studio 2005, 16
crash protection
data tier, SQLServer 2005, 126–131
disaster recovery
built-in Windows tools, 123
ease of use, 123
importance, 121–122
plan, 122
SQL Server 2005 Backup and Restore, 123–124
third-party tools, 123
Team Foundation Server
databases, 125–131
encryption key, 131–133
credit card numbers
generating, 219–224
stored procedures, retrieving, 206–207
table, renaming, 210–212
Crosby, Philip (Quality is Free and Quality Without Tears), 156
Crystal Reports, 26
CS-Converter with Visual SourceSafe, 333–334
CTP (Community Technology Preview), 199
culture, Team Foundation Server, 234
cumulative flow diagram, CMMI process improvement, 164
custom check-in policies, extensibility, 337–340
custom development tools
extensibility versus customization, 227–228
TFCS
classification service, 229
described, 6, 228–229
eventing service, 229–230, 240–242
linking service, 229, 230–231, 244–246
registration service, 229, 231
security service, 229, 231, 243–244
subscribing to an event, 231–232
TFSOM
described, 232–233
IAuthorizationService, 236–238
ICommonStructureService, 238–240
IGroupSecurityService, 243–244
ILinking, 244–246
IProcessTemplates, 246–247
IRegistration, 247–250
IServerStatusService, 250–251
services, accessing, 235–236
TeamFoundationServer object, 233–235
VersionControlServer, 251–252
WorkItemStore, 252–254
custom reports
Team System, 429–431
VSTS, 428
customer
members, working with, 350
scope change, 167
CVS system, 302