Index

A

acceptance test-driven development

coach 56

compared to test-driven development 47

definition 42

for requirements 271

for UAT 463

in iteration 48

is not testing 47

offshore 462

overview 44

recommended reading 96

adapters 327

adoption

agile curriculum 401

avoid cookbooks 401

large-group introductions 397

Open Space 398

overview 373

project 380

targets 385

Adzic, Gojko 49

agile modeling 268, 292, 303

in design workshops 289

ambassador

activities in coordination 194

multisite 432

offshore 455

analysis

see requirements

analysis group 234

Ancona, Deborah 193

andon 359

appraisals

CMMI 480

appraisers

CMMI 494

Arbogast, Tom 499

architect

active master programmers 288, 302

astronauts 302

avoid handing off to programmers 308

avoid separate review of work 312

coaches during design workshops 299

impact if not programming 286

PowerPoint 285, 302

program spikes 308

programmer in tiger team 308

teaches during code reviews 312

architecture

analysis 301

and customer-centric features 307

build vertical slices 305

Community of Practice 313

design 301

documentation 310

see SAD workshops

group 234

integrity 293

outdated 302

question finality 301

see also design

spikes 308

versus growing, gardening 282

Area Backlog 15, 133, 215, 221, 555

Area Product Owner 15, 133, 135, 136, 215, 423, 555

artifacts

see documentation

A-TDD

see acceptance test-driven development

attrition 468, 469

B

backlog grooming

see Product Backlog refinement

best practices 4, 492

branching 358

browser wars 334

bug-free code 39

build speed 361

business advantages 100

business analyst

not the Product Owner 124

business manager

as Product Owner 121

business rules 52

C

C++ unit testing 73

career paths 342

cargo cult 2

Carmel, Erran 413

certifications

agile 493

CMMI 480

change management

contracts 521

change project 380

changes

large ones 369

chief engineer 128, 191

chief Product Owner 135

clean up your neighborhood 346

ClearCase

avoid 362, 441

CMMI

appraisers 494

overview 480

coaches

avoid coaches who aren’t hands-on 400

external 399

external and internal 400

offshore 469

coaching

internal group 399

code

HTLM-ize it 317

is the design 282

multisite 438

reviews 312

coffee 86

Cohn, Mike 195

collaboration 116

co-located team 413

commitments 190, 335

committer role 314

communicate in code 211

communication barriers 209

Communities of Practice

design/architecture 313

for communication 208

general 207

multisite 433

Community of Practice

testing 35

competition between teams 198

component guardians 314

component teams

drawbacks 553

to feature teams 391

Concordion 57

continuous integration

developer practice 352

how frequently? 356

misconceptions 351

multisite 424

overview 351

continuous integration system

multi-stage 364

overview 65, 359

scaling 361

scaling example 366

continuous product development 157

contract game 106

contract negotiation 106

contracts

acceptance 522

agile 518

appreciate lawyer point of view 502

change management 521

collaborate with lawyers 516

collaboration 116

common misunderstandings 504

contract game 106

deliverables 525

delivery 519

fixed price 527

fixed-price fixed-scope 531

hybrid pricing 530

incentives, rewards, penalties 514

internal 190

key agile insights 500

lawyer education 501, 509, 511, 513

liability 524

multi-phase models 539

multi-phase variable-model 543

offshore 494

overview 499

payment timing 526

pay-per-use pricing 529

progressive 536

release contract 106

scope 519

silo mentality 505

target-cost 520, 540

termination 522

thinking about 500

time and materials 527

traditional assumptions 504

value-based pricing 528

variable-price variable-scope 536

warranty 525

cookbooks 401

coordination

centralized 200

cross-department 190

decentralized 206

meetings 200

responsibility for 196

ScrumMaster’s responsibilities 197

team is responsible for 194

thinking about 189

travelers 207

coordinator 190

coordinator, ambassador, and scout 193

copy-paste 336

CppUTest 73

craftsmanship 337, 339

cross-department coordinator 190

