Index
Note: Page numbers followed by “b”, “f” and “t” refer to boxes, figures and tables respectively
0-9
80-20 specifications,
16–17
A
challenge of breadth,
19–22
challenge of depth,
22–26
Architectural reserve,
64
Automated and continuous integration testing. see Testing
B
Big bang approach,
Big design up-front strategy, ,
13,
305
developers overtime work,
91–92
diagnosing problems with,
97–102
measuring velocity,
92–93
team aggregate progress,
87–92
C
Capabilities Maturity Model (CMM),
311–312
Categorized services model,
235–238
Colocation of team members,
16,
72–73
Command and control approach, ,
311–312
Community demonstration,
67
Compliance, architectural,
63–65
Cross-method comparison projects,
333–334
Cycles, in ADW
Cycles, in waterfall projects
D
Data architect, responsibilities,
262–264
Data topology chart,
316f
Data warehousing/business intelligence (DWBI),
Data warehousing reference architecture,
185–186
Database administrators (DBA),
267–268
Decision support,
Developer stories for data integration,
178–180
defining work units,
183f
in requirements management,
180
Development iteration,
39
Disappointment cycle, waterfall method,
8–12
Done, definition of,
40–41
E
Estimation
causes of inaccurate forecasts,
208–215
criteria for better approach,
213–215
remaining labor estimates,
87–88
Evolving target data model,
297–300
Extract, transform, and load (ETL),
19–20,
84
Extreme Programming (XP),
34
F
Fact-qualifier matrix,
23
“Fail fast and fix quickly” strategy,
17–18,
255
G
H
I
Integrated quality assurance,
18
IT Infrastructure Library (ITIL),
312
Iterative and incremental development,
14–19
J
Just-in-time requirements,
122
K
L
Lightweight modeling,
137
Logical data modeling,
234
M
Minimally marketable feature,
171
N
Net promoter score (NPS),
329
O
Online transaction processing (OLTP),
143
Organizational change management,
313
P
Physical data modeling,
234
resolving task board issues,
280–282
Prime directive, for sprint retrospectives,
68b
Programming, accelerated,
59–62
Project architect, responsibilities,
256–262
Project backlog,
46,
48,
66–67,
73,
81,
101,
117,
123,
126,
130,
143–174,
175,
182,
183,
184,
207,
228,
229,
230,
232,
254,
318,
325,
332,
334
Project manager
Q
Quality of estimates,
330
R
Refactoring databases,
299t
converting Type 1 to Type 2 dimension,
301t
verbs and nouns for,
299t
Release cycle
construction phase,
36–37
discovery and elaboration phase,
36–37
Remote teammates, managing,
106–112
Requirements
Requirements traceability matrix (RTM),
119
Return on investment (ROI),
228–229
S
geographical distribution,
311
Scrum (daily meeting),
57–59
automatic and continuous integration testing,
307–309
developer stories and current estimates,
306–307
managed development data and test-driven development,
307
pull-based collaboration,
309
Segmentation techniques
categorized services model,
243–245
Service level agreement (SLA),
339
Source-to-target mappings,
265
Sprints, nonstandard,
74–77
Story point distribution,
334,
335f
Systems analyst, responsibilities,
264–265
Systems tester, responsibilities,
265–266
T
integrate team efforts,
85–86
Tiered integration model,
235
Time-boxed development,
41–42
U
focus on understanding “who, what, and why,",
134–140
INVEST criteria for quality,
126–127
reverse story components,
134
V
Velocity,
14,
41–42,
50–51,
56,
65,
70,
71,
72,
73,
92–93,
94,
95,
99,
102–103,
104,
110,
184,
196,
205,
217,
222,
225,
230–231,
254,
284,
304,
306,
318–319,
334
W
Warehouse test engines, requirements for,
293–294
“Why isn’t somebody coding yet?!” (WISCY),
120
Work breakdown structure (WBS),
36,
211
Work-in-progress limits,
309