Index

Numerics

1. 3-3-5 framework, 13
2. 3M, 260
3. 5-6-7 framework, 14
4. 7Shifts, 147
5. 360-degree performance reviews, 255–256

A

1. abandonment rate, as a metric, 280
2. absolute estimating, 73
3. AC (actual cost), 85, 224, 356
4. academic education, 311
5. acceptance criteria, as a target outcome of product backlog refinement, 56
6. accountability
   1. displaced, 223
   2. in family life, 299
   3. team members and, 252
7. A-CSD (Advanced Certified Scrum Developer), 362
8. A-CSM (Advanced Certified Scrum Master), 361
9. A-CSPO (Advanced Certified Scrum Product Owner), 362
10. actual cost (AC), 85, 224, 356
11. adaptability
    1. in construction, 158
    2. increased, as a benefit of using agile framework, 266
12. adaptation
    1. about, 124
    2. customer service and, 280–281, 284–285
    3. for families, 304–305
    4. importance of, 334–335
    5. as a pillar of improvement, 17
    6. in publishing industry, 190–192
    7. as you release, 142
13. Advanced Certified Scrum Developer (A-CSD), 362
14. Advanced Certified Scrum Master (A-CSM), 361
15. Advanced Certified Scrum Product Owner (A-CSPO), 362
16. affinity estimating, 77–78
17. Agile
    1. Agile Manifesto, 17–18, 165, 284
    2. audits by Platinum Edge, 364
    3. double-work, 351
    4. pillars of improvement, 16–17
    5. principles, 18–20, 267
    6. principles in marketing, 267
    7. roots of, 16
18. Agile Advantage surveys, 266–267
19. Agile Alliance, 362
20. Agile Manifesto, 17–18, 165, 284
21. Agile Marketing Manifesto, 267
22. “Agile programming — for your family” TED talk, 304
23. agile project, 2
24. “Agile Project Development at Intel: A Scrum Odyssey” case study, 166
25. Agile Project Management For Dummies, 2nd Edition (Layton and Ostermiller), 16, 138, 192
26. agile release train (ART) model, 239
27. Agile School, 306
28. Agile Team Retrospectives: Making Good Teams Great (Derby and Larsen), 122, 335
29. AICPA (American Institute of Certified Public Accountants), 261
30. allocating people, 220
31. Amazon, 141, 153
32. American Institute of Certified Public Accountants (AICPA), 261
33. analysis paralysis, 129
34. Anthem healthcare, 209
35. antipatterns, 129–130
36. Apple, 153
37. applications
    1. publishing, 191–192
    2. software, 147–153
38. applying scrum in publishing industry, 192–193
39. approval, as a step for building requirements, 52
40. architecture
    1. emergent, 146–147
    2. owner of, 232
41. art, in video-game development, 151
42. ART (agile release train) model, 239
43. artifacts, 13
44. Atos Origin, 20
45. AT&T Wireless, 258
46. audits, conducting, 327–328
47. automated testing, 338–339
48. automobiles, 164
49. autonomy, in Saab Jet Fighter, 169
50. average handle time, as a metric, 280
51. average speed of answer, as a metric, 280

B

1. behavior tests, 296
2. “being in the zone,” 41
3. benefits
   1. in implementation strategy, 328
   2. of scrum, 343–350
4. bids, in construction, 157–158
5. Big Data, 202–208
6. Bigollo, Leonardo Pisano (Fibonacci) (mathematician), 74
7. Blanchard, Kenneth (author)
   1. The New One Minute Manager, 38
8. Blueprint High School, 186
9. body language, 285
10. Boesch, Jordan (app developer), 147
11. bots, 209
12. bring in outside applications (BYOA), 208
13. bring your own device (BYOD), 208
14. budgets, 261–262, 317
15. Build, Measure, and Learn pattern, 227
16. building retirement, 309
17. Bunch, John (transition leader), 254
18. burndown chart, 100–101
19. burnup chart, 94
20. business alignment, with technology, 143–145
21. business development
    1. about, 263
    2. marketing, 264–269
    3. sales, 269–275
22. Business Development For Dummies (Kennedy), 264
23. business performance, increased, as a benefit of using agile framework, 266
24. BYOA (bring in outside applications), 208
25. BYOD (bring your own device), 208

C

1. CafePress, 268
2. CAL (Certified Agile Leadership), 362
3. Canon, 155
4. capacity, backlog, 101–102
5. capital redeployment, 355–356
6. Carpentier, Andrée (app developer), 147
7. CEC (Certified Enterprise Coach), 362
8. CEC (Certified Scrum Coach), 329, 336
9. certainty, need for, 125–126
10. Certified Agile Leadership (CAL), 362
11. Certified Enterprise Coach (CEC), 362
12. Certified Scrum Coach (CEC/CTC), 329, 336
13. Certified Scrum Developer (CSD), 328–329, 362, 365
14. Certified Scrum Master (CSM), 328–329, 361, 365
15. Certified Scrum Product Owner (CSPO), 328–329, 362, 365
16. Certified Scrum Professional (CSP), 362
17. Certified Scrum Professional (CSP-SM, CSP-PO), 329, 336
18. Certified Scrum Trainer (CST), 336
19. Certified Team Coach (CTC), 362
20. CFDs (cumulative flow diagrams), 94
21. challenges
    1. for development team, 143
    2. in education, 180–182
    3. family life, 299
    4. identifying, 336
    5. with IT security, 209
    6. in portfolio management, 220–225
    7. service-versus-control, 209
22. change, embracing, 142–147
23. Cheat Sheet (website), 365
24. Chicago Tribune (newspaper), 194, 195
25. chief product owner (CPO), 234
26. chores, 305–306
27. Christensen, Clayton (scholar), 194
28. CI (continuous integration), 239–240
29. Cirillo, Francesco (Pomodoro technique developer), 42
30. Cisco, 202
31. clarity
    1. of pilot projects, 331
    2. as a target outcome of product backlog refinement, 56
32. classrooms, 183–186
33. close, in sales pipeline/funnel, 272
34. clout, as a scrum master trait, 38
35. CMG Partners, 266–267
36. Cockburn, Alistair (Agile Manifesto signatory), 284, 285
37. code
    1. quality of, 240
    2. refactoring, 140–141
38. cognitive consistency theory, 69
39. collaboration, increased, with scrum, 347
40. collaboration time, 41
41. collective intelligence, using for vision statement, 37
42. college, 323–324
43. co-location, 69–70, 332
44. Comcast, 278
45. commitment, as a Scrum value, 23
46. communication
    1. as a dating challenge, 290
    2. in family life, 299
    3. quality of, 285
    4. for relationships, 296
    5. with scrum, 303–304