cross-functional teams 191

cubicles 209

Cucumber 57

culture

multisite 437

overview 468

Cunningham, Ward 57

customer documentation 192

customer-facing test 42

customers 145

D

Daily Scrum 14, 124

defect tracking 39

defects

(to fix) in Product Backlog 225

zero tolerance 39

Definition of Done 15, 170, 178

demo preparation 59

department interfaces 190

dependency injection 318, 319, 320

design

multisite 435

overview 281

see also architecture

sending offshore 316

thinking about 282

walking skeleton 305

design patterns 316

design workshops

at the start 296

each iteration 295

in team room 297

joint for multiple teams 298

overview 289

developer testing 72

development skills 335, 339

discuss-develop-deliver cycle 44

dispersed team 413, 416, 419, 420, 472

distributed teams 413, 416

documentation

architectural 310

offshore 461, 462

requirements

done

see Definition of Done

dual targeting 76

duplication

between requirements and tests 56

between tests 66

code 82

E

education

for all teams 401

embedded software

learning tests for new hardware 80

testing 77

environment mapping 211

epic

see splitting

terminology 222

estimation

Monte Carlo simulation 184

multisite 429

overview 181

value 139

examples for requirements 50, 245

experiments 2

exploratory testing 62

external coordinator 195

Extreme Programming

see XP

F

false dichotomies 2

Feathers, Michael 73

feature 222

feature screening 216

feature teams

as automation team 38

choosing 554

dispersed 420

from component teams 391

in large-scale Scrum 12

multisite 418

overview 549

transition 555

vs component teams 551

vs project groups 552

Fit 57

FitNesse 57

fixed-price contracts

see contracts

flexibility and specialization 551

Fowler, Martin 351

FPGA 322

function-to-function-pointer refactoring 78

FURPS+ 231

G

Git 358

Grenning, James 97

grooming

see Product Backlog refinement

growing vs building 355

H

Hackman, Richard 198

hardware 317

hardware abstraction layer 320, 321

hardware design 322

hardware simulators 71

Hetzel, Bill 29

Hohmann, Luke 152

I

impediments

backlog 381

service 381

improvement 373

incentives 514

incremental handoff 179

infrastructure work 128, 168

inspect-adapt

overview 373

product management 148

interaction design

see UI design

interaction design group 234

interface API design 323, 324, 326

INVEST test 247

ISTQB 32

iteration planning

see Sprint Planning

J

jidoka 353

JIT modeling 295

joint design workshop 298

joint requirement workshops 246

joint Scrum meetings 205

joint Sprint Retrospective 15, 17, 403

joint Sprint Review 17, 405

K

Klärck, Pekka 57

L

lake and rocks metaphor 407

language 456

large-scale Scrum

artifacts 13

definition 9

framework-1 10

framework-2 15

overview 9, 10

roles 12

law of communication paths 199

law of the inverse relationship between size and

skill 339

lead Product Owner

overall 135

learning debt 336

learning tests 79

Lecht, Charles 334

legacy code

awareness 342

lethal 347

overview 333

solution 343

line manager 393

M

maintainable tests 65

Marick, Brian 27

Martin, Bob 57

matrix organization 31

MDA 291

MDD 291

meetings

multisite 428, 431, 435

Meszaros, Gerard 36

milestone 108

mocks 318, 321

modeling

agile 292

avoid extremists 303

just-in-time 295

requirements

tools 291

Monte Carlo simulation 184

moving skeletons 368

multisite

ambassador 432

avoid ClearCase 441

centrifugal forces 413

coding style 438

Communities of Practice 433

continuous integration 424

culture 437

design 435

dispersed vs. distributed 416

estimation 429

feature team 418

is non-trivial 415

matchmakers 435

meetings 425, 431, 435

one iteration per product, not site 417

Open Space 430

overview 413

partner sites 423

planning poker 429

Scrum of Scrums 430

shared space 209

site organization 417

teams 420

thinking about 414

tools 438, 439

transition to feature teams 421

