E

editing tools, MSF process templates, 172

effective team communication

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

Einstein (C++ developer), 152

Elvis (C# developer), 152

e-mail

notifications, Team Foundation Build Server, 90–91

team communication, limitations of, 379

<EMPTY /> field rule, 283

encryption key, backup, 131–133

engineering software, 148

English (United States) language support, 417

Enough Design Up Front (ENUF), 151

enterprise deployment, Team Foundation Server, 10–11

enterprise IT administrator, 32

enterprise project management (EPM), 351, 375

errors

human, 371

New Team Project Wizard

network errors, 192–193

permission, 191–192

Essential Unified Process, 169

estimation of work, 362, 363

eventing service

test automation, 373

TFCS, 229–230, 240–242

events, subscribing to, 231–232, 241–242

ever operator, 298

Excel (Microsoft)

administration, 293–294

checklist of software, hardware, and necessary tasks, 8

Choose Team Project button, 352

as client component, 6

connecting to Team Foundation Server, 13

team portal, integrating, 257

Team Project areas and iterations, modifying, 196

work item

summaries, viewing with pivot tables, 364–367

tracking system, 275, 293–294

extensibility

custom check-in policies, 337–340

customization versus, 227–228

described, 336–337

MSSCCI provider, 341–343

object model, 341

test automation, 373

TFVC, Visual Studio 2005 Software Development Kit, 24

Extreme Programming Explained (Beck), 84, 150–151

Extreme Programming (XP), 149