47. companies
    1. culture of, 31–32
    2. goal, 35–37
    3. strategy, 35–37
    4. turnover for, 357
48. companionship, 293–294
49. compensation, 250–251
50. comprehensive testing, as a step for building requirements, 52
51. concentration time, 41
52. conducting
    1. audits, 327–328
    2. daily scrum, 110–111
53. Cone of Uncertainty, 126
54. construction
    1. about, 157
    2. bids, 157–158
    3. customer involvement, 159–160
    4. roles in, 158–159
    5. subcontractors, 160–161
    6. worker safety, 161–163
55. containability, of pilot projects, 331
56. continued learning, 336
57. continuous improvement, 169
58. continuous integration (CI), 239–240
59. contributor personality, 249
60. conversion, in sales pipeline/funnel, 272
61. converting legacy systems, 207
62. coordination of priorities, as a cost-cutting aid in healthcare, 176
63. cost cutting
    1. in healthcare, 176–177
    2. of losing customers, 279
    3. in video-game development, 148
64. costs
    1. reducing with incremental funding, 259
    2. sunk, 145
65. courage, as a Scrum value, 24
66. CPO (chief product owner), 234
67. creating
    1. code quality, 240
    2. cross-functionality, 66–67
    3. culture, 249–257
    4. motivating environments, 65
    5. product backlog, 312
    6. product roadmap, 48–49, 312
68. creativity
    1. culture of, 260
    2. motivating, 133
69. CRM (customer relationship management) tool, 204
70. cross-functionality, 65–67, 210
71. Crossing the Chasm (Moore), 36
72. cross-team coordination, in Large-Scale Scrum (LeSS), 243
73. CSD (Certified Scrum Developer), 328–329, 362, 365
74. CSDP for Scrum Masters (CSP-SM), 362
75. CSM (Certified Scrum Master), 328–329, 361, 365
76. CSP (Certified Scrum Professional), 362
77. CSP for Developers (CSP-D), 362
78. CSP for Product Owners (CSP-PO), 362
79. CSP-D (CSP for Developers), 362
80. CSPO (Certified Scrum Product Owner), 328–329, 362, 365
81. CSP-PO (CSP for Product Owners), 362
82. CSP-SM (CSDP for Scrum Masters), 362
83. CSP-SM, CSP-PO (Certified Scrum Professional), 329, 336
84. CST (Certified Scrum Trainer), 336
85. CTC (Certified Team Coach), 329, 336, 362
86. CubeSat (Johns Hopkins), 168
87. culture
    1. company, 31–32
    2. creating, 249–257
    3. of creativity, 260
    4. of innovation, 132–133, 168
88. cumulative flow diagrams (CFDs), 94
89. current processes, in implementation strategy, 328
90. curriculum scope, 181–182
91. customer feedback, in Wikispeed modular car, 168
92. customer relationship management (CRM) tool, 204
93. customer satisfaction
    1. as a metric, 280
    2. with scrum, 345
94. customer service
    1. about, 277–278
    2. customers, 278–280
    3. definition of done, 282–283
    4. information sharing, 283–284
    5. metrics for, 280
    6. product backlog and, 281–282
    7. scrum and, 280–286
95. customers
    1. about, 278
    2. cost of losing, 279
    3. information overload, 279–280
    4. involving, 159–160
    5. service and, 278–279
96. customizing
    1. projects, 152
    2. release sizes, 141–142
97. cyberattacks, 188
98. cycle time, 216

D

1. daily scrum
   1. about, 108
   2. conducting, 110–111
   3. customer service and, 281
   4. defining, 108–109
   5. in families, 302–303
   6. in kanban, 217
   7. in Large-Scale Scrum (LeSS), 243
   8. making more effective, 111–112
   9. performance issues and, 252
   10. risk and, 350
   11. scheduling, 110
   12. team coordination of, in construction, 158
2. data
   1. Big, 202–208
   2. sizes of, 203
3. data warehouses, 203–205
4. dating
   1. about, 289–290
   2. definition of done, 293
   3. finding relationships with scrum, 290–299
   4. focusing vs. multitasking, 296–297
   5. with scrum, 294–295
   6. setting visions, 291–292
   7. stages in, 292–293
   8. teamwork, 295–296
5. De Bono, Edward (psychologist and philosopher), 132
6. debt, retirement and, 312
7. decisions, timing of, 127
8. decisiveness, as a product owner characteristic, 34
9. dedicated development teams, 65–67
10. defect rates, 353
11. defects, metrics for, 352–353
12. definition of done
    1. about, 71–73
    2. customer service and, 282–283
    3. for dating, 293
    4. defining for news media content, 195–196
    5. establishing, 333
    6. retirement and, 309
13. delaying delivery, 225
14. delivery, delaying, 225
15. denominator, 63
16. dependencies, 222
17. Derby, Esther (author)
    1. Agile Team Retrospectives: Making Good Teams Great, 122, 335
18. design, as a step for building requirements, 52
19. determining sprint lengths, 313
20. developed, as a factor in “done” definition, 72
21. developers, hiring, 252–253
22. developing
    1. defects during, 353
    2. hardware, 167–169
    3. software. See software development
23. development and operations (DevOps), 212–213
24. development teams. See also teams
    1. about, 64
    2. backlog estimation and, 70–71
    3. challenges for, 143
    4. co-locating, 69–70
    5. in construction, 159
    6. creating motivating environments, 65
    7. cross-functionality, 65–67
    8. dedicated, 65–67
    9. for news media, 197
    10. pair programming, 67
    11. scrum of scrums model, 231
    12. as a scrum role, 12
    13. self-managing, 68–69
    14. self-organizing, 68–69
    15. in sprint review process, 118
    16. stages of, 71
    17. as a step for building requirements, 52
    18. uniqueness of, 64
    19. why they love scrum, 70
    20. work-in-progress limits for, 224
25. DevOps (development and operations), 212–213
26. discipline, laxity of, 340
27. disconnecting, between projects and business objectives, 222–223
28. displaced accountability, 223
29. disruptive innovation, 194
30. documentation
    1. as a factor in “done” definition, 72
    2. as a step for building requirements, 52
31. double-work agile, 351
32. Download Here button, 141
33. Drive: The Surprising Truth About What Motivates Us (Pink), 65
34. Dropbox, 227
35. Dummies (website), 365

E