video culture 425, 428

visits 432

myriad coordination methods 199

N

Netscape 334

non-functional requirements

in Product Backlog 225

see FURPS+

O

offshore

acceptance TDD 462

ambassador 455

certification 480

CMMI 480

CMMI appraisers 494

coaches 469

contracts 494

culture 468

design problems 316

documentation 461, 462

domain and vision workshop 460

educate customers 446

educate Sales 448

feature teams 470

kickoff workshop 448

language 456

matchmakers 450

onshore partnership 469

onshore Product Owner 457

overview 445

partnership 470

planning 470

remove barriers 450

requirements 462, 465

requirements workshop 458

ScrumMaster 468

Sprint Retrospective 456

Sprint Review 454

team visits onshore 457

teams 466

titles 467

tools 495

translator on team 455

UAT 463, 464

UI design 461

video sessions 451

visits both ways 454

Open Space

for agile adoption 398

multisite 430

overview 204

outsourcer

avoid factories and factory mindset 478

choose good programmers 479

choosing 475

four-year programmers 477

improve together 480

poor environment 477

top-heavy management 476

outsourcing

and legacy code 341

choosing a partner 475

overview 445

overall product focus 193, 198

overall Product Owner 135

overburden 337

P

PBI 215

PDMA 152

penalties 514

personal safety 376

Pichler, Roman 152

planning

infrastructure 168

iteration 163

overview 155

research and learning 166

Sprint 163

planning poker

multisite 429

platform departments 191

platform development 128, 168

Poppendieck, Mary 4

potentially shippable 26

potentially shippable product increment 14, 170

PowerPoint architects 302

practices

context dependent 4

pricing

contracts and outsourcing 527

prioritization

avoid categories 143

of Product Backlog 139

of value 139, 141

Product Backlog

Area Backlog 215

avoid tasks 237

avoid team-level backlogs 238

creation 155

items 215

major improvement goals 404

one per product 132

only one per product 13

PBI 215

prioritization 139, 141

refinement 166

themes 216

visual management 229

Product Backlog refinement

for A-TDD 49

initial 155, 158

joint or asynchronous 166

overview 15

workshop 243

product management

avoid short-term focus 123

changes when adopting Scrum 104

collaboration with R&D 116

contract negotiation 106

inspect-adapt 148

overview 99

traditional assumptions 117

product manager 120, 126, 128

Product Owner 120, 122, 135

Area 15, 133, 135, 136, 215

avoid too inward 124

chief 135

fake 123

has business authority 121

help from Team 147

interaction with other POs 131

lead 135

looks outward 124

not just an analyst 124

offshore development 457

overall 135

overview 12, 120

PO Team 17, 136, 137, 236

proxy 135

representative 135, 138

supporting PO 134, 135

us-them versus Team 125

Product Owner representative 135, 138

Product Owner Team 17, 136, 137, 236

profit 141

program manager 190

project managers 196, 393

projects

prefer product view 127, 157

prototypes 304

proxies 327

proxy Product Owner 135

punching holes 210

R

refactoring

large ones 369

Reinertsen, Donald 4

relative value points 139

release contract 106

release planning 155, 158

Release Sprint 175, 177

release train 180

requirement areas 133, 215

for non-functionals 70

overview 555

vs development areas 556

requirements

acceptance TDD 271

artifacts 229

by example 245

clarifying by writing tests 49

customer-centric 236

meta-models 232, 233

multiple descriptions 56

non-functional 225

offshore 462

offshore to onshore 465

offshore workshop 458

overview 215

splitting 217, 247

tables 245

tool 462

requirements workshop

A-TDD workshop agenda 54

for Product Backlog refinement 243

overview 240

so-called optimizing 51

research

fake 228

in Product Backlog 227

planning it 166

rewards 385, 514

risk 141

Robot Framework

architecture 87

calling C code 90

example using 83

introduction 57

test library 86

types of tables 86

room

see team room

rubber chicken 354

S

SAD workshop 310

safety (personal) 376