1. early learning, 319–320
2. eBay, 202
3. education
   1. about, 180
   2. challenges in, 180–182
   3. classrooms, 183–186
4. eduScrum, 185–186
5. effectiveness, of daily scrums, 111–112
6. efficiency, of environments, 332
7. Einstein, Albert (physicist), 319
8. Eliot, T.S. (poet), 191–192
9. Elwer, Pat (engineer), 166
10. embracing change, 142–147
11. emergency fund, 308–309
12. emergent architecture, 146–147
13. emotional intelligence (EQ), 297
14. employee satisfaction, increased, as a benefit of using agile framework, 266
15. employing transparency in projects, 128
16. energy efficiency, 211–212
17. engineering, up-front, 145–146
18. ensuring training, 329
19. enterprise architect, as a portfolio-level role, 238
20. enterprise resource planning (ERP), 205–208
21. environments
    1. inappropriate, 339
    2. maximizing efficiency of, 332
    3. motivating, 65
22. epic owners, as a portfolio-level role, 238
23. epics, 53
24. EQ (emotional intelligence), 297
25. Equifax, 209
26. ERP (enterprise resource planning), 205–208
27. establishing definition of done, 333
28. Estimable, as a user story quality, 62
29. estimating
    1. absolute, 73
    2. affinity, 77–78
    3. common practices for, 73–81
    4. relative, 73–74
30. estimation poker, 75–76
31. example approach, 184–185
32. exposure, of progress with scrum, 348–349
33. external forces, 130
34. external interruptions, 41
35. eXtreme Programming (XP), 62

F

1. Facebook, 141, 202, 260
2. face-to-face interaction, 285, 303–304
3. families
   1. adapting for, 304–305
   2. chores, 305–306
   3. communicating with scrum, 303–304
   4. inspecting for, 304–305
   5. task board, 306
4. family life
   1. about, 289–290
   2. challenges in, 299
   3. families, 299–306
   4. finding relationships with scrum, 290–299
   5. focusing vs. multitasking, 296–297
   6. setting family strategy, 300
   7. setting project visions, 300
   8. setting visions, 291–292
5. faux scrum, 337–338
6. FBI, 188
7. features, 53
8. feedback
   1. about, 15
   2. access to, 265
   3. adapting through, 280–281
   4. inspecting through, 280–281
   5. providing during performance reviews, 254–255
   6. in publishing industry, 190–191, 192
   7. rapid and regular, as a general benefit of scrum, 173
   8. stakeholder, 119–120
   9. in video-game development, 148
9. feedback loop
   1. about, 126–128
   2. testing in the, 131–132
10. Feiler, Bruce (author)
    1. “Agile programming — for your family” TED talk, 304
11. Fibonacci numbers, 74–79, 301
12. finances
    1. about, 247, 258
    2. budgets, 261–262
    3. emergency fund, 308–309
    4. incremental funding, 258–260
    5. securing financial freedom, 310–311
    6. statements of position (SOP), 261
13. finding relationships with scrum, 290–299
14. fist of five, 76–77
15. fitness goals, 312–314
16. 5-6-7 framework, 14
17. flexibility
    1. in software development, 140–142
    2. in video-game development, 148
18. flyover project, 162–163
19. focus(ing)
    1. multitasking vs., 296–297
    2. as a Scrum value, 23
20. follow-up, in sales pipeline/funnel, 272
21. forces, external, 130
22. Ford, Henry (businessman), 227
23. Ford Motor Co., 258
24. formality, resisting, 20–21
25. fragmentation, 222
26. frameworks
    1. about, 12–13
    2. 5-6-7, 14
    3. Large-Scale Scrum (LeSS), 242–243
    4. Large-Scale Scrum (LeSS) Huge, 243–244
    5. 3-3-5, 13
27. frequency, of release, 141
28. Fuji-Xerox, 155
29. Fulgham, Chad (CIO), 188
30. fun, in video-game development, 148
31. future processes, in implementation strategy, 328

G

1. General Electric, 179
2. Global Positioning System (GPS), 18
3. goals
   1. company, 35–37
   2. lack of transparency in, 251
   3. life. See life goals
   4. release. See release goals
   5. release plan, 88–89
   6. sprint. See sprint goals
4. Google, 141, 153, 260
5. GORE-TEX, 260
6. governance, 12
7. GPS (Global Positioning System), 18
8. graduating, from high school, 320–322
9. guilds, 210

H

1. handling
   1. rejection, 115–116
   2. unfinished requirements, 117
2. hardware development
   1. about, 167
   2. identifying high-risk requirements, 167
   3. live, 167–169
3. Hawthorne effect, 67
4. Hawthorne Works, 67
5. health care
   1. about, 171–173
   2. cost cutting, 176–177
   3. increased quality, 175
   4. issue management, 178
   5. medical device manufacturing and safety, 178–179
   6. reduced mistakes, 175
   7. regulations for, 177
   8. risk management, 178
   9. speed to market, 173–174
6. Healthcare.gov, 153
7. Hewlett-Packard, 258
8. hiring, scrum in, 252–253
9. holocracy, 254
10. home building, 163–164
11. Honda, 155
12. houses, as liabilities, 311
13. Howey, Hugh (author)
    1. Wool, 191
    2. Wool Omnibus, 191
14. HR. See human resources (HR)
15. human resources (HR)
    1. about, 247
    2. creating culture, 249–257
    3. scrum and, 248

I

1. IaaS (Infrastructure as a Service), 152
2. IBM, 212
3. icons, explained, 3
4. ICT (information and computer technology) consulting company, 274
5. identifying
   1. challenges, 336
   2. pilot projects, 330–332
   3. talent, 328–329
6. implementation strategy, 327–328
7. importance, of pilot projects, 331
8. improvement
   1. antipatterns, 129–130
   2. culture of innovation, 132–133
   3. embracing change, 142–147
   4. external forces, 130
   5. feedback loop, 126–128
   6. hardware development, 167–169
   7. in-flight course correction, 130–131
   8. need for certainty, 125–126
   9. pillars of, 16–17
   10. software applications, 147–153
   11. testing in the feedback loop, 131–132
   12. transparency, 128
9. improvement type, of backlog item, 59
10. incentivizing, 250
11. incremental funding, 258–260
12. increments, product, 120
13. Independent, as a user story quality, 62
14. in-flight course correction, 130–131
15. influencers, 32
16. InfoQ, 364
17. information and computer technology (ICT) consulting company, 274
18. information sharing, customer service and, 283–284
19. Infrastructure as a Service (IaaS), 152
20. innovation
    1. culture of, 132–133
    2. stability vs., 212–217
21. inspecting
    1. about, 124
    2. customer service and, 280–281, 284–285
    3. for families, 304–305
    4. importance of, 334–335
    5. as a pillar of improvement, 16–17
    6. in publishing industry, 190–192
    7. as you release, 142
22. integration
    1. as a factor in “done” definition, 72
    2. as a step for building requirements, 52
23. Intel, 166
24. interference, 41
25. Internet of Things (IoT), 164
26. Internet resources
    1. Agile Alliance, 362
    2. Agile Manifesto, 18
    3. Agile Marketing Manifesto, 267
    4. “Agile programming — for your family” TED talk, 304
    5. “Agile Project Development at Intel: A Scrum Odyssey” case study, 166
    6. Agile School, 306
    7. burndown chart, 100
    8. Cheat Sheet, 365
    9. Dummies, 365
    10. estimation poker cards, 75
    11. half-marathon training, 314
    12. Healthcare.gov, 153
    13. InfoQ, 364
    14. Large-Scale Scrum (LeSS), 364
    15. Pink, Daniel (author), 65, 133
    16. Platinum Edge, 364
    17. racing in reverse, 220
    18. “A Real-Life Example of Agile, Incremental Delivery of an Infrastructure Project in Bangalore, India,” 162
    19. Scaled Agile Framework (SAFe), 363
    20. Scrum Alliance, 329, 361
    21. Scrum at Scale model, 236
    22. Scrum Guide, 124
    23. Scrumguides.org, 362
    24. Scruminc.com (Scrum at Scale), 363
    25. Scrum.org, 363
    26. ScrumPLoP, 363
    27. student loans, 311
27. intrapreneurship, 260
28. INVEST acronym, 62
29. involving customers, 159–160
30. in-your-face documentation, 72
31. IoT (Internet of Things), 164
32. iSense Prowareness, 274–275
33. issue management, in healthcare, 178
34. IT management and operations
    1. about, 201–202
    2. Big Data, 202–208
    3. innovation vs. stability, 212–217
    4. Large Data Migration, 202–208
    5. profit-and-loss potential, 211–212
    6. retiring-boomer gap, 210–211
    7. service-versus-control, 208–210
35. iterative planning process, 102
36. iTunes, 190

J

1. J Sainsbury PLC, 258
2. Johns Hopkins CubeSat, 168
3. Johnson, Spencer (author)
   1. The New One Minute Manager, 38
4. JPMorgan, 245

K

1. kanban, in IT management, 214–217
2. Kanban board, 114
3. Kennedy, Anna (author)
   1. Business Development For Dummies, 264
4. knowable things, 127
5. known things, 127

L

1. Large Data Migration, 202–208
2. Large-Scale Scrum (LeSS)
   1. about, 241–242, 364
   2. framework, 242–243
   3. Huge framework, 243–244
3. Larsen, Diana (author)
   1. Agile Team Retrospectives: Making Good Teams Great, 122, 335
4. lateral thinking, 132
5. law enforcement, scrum and, 186–188
6. Layton, Mark (author)
   1. Agile Project Management For Dummies, 2nd Edition, 16, 38, 192
   2. Scrum For Dummies, 193
7. lead time, 216
8. leads, in sales pipeline/funnel, 271
9. Lean Startup
   1. about, 225–227
   2. retirement and, 309
10. lean-agile leaders, as a portfolio-level role, 238
11. learning
    1. antipatterns, 129–130
    2. continued, 336
    3. culture of innovation, 132–133
    4. early, 319–320
    5. embracing change, 142–147
    6. external forces, 130
    7. feedback loop, 126–128
    8. hardware development, 167–169
    9. in-flight course correction, 130–131
    10. lack of support for, 340
    11. need for certainty, 125–126
    12. software applications, 147–153
    13. testing in the feedback loop, 131–132
    14. transparency, 128
12. legacy systems, converting, 207
13. length, sprint, 93–95
14. LeSS (Large-Scale Scrum)
    1. about, 241–242, 364
    2. framework, 242–243
    3. Huge framework, 243–244
15. levels of requirement decomposition, 51–52
16. life balance, 314–316
17. life cycle, sprint, 95–97
18. life goals
    1. about, 307
    2. fitness, 312–314
    3. life balance, 314–316
    4. retirement, 307–312
    5. studying, 319–324
    6. travel, 316–318
    7. weight, 312–314
19. Lockheed Martin, 260
20. Los Angeles Department of Water and Power, 286

M

1. maintenance, in IT management, 213–214
2. maintenance type, of backlog item, 59
3. malware, 209
4. manager:creator ratio, 359
5. “Managing the Development of Large Software Systems” (Royce), 139–140
6. manufacturing
   1. about, 164–165
   2. fastest to market, 165
   3. shareholder value, 165
   4. strategic capacity management, 166
7. marketing
   1. about, 264
   2. adopting scrum in, 266–267
   3. Agile Advantage surveys, 266–267
   4. defined, 263
   5. evolution of, 264–265
   6. scrum and, 264–269
   7. scrum in action, 267–269
   8. social media, 265–266
   9. speed to, 165
   10. in video-game development, 150
8. The Marshmallow Challenge (TED talk), 19
9. maturity, importance of, 334, 335–336
10. maximizing environment efficiency, 332
11. McDonald's, 258
12. measurability, of pilot projects, 331
13. medical devices, manufacturing and safety of, 178–179
14. meeting, as a dating challenge, 291
15. Mehrabian, Albert (professor), 69, 284
16. mentoring program, 210
17. metrics
    1. customer service, 280
    2. redefining, 336
    3. relevancy of with scrum, 347–348
    4. for scrum, 351–359
18. Microchip, 270
19. Microsoft Office, 229
20. migration, large-scale, 202–208
21. military, scrum and, 186–188
22. minimum viable product (MVP), 85, 207, 259, 301
23. Mission Command, 186–187
24. mistakes, reduced, in healthcare, 175
25. misunderstandings, 285
26. MMBD (Multi-Mission Bus Demonstrator) project, 168
27. mobilizing transition teams, 329–330
28. modular architecture, in Saab Jet Fighter, 169
29. monetization, faster, as a general benefit of scrum, 173
30. Moore, Geoffrey (author)
    1. Crossing the Chasm, 36
31. Mortensen, Brady (news professional), 194
32. motivating creativity, 133
33. Multi-Mission Bus Demonstrator (MMBD) project, 168
34. multitasking
    1. about, 116
    2. focusing vs., 296–297
35. music industry, 190
36. MVP (minimum viable product), 85, 207, 259, 301

N

1. National Public Radio (NPR), 194, 195
2. Negotiable, as a user story quality, 62
3. Nelson, Admiral, 187–188
4. “New New Product Development Game,” 155
5. news media
   1. about, 194–195
   2. defining “done,” 195–196
   3. sprint flexibility, 197
   4. team for, 196–197
6. “The New New Product Development Game,” 15
7. The New One Minute Manager (Blanchard and Johnson), 38
8. nonverbal signals, 285
9. NPR (National Public Radio), 194, 195
10. numerator, 63

O

1. obfuscation, 129
2. Observer effect, 67
3. OC (opportunity cost), 85, 224, 356
4. on demand release, 141
5. openness, as a Scrum value, 24
6. open-source hardware, 167
7. operations and IT management
   1. about, 201–202
   2. Big Data, 202–208
   3. innovation vs. stability, 212–217
   4. Large Data Migration, 202–208
   5. profit-and-loss potential, 211–212
   6. retiring-boomer gap, 210–211
   7. service-versus-control, 208–210
8. opportunity cost (OC), 85, 224, 356
9. organization structures, human resources and, 250–252
10. organizational culture, creating, 249–257
11. Ostermiller, Steven (author)
    1. Agile Project Management For Dummies, 2nd Edition, 16, 138, 192
12. overhead type, of backlog item, 59
13. ownership, increased, with scrum, 347

P

1. PaaS (Platform as a Service), 152
2. pair programming
   1. about, 67
   2. in college, 323
   3. creating cross-functionality by using, 66
3. Pattern Languages of Programs (PLoP), 363
4. PayPal/TIO, 209
5. peer-to-peer communication, in Wikispeed modular car, 168
6. people allocation, 220
7. performance reviews, 253–256
8. personal interruptions, 41
9. personal responsibility, in family life, 299
10. personas, 60
11. Petraeus, David (General), 187
12. pharmaceutical industry, 173–174
13. Phase I, of sprint planning, 98
14. Phase II, of sprint planning, 98–99
15. phased approach, 179
16. phishing, 209
17. pillars of improvement, 16–17
18. pilot projects
    1. identifying, 330–332
    2. kicking off, 333–334
19. Pink, Daniel (author)
    1. Drive: The Surprising Truth About What Motivates Us, 65
    2. TED talks, 133
20. “plan all and then develop all” mindset, 145
21. planning
    1. prioritizing, 300–303
    2. projects. See project planning
    3. travel, 316–318
    4. weddings, 298–299
22. Platform as a Service (PaaS), 152
23. Platinum Edge, 364–365
24. PLoP (Pattern Languages of Programs), 363
25. PO (product owner), 234
    1. about, 234
    2. in construction, 158
    3. effectiveness of, 338
    4. hiring, 253
    5. in Large-Scale Scrum (LeSS) Huge, 244
    6. for news media, 197
    7. power in, 32–34
    8. responsibilities of, 32–33
    9. Scrum at Scale model, 234–236
    10. scrum of scrums model, 230–231
    11. as a Scrum role, 12
    12. in sprint review process, 118
    13. why they love Scrum, 34–35
26. Pomodoro technique, 42
27. portfolio management
    1. about, 219
    2. advantages of SAFe model, 239–241
    3. challenges in, 220–225
    4. Large-Scale Scrum (LeSS), 241–244
    5. Lean Startup, 225–227
    6. Scaled Agile Framework (SAFe), 237–241, 238
    7. scaling scrum for large portfolios, 228
    8. Scrum at Scale approach, 232–237
    9. scrum of scrums model, 230–232
    10. vertical slicing, 228–229
28. postproduction, as a stage in video-game development, 149
29. potential challenges, in implementation strategy, 328
30. power, in product owner, 32–34
31. predictability, 179
32. preproduction, as a stage in video-game development, 148
33. principles
    1. Agile, 18–20
    2. for projects, 20–22
34. prioritizing
    1. conflicting in families, 299
    2. planning, 300–303
    3. projects, 220
    4. in release planning, 86–88
    5. requirements, 50–51
    6. setting, 300–303
    7. sprints, 104–105
    8. for students, 321
35. product backlog
    1. about, 53–55
    2. creating, 312
    3. customer service and, 281–282
    4. defined, 10
    5. development team and estimating, 70–71
    6. ever-changing, 55
    7. in Large-Scale Scrum (LeSS), 243
    8. for news media, 196, 197
    9. refining, 55–58
    10. retirement and, 310
    11. setting capacity, 101–102
    12. travel and, 317
36. product defects, fewer, as a general benefit of scrum, 173
37. product increments, 120
38. product owner (PO)
    1. about, 234
    2. in construction, 158
    3. effectiveness of, 338
    4. hiring, 253
    5. in Large-Scale Scrum (LeSS) Huge, 244
    6. for news media, 197
    7. power in, 32–34
    8. responsibilities of, 32–33
    9. Scrum at Scale model, 234–236
    10. scrum of scrums model, 230–231
    11. as a scrum role, 12
    12. in sprint review process, 118
    13. why they love scrum, 34–35
39. product owner agent role, 35
40. product release
    1. about, 73
    2. adapting as you, 142
    3. customizing size of, 141–142
    4. on demand, 141
    5. frequency of, 141
    6. inspecting as you, 142
    7. for news media, 196
    8. risk and, 350
41. product roadmap. See also roadmap to value
    1. about, 46
    2. creating, 48–49, 312
    3. in estimation refinement, 73
    4. long view of, 46–47
    5. setting timeframes, 49–50
    6. tools for, 47–48
42. production, as a stage in video-game development, 148
43. products
    1. changes in, 191–192
    2. for news media, 196
44. Professional Scrum Developer (PSD), 363
45. Professional Scrum Master (PSM I, II, III), 363
46. Professional Scrum Product Owner (PSPO I, II), 363
47. profit-and-loss potential, 211–212
48. program, Scaled Agile Framework (SAFe), 238–239
49. progress, exposure and visibility of, 348–349
50. project attrition, 358
51. project planning
    1. about, 45
    2. breaking down requirements, 50–52
    3. common practices, 59–62
    4. in families, 300–301
    5. product backlog, 53–62
    6. product roadmap, 46–50
    7. terminology, 53
52. project-manager, in construction, 158
53. projects
    1. customizing, 152
    2. disconnecting between business objectives and, 222–223
    3. employing transparency in, 128
    4. increased control with scrum, 349–350
    5. pilot, 330–332
    6. principles for, 20–22
    7. prioritizing, 220
    8. setting visions in family life, 300