SAGE 338

salary 342

scenario 249

Schwaber, Ken 9

Scientific Management, critique 4

scout activities 194

Scrum

see large-scale Scrum

Scrum 2.0 9

Scrum of Scrums

alternatives

Open Space 204

Town Hall 205

format 201

multisite 430

overview 200

rotate representatives 203

rotate representatives too frequently 203

ScrumMaster’s role 203

status to management 202

two parts 202

ScrumMaster

avoid representing team 434

in large-scale Scrum 13

not project manager 393

offshore 468

slow rotation 408

Second Life 209

secret toolbox 336

shared space 208

simulation layers 321

Slim 57

small changes 355

specialization 550

spikes 308

splitting requirements 217, 247

splitting user stories

see splitting requirements

Sprint Backlog 13

Sprint Planning 163

in large-scale Scrum 14, 17

multisite issues 165

part one 163

part two 166

Sprint Retrospective

in large-scale Scrum 15

joint 17, 403, 433

multisite 433

offshore 456

Sprint Review

bazaar 206

in large-scale Scrum 15, 17

joint 17, 405

multisite 454

offshore 454

show tests 59

team level 406

stakeholders 141

stop and fix 38

stories

see user stories

story points 181

strategic alignment 141

stubs 318, 321

supporting Product Owner 134, 135

T

tables for requirements 245

target-cost contracts 520

targets 385

task-coordinator activities 194

tasks

in Product Backlog 237

Taylor, Frederick 4

TDD

see test-driven development

Team (in Scrum) 12

team room 297, 394

team size 192

teams

cross-functional 234

technical debt 336

technical writing 34

test 23

test automation team 37

test department 30

test education 34

test independence 29

test sessions 64

test smells 36

test tools

commercial 40

conventional 57

wrap conventional tools 58

test-driven development

better architecture 319

coach 74

internal 75

overview 74

tester certification 32

testing

and Product Owner 51

assumptions 24, 26

before release 42

classifications 27

customer-facing 28, 42

developer 28, 72

in Sprint Planning 41

in Sprint Review 42

keyword-driven 83

legacy code 346

manual 60, 61

meaning of 24

on the hardware 317

overview 40

skills 96

specialization 33

terminology 26

thinking about 24

through the UI 67

traditional 46

UAT 463, 464

using walls 52

testing community 35

tests

automated 60

deleting 66

distill 55

expensive 71

long-running 70

non-automatable 62

non-functional 69

on development environment 76

on real hardware 77

performance 70

refactoring 81

reliability 70

table format 53

user-acceptance 59

workflow 54

testware 37

themes 216

tiger team 308

TMM 32

tools

agile management 389

for modeling 291

for requirements 273

multisite 438, 439

offshore 495

requirements offshore 462

testing 40, 56, 57

Town Hall meeting 205

TPI 32

traceability 67, 68, 229

tracer code 305

transformation project 380

transition

component teams to feature teams 391

overview 373

to feature teams 421

travelers 207

trivializing programming 341

TTCN 57

U

UAT 463

pre-UAT 464

with A-TDD 463

UI design

importance of 300

offshore 461

UML 291, 295

Undone Unit 31, 177

Undone Work 173, 177, 179, 225, 226

unit testing

overview 72

rules for 73

unit tests

slow 83

use case 249

user stories

formats 271

history 223, 271

overview 266

question their use

splitting

term 222

user-acceptance test 59

see UAT

V

value 139, 141

velocity 184

video sessions 451

video technology 425

virtual shared space 209

virtualization of hardware 71

visual management 229, 367

W

walking skeleton 305

weakly-typed interfaces 324

whiteboards 290

wikis 275, 440, 462

wishful thinking 337

workflow test 54

working agreements

cross-team 405

for coordination 212

workshops

design 289, 295, 296, 297

initial Product Backlog refinement 158

joint 246

joint design 298

multisite 428

requirements 54, 240, 243

SAD 310

X

XP 303

xUnit 76

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.188.8.91