54. PSD (Professional Scrum Developer), 363
55. PSM I, II, III (Professional Scrum Master), 363
56. PSPO I, II (Professional Scrum Product Owner), 363
57. publishing
    1. about, 189
    2. applying scrum in, 192–193
    3. changes in, 190–193
    4. news media, 194–197
58. pull model, push model vs., 104
59. purpose-driven development, 89
60. push model, pull model vs., 104

Q

1. quality
   1. increased, in healthcare, 175
   2. increased, with scrum, 343–344
2. queuing theory, 95

R

1. racing in reverse, 220
2. readers, changes in, 190–191
3. “A Real-Life Example of Agile, Incremental Delivery of an Infrastructure Project in Bangalore, India,” 162–163
4. recruiting
   1. by Platinum Edge, 364
   2. talent, 328–329
5. redefining metrics, 336
6. reducing
   1. single points of failure, 332–333
   2. stress, 315
7. refactoring
   1. about, 147
   2. in publishing industry, 190–192
   3. in software development, 140–142
8. refactoring code, 140–141
9. regulations, in healthcare, 177
10. rejection, handling, 115–116
11. relative compensation, 250–251
12. relative estimating, 73–74
13. release
    1. about, 73
    2. adapting as you, 142
    3. customizing size of, 141–142
    4. on demand, 141
    5. frequency of, 141
    6. inspecting as you, 142
    7. for news media, 196
    8. risk and, 350
14. release defects, 353
15. release goals
    1. about, 88–89
    2. retirement and, 309
    3. setting, 312, 316
    4. for students, 321, 323
16. release planning
    1. about, 83–84, 84–86
    2. customer service and, 282
    3. defined, 84
    4. in estimation refinement, 73
    5. in families, 301
    6. goals for, 88–89
    7. in practice, 90–92
    8. prioritizing, 86–88
    9. release sprints, 89–90
17. release sprints, 89–90
18. Remember icon, 3
19. Republican National Committee, 209
20. requirement type, of backlog item, 59
21. requirements
    1. elaboration of, as a step for building requirements, 52
    2. levels of decomposition of, 51–52
    3. prioritizing, 50–51
    4. steps for building, 52
    5. unfinished, handling, 117
22. resisting formality, 20–21
23. resources, 361–365
24. respect, as a scrum value, 24
25. responsibilities, of product owner, 32–33
26. retirement
    1. about, 307–308
    2. building, 309
    3. debt and, 312
    4. saving for emergencies, 308–309
    5. securing financial freedom, 310–311
27. retiring-boomer gap, 210–211
28. return on investment (ROI)
    1. about, 259–260
    2. increased, with scrum, 344–345
    3. metrics for, 354–355
    4. new requests withing budgets for, 355
29. returns, maximizing with incremental funding, 259
30. risks
    1. managing in healthcare, 178
    2. mitigating with incremental funding, 259
    3. reduced, with scrum, 350
    4. as a target outcome of product backlog refinement, 56
31. roadmap to value. See also product roadmap
    1. about, 8–9, 31
    2. customer service and, 280–281
    3. dating and, 297
    4. sales process and, 273–274
    5. for studying, 319
    6. vision statement, 36–37
32. ROI (return on investment)
    1. about, 259–260
    2. increased, with scrum, 344–345
    3. metrics for, 354–355
    4. new requests withing budgets for, 355
33. roles
    1. in construction, 158–159
    2. outside scrum, 42–43
    3. product owner agent, 35
    4. scrum, 12
    5. scrum master, 39
    6. stakeholders, 43
34. Royce, Winston (computer scientist)
    1. “Managing the Development of Large Software Systems,” 139
35. rubber duck problem solving, 67
36. rubber duckie test, 67
37. rubber ducking, 67

S

1. Saab Jet Fighter, 169
2. SaaS (Software as a Service), 141, 151
3. SAFe (Scaled Agile Framework)
   1. about, 237, 363–364
   2. advantages of, 239–241
   3. portfolio, 238
   4. program, 238–239
   5. team, 239
4. safety, worker, 161–163
5. sales
   1. about, 269–270
   2. defined, 263
   3. scrum process for, 272–274
   4. scrum solution, 270–272
6. sales call, in sales pipeline/funnel, 272
7. sales cycles, 273
8. sales pipeline/funnel, 270–272
9. Satir's Curve, 331
10. satisfaction surveys, 356–357
11. saving, for emergencies, 308–309
12. scaffolding, 180
13. Scaled Agile Framework (SAFe)
    1. about, 237, 363–364
    2. advantages of, 239–241
    3. portfolio, 238
    4. program, 238–239
    5. team, 239
14. scaling
    1. importance of, 334, 336
    2. methodically, 336
    3. scrum for large portfolios, 228
15. scheduling
    1. conflicting, in family life, 299
    2. daily scrum, 110
16. Schwaber, Ken (Scrum co-creator), 15
    1. The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game, 362
17. scope creep, 179, 223
18. Scott, Chris (blogger), 306
19. scrum. See also specific topics
    1. about, 1, 10–11
    2. applying in publishing industry, 192–193
    3. basics of, 7–24
    4. benefits of, 343–350
    5. common roles outside, 42–43
    6. communicating with, 303–304
    7. companionship and, 293–294
    8. considerations for converting to, 28
    9. converting to, 28–32
    10. customer service and, 280–286
    11. dating with, 294–295
    12. defined, 8
    13. development teams and, 70
    14. faux, 337–338
    15. finding relationships with, 290–299
    16. for fitness goals, 312–314
    17. general benefits of, 173
    18. in hiring, 252–253
    19. human resources (HR) and, 248
    20. for life balance, 314–316
    21. marketing and, 264–269
    22. metrics for, 351–359
    23. origins of, 15
    24. process of, 10
    25. resources, 361–365
    26. for retirement, 307–312
    27. roles of, 12
    28. for sales, 269–275
    29. scaling for large portfolios, 228
    30. social media and, 265–266
    31. software development and, 138–140
    32. steps to transitioning to, 327–336
    33. for studying, 319–324
    34. for travel planning, 316–318
    35. values, 22–24
    36. watering down, 341
    37. wedding planning with, 298–299
    38. for weight goals, 312–314
    39. why product owners love, 34–35
20. Scrum Alliance, 329, 361–362
21. Scrum at Scale model
    1. about, 232–233
    2. product owner, 234–236
    3. scrum master, 233–234
    4. synchronizing, 236–237
    5. website, 236
22. scrum coach, 43
23. Scrum For Dummies (Layton), 193
24. scrum framework
    1. about, 12–13
    2. 5-6-7, 14
    3. 3-3-5, 13
25. scrum frameworks
    1. about, 12–13
    2. 5-6-7, 14
    3. Large-Scale Scrum (LeSS), 242–243
    4. Large-Scale Scrum (LeSS) Huge, 243–244
    5. 3-3-5, 13
26. Scrum Guide (website), 124
27. scrum master
    1. about, 38
    2. in construction, 159
    3. hiring, 253
    4. for news media, 197
    5. reasons for loving scrum, 40
    6. role of, 39
    7. Scrum at Scale model, 233–234
    8. scrum of scrums model, 231–232
    9. as a Scrum role, 12
    10. as servant leader, 39–40
    11. in sprint review process, 118
    12. traits of, 38–39
28. scrum mentors, 43
29. scrum of scrums model
    1. about, 230
    2. customer service and, 281
    3. development team, 231
    4. product owner, 230–231
    5. scrum master, 231–232
30. scrum solutions, 223–225
31. Scrumguides.org, 362
32. Scruminc.com (Scrum at Scale), 363
33. Scrum.org, 363
34. ScrumPLoP, 363
35. The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game (Sutherland and Schwaber), 362
36. seagull management, 130
37. Section 72(t) (tax code), 309
38. security
    1. breach of, 209
    2. challenges with IT, 209
    3. of financial freedom, 310–311
39. seeding teams, 336
40. selecting teams, 340
41. self-managing, 68–69
42. self-organizing, 68–69
43. self-publishing, 191
44. seniority, 250–251
45. serial stories, 191
46. servant leader, scrum master as, 39–40
47. services
    1. about, 151–152, 171
    2. customers and, 278–279
    3. education, 180–186
    4. health care, 171–179
    5. military and law enforcement, 186–188
48. service-versus-control
    1. about, 208–209
    2. security challenges, 209
49. setting
    1. backlog capacity, 101–102
    2. family strategy, 300
    3. prioritization, 300–303
    4. project visions in family life, 300
    5. release goals, 312, 316
    6. sprint goals, 316
    7. time frame for product roadmap, 49–50
    8. visions, 291–292, 312, 316
50. 7Shifts, 147
51. shadowing, creating cross-functionality by using, 66–67
52. shareholder value, 165
53. SHIFT Media Manager, 22
54. shippable, 10
55. Shu Ha Ri technique, 335–336
56. silo teams, 179
57. simplicity, as a cost cutting aid in healthcare, 177
58. situational leadership, 249
59. size
    1. of data, 203
    2. of pilot projects, 331
    3. release, 141–142
    4. as a target outcome of product backlog refinement, 56
60. skill versatility, 358
61. Skillman, Peter (designer), 19
62. Small, as a user story quality, 62
63. smoke and mirrors, 130
64. social media, 265–266
65. Software as a Service (SaaS), 141, 151
66. software development
    1. about, 137
    2. flexibility in, 140–142
    3. refactoring in, 140–142
    4. scrum and, 138–140
67. Sony, 260
68. SOP (statements of position), 261
69. speed to market, in healthcare, 173–174
70. Spotify, 153
71. sprint backlog
    1. about, 99
    2. burndown chart benefits, 100–101
    3. Los Angeles Department of Water and Power, 286
    4. prioritizing sprints, 104–105
    5. push vs. pull, 104
    6. setting backlog capacity, 101–102
    7. working the, 103
72. sprint goals
    1. about, 97–98
    2. retirement and, 310
    3. setting, 316
    4. for students, 321, 323
    5. success rates for, 352
73. sprint lengths
    1. determining, 313
    2. for early learning, 320
    3. for news media, 196
74. sprint planning
    1. about, 83–84, 92, 97
    2. customer service and, 280–281
    3. defining sprints, 92–93
    4. in estimation refinement, 73
    5. in families, 301–302
    6. goals for, 97–98
    7. in kanban, 217
    8. in Large-Scale Scrum (LeSS), 243
    9. in Large-Scale Scrum (LeSS) Huge, 244
    10. length, 93–95
    11. life cycle, 95–97
    12. for news media, 196
    13. Phase I, 98
    14. Phase II, 98–99
75. sprint retrospectives
    1. about, 120–121, 142
    2. adaptation, 124
    3. as a cost-cutting aid in healthcare, 176
    4. customer service and, 281
    5. Derby and Larsen process, 122–124
    6. for fitness goals, 313
    7. importance of, 335
    8. inspection, 124
    9. in kanban, 217
    10. in Large-Scale Scrum (LeSS), 243
    11. in Large-Scale Scrum (LeSS) Huge, 244
    12. performance issues and, 252
    13. process of, 121–122
    14. risk and, 350
    15. for weight goals, 313
76. sprint reviews
    1. about, 117–118
    2. customer service and, 281
    3. importance of, 335
    4. in kanban, 217
    5. in Large-Scale Scrum (LeSS), 243
    6. in Large-Scale Scrum (LeSS) Huge, 244
    7. for news media, 197
    8. performance issues and, 252
    9. process of, 118–119
    10. product increments, 120
    11. risk and, 350
    12. stakeholder feedback, 119–120
    13. in Wikispeed modular car, 168
77. sprints
    1. about, 107
    2. components of, 93
    3. daily scrum, 108–112
    4. defined, 10, 84
    5. defining, 92–93
    6. estimating, 63
    7. flexibility of in news media, 197
    8. planning length of, 93–95
    9. prioritizing, 104–105
    10. release, 89–90
    11. retirement and, 309
    12. sprint retrospective, 120–124
    13. sprint review, 117–120
    14. team task board, 112–117
    15. in Wikispeed modular car, 168
78. squeaky-wheel syndrome, 220
79. stability, innovation vs., 212–217
80. stakeholders
    1. customers as most crucial, 278–280
    2. feedback from, 119–120
    3. as role outside scrum, 42–43
    4. in sprint review process, 118
81. starting pilot projects, 333–334
82. statements of position (SOP), 261
83. step-by-step plan, in implementation strategy, 328
84. story points
    1. about, 74–79
    2. velocity and, 81
85. strategic capacity management, 166
86. strategy, company, 35–37
87. stress, reducing, 315
88. student loans, 311
89. student-to-teacher ratios, 182
90. studying
    1. in college, 323–324
    2. early learning, 319–320
    3. graduating from high school, 320–322
    4. scrum for, 319–324
91. subcontractors, 160–161
92. success factors, in implementation strategy, 328
93. sunk costs, 145
94. Sutherland, Jeff (Scrum co-creator), 15, 27
    1. The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game, 362
95. swarming, 114–115
96. synchronizing Scrum at Scale mode, 236–237

T

1. talent retention, increased
   1. as a general benefit of scrum, 173
   2. identifying and recruiting, 328–329
2. tangible goods
   1. about, 155
   2. construction, 157–163
   3. home building, 163–164
   4. manufacturing, 164–166
   5. waterfall, 156–157
3. task board
   1. about, 112–114, 306
   2. for early learning, 320
   3. for fitness/weight goals, 313
   4. handling rejection, 115–116
   5. handling unfinished requirements, 117
   6. swarming, 114–115
   7. team, 112–117
4. tasks, 53
5. TDD (test-driven development), 239–240
6. team interruptions, 41
7. team morale, higher, with scrum, 345–346
8. team task board
   1. about, 112–114
   2. handling rejection, 115–116
   3. handling unfinished requirements, 117
   4. swarming, 114–115
9. “team topics,” 111
10. team-building, in college, 323
11. teams. See also development teams
    1. about, 11–12, 39
    2. communication in, 296
    3. defined, 269
    4. development. See development team
    5. in Johns Hopkins CubeSat, 168
    6. member turnover, 357
    7. for news media, 196–197
    8. Scaled Agile Framework (SAFe), 239
    9. seeding, 336
    10. selecting, 340
    11. thinking and acting as, 21–22
    12. turnover, 357
    13. underperforming members of, 251–252
12. Technical Stuff icon, 3
13. technology, 143–145, 332
14. Telefonica Digital, 169
15. Testable, as a user story quality, 62
16. test-driven development (TDD), 239–240
17. tested, as a factor in “done” definition, 72
18. testing
    1. automated, 338–339
    2. behavior tests, 296
    3. in the feedback loop, 131–132
19. themes, 53
20. thrashing, 116, 221–222, 303, 316, 320
21. 3-3-5 framework, 13
22. 3M, 260
23. 360-degree performance reviews, 255–256
24. time frames
    1. as a dating challenge, 290
    2. setting for product roadmap, 49–50
25. time to implementation, accelerated, as a general benefit of scrum, 173
26. time to market
    1. decreased, with scrum, 344
    2. metrics for, 353–354
27. timebox, 78, 151, 304
28. timing, of decisions, 127
29. Tip icon, 3
30. titles, creating cross-functionality by not using, 66
31. tools, for product roadmap, 47–48
32. total project duration/cost metric, 355
33. Toyota, 164
34. training
    1. ensuring, 329
    2. lack of, 338
    3. by Platinum Edge, 365
35. traits, of scrum master, 38–39
36. transformation, by Platinum Edge, 365
37. transitioning
    1. lack of support for, 339
    2. mobilizing transition teams, 329–330
    3. to scrum, 327–336
38. transparency
    1. in construction, 157–158
    2. as a cost cutting aid in healthcare, 177
    3. employing in projects, 128
    4. lack of in goals, 251
    5. as a pillar of improvement, 16
    6. in sprint planning for families, 302
    7. in Wikispeed modular car, 168
39. travel planning, scrum for, 316–318
40. turnover, 357
41. Twitter, 22

U

1. Uber, 209
2. unfinished requirements, 117
3. unknowable things, 127
4. up-front engineering, 145–146
5. user stories
   1. about, 53
   2. as a product backlog common practice, 59–61
6. user-acceptance testing defects, 353

V

1. Valuable, as a user story quality, 62
2. value (V)
   1. about, 85, 224, 356
   2. roadmap to, 8–9, 31
   3. scrum, 22–24
   4. shareholder, 165
3. velocity, 80–81
4. vertical slicing, 228–229
5. video-game development, 148–151
6. visibility
   1. of pilot projects, 331
   2. of progress with scrum, 348–349
   3. in sprint planning for families, 302
7. vision statement, 36–37, 292
8. visions
   1. customer service and, 280
   2. setting, 291–292, 312, 316
   3. for students, 321
   4. for studying, 319
9. visualizing, writing vs., 22
10. voice-to-voice communication, 285
11. von Moltke, Helmuth (military strategist), 186–187

W

1. Wake, Bill (eXtreme Programming movement influencer), 62
2. Walmart, 202
3. Warning icon, 3
4. Washington Post (newspaper), 194, 195
5. The Waste Land (poem), 191–192
6. waterfall method
   1. about, 96
   2. fall of, 156–157
   3. project management with, 138–140
   4. transitioning from, 240–241
7. watering down scrum, 341
8. websites
   1. Agile Alliance, 362
   2. Agile Manifesto, 18
   3. Agile Marketing Manifesto, 267
   4. “Agile programming — for your family” TED talk, 304
   5. “Agile Project Development at Intel: A Scrum Odyssey” case study, 166
   6. Agile School, 306
   7. burndown chart, 100
   8. Cheat Sheet, 365
   9. Dummies, 365
   10. estimation poker cards, 75
   11. half-marathon training, 314
   12. Healthcare.gov, 153
   13. InfoQ, 364
   14. Large-Scale Scrum (LeSS), 364
   15. Pink, Daniel (author), 65, 133
   16. Platinum Edge, 364
   17. racing in reverse, 220
   18. “A Real-Life Example of Agile, Incremental Delivery of an Infrastructure Project in Bangalore, India,” 162
   19. Scaled Agile Framework (SAFe), 363
   20. Scrum Alliance, 329, 361
   21. Scrum at Scale model, 236
   22. Scrum Guide, 124
   23. Scrumguides.org, 362
   24. Scruminc.com (Scrum at Scale), 363
   25. Scrum.org, 363
   26. ScrumPLoP, 363
   27. student loans, 311
9. wedding planning, 298–299
10. weight goals, 312–314
11. Wiggins, Alex (blogger), 321–322
12. Wikispeed modular car, 168
13. WIP (work in progress), 103, 117
14. Wool (Howey), 191
15. Wool Omnibus (Howey), 191
16. work in progress (WIP), 103, 117
17. work space, 332
18. worker safety, 161–163
19. working system, in Johns Hopkins CubeSat, 168
20. work-in-progress limits, for development teams, 224
21. worms, 209
22. writers, changes in, 191
23. writing, visualizing vs., 22
24. Wujec, Tom (author and speaker), 19

X

1. xerography, 268
2. Xerox, 268–269
3. XP (eXtreme Programming), 62

Y

1. YouTube, 192

Z

1. Zappos, 254
2. zettabyte, 203