10x developers, 262
AAD (Azure Active Directory), 111
acceptance criteria, specifying, 166
acceptance tests, 233. See also ATDD (acceptance test-driven development); software development
naming convention, 249
and Definition of Done, 252–253
Fabrikan Fiber Case Study, 253
Test Case work items, 237
access levels, Azure DevOps, 66–67
ActionableAgile Analytics extension, 303, 310
active listening, 269
Developers, 9
execution, 109
adaptation, 5
estimation techniques, 169
Agile Manifesto, 262, 263, 369
ALM (application lifecycle management), 49–50, 263. See also Azure DevOps; DevOps
2010 version, 49
2015 version, 50
anchoring, 171
artifacts, 5, 30–31. See also Increments; Product Backlog; Sprint Backlog
Increments, 39
Nexus framework, 377
Product Backlog, 31, 32–33, 34–35
developer interactions, 32
Fabrikan Fiber Case Study, 36
PBIs (Product Backlog Items), 31–32, 34
and Product Owner, 35
three C’s, 33
collaboration, 38
Definition of Done, 37
Fabrikan Fiber Case Study, 38
assessing progress, 326
toward a Product Goal, 326–327
ATDD (acceptance test-driven development), 233–234, 244–245, 245–246. See also TDD (test-driven development)
naming convention, 249
and BDD (behavior-driven development), 245
Fabrikan Fiber Case Study, 246
automated acceptance testing, 247–252
naming convention, 249
availability, 191
Azure DevOps, 5–6, 51, 52–53, 54, 55
Fabrikan Fiber Case Study, 67
ActionableAgile Analytics extension, 303, 310
analytics widgets, 309
Burndown, 328
Burnup, 329
Azure Boards, 56, 71, 110, 139, 192
bulk-modifying work items, 153–154
categories, 73
creating a Product Backlog, 140–142
customizing the Taskboard, 221
ordering the Product Backlog, 178–179
PBI (Product Backlog Item) work item, 76–78
removing PBIs from forecast, 194
Scrum process, 75
Taskboard, 207, 211–214, 215–216, 217–221
workflow states, 74
migrating to Azure DevOps Services, 62–63
Azure DevOps Services, licenses, 66
deleting test artifacts, 241
continuous delivery of value, 52–53
creating an organization, 111–112
information radiators, 130
Summary page, 130
licenses, 113
Marketplace extensions, 115–116
for Professional Scrum, 117–119
Nexus support
configuring additional teams, 380–382
configuring iterations, 384–385
Open in Excel extension, 153
projects
determining number needed, 121–123
providing access to your organization, 112–114
services, 54
stakeholder access, 67
Fabrikan Fiber Case Study, 64
subscriptions, 65
Azure DevOps Services, 112
project collection, 111
BDD (behavior-driven development), 245
billing
multi-organization, 114
blocked tasks, 219–221, 315–316
branching, 289
and collaboration, 290
Fabrikan Fiber Case Study, 288
pull requests, 290
trunk-based software development, 287–288
Bug work item type, 79–80, 81, 97
Fabrikan Fiber Case Study, 81
reactivations, 163
proven practices, 159
in-Sprint vs. out-of-Sprint, 160–163
tracing, 160
triage, 156
bulk-modifying work items, 153–154
assessing progress toward a Sprint Goal, 327–331
business value, 165
capturing the Sprint Goal, 201–202
categories, parent-child links, 149
CI (continuous integration) builds, 249–250, 288–289
CMMI (Capability Maturity Model Integration) process, 71, 73
collaboration, 11, 17, 23, 37, 261, 263
active listening, 269
being T-shaped, 271
and branching, 290
collective code ownership, 274–277
associating Git commits to work items, 279–280
tracking ownership in Azure DevOps, 275–277
development practices, 274
feedback, 272
Developer, 273
handling interruptions, 283
setting up a team room, 266–267
software development, 262
Sprint Backlog, 38
collective code ownership, 274–275
associating Git commits to work items, 279–280
tracking ownership in Azure DevOps, 275–277
commitment, 43, 191. See also values
continuous delivery (CD), 52
continuous improvement, 321
customization, Taskboard, 221
Daily Scrum, 16, 23–24, 189, 207, 217
Fabrikan Fiber Case Study, 24
Day, B., 217
Definition of Done, 7, 37, 40–41, 134, 191, 195–196, 342–343
Integrated Increments, 379–380
Developers, 8–10, 18, 37, 262. See also software development; Sprint Planning
10x, 262
activities, 9
bug tracing, 160
Fabrikan Fiber Case Study, 10
feedback, 273
handling interruptions, 283
interaction with Sprint Backlog, 36–37
interactions with Product Owner, 11–12
interactions with stakeholders, 15
measuring performance, 349
pairing, 282
and Scrum values, 43
services provided by Scrum Master, 14
Sprint Review, 25
taking ownership of tasks, 216–219
velocity, 196
editing, work items, 153
Epic work items, 82–83, 84–85, 98
Professional Scrum, 102
estimating
size of PBIs, 168–169, 323–324
poker planning sessions, 170–171
Daily Scrum, 16, 23–24, 189, 207, 217
inspection and adaptation, 346
Nexus framework, 373
Sprint Planning, 6, 16, 19, 189, 190–191
capturing the Sprint Goal, 201–202
Definition of Done, 37
Fabrikan Fiber Case Study, 23
length of, 19
Nexus framework, 374
outputs, 191
Sprint Goal, 191
Sprint Retrospective, 7, 17, 27, 345
Fabrikan Fiber Case Study, 29
flow-based, 318
length of, 27
length of, 25
Nexus framework, 375
offline, 375
execution activities, 109
extensions
ActionableAgile Analytics, 303, 310
Open in Excel, 153
for Professional Scrum, 117–119
Sprint Goal, 202
Fabrikan Fiber Case Study, 18, 67, 125, 127, 144, 156, 157, 195, 203, 204, 222–225, 269
acceptance tests, 253
active listening, 269
ATDD (acceptance test-driven development), 246
branching, 288
Bug work item, 81
CI (continuous integration) builds, 289
code reviews, 286
commenting in code, 279
Daily Scrum, 24
Developers, 10
epic PBIs, 150
Forecasting tool, 199
Product Owner, 12
productive collaboration, 271
Professional Scrum process, 104
scope creep, 168
Scrum Master, 14
setting up a team room, 267
Sprint Backlog, 38
Sprint Planning, 23
Sprint Retrospective, 29
Sprint Review, 26
stakeholders, 16
TDD (test-driven development), 247
tracking ownership in Azure DevOps, 277
Visual Studio, 64
Visual Studio licenses, 67
FBI Sentinel Project, 321
Feature work items, 85, 87, 88, 98
Professional Scrum, 102
refining, 87
feedback, 272
Developer, 273
Product Owner, 273
FFDD (feature flag-driven development), 336
fields
bug reports, 158
PBI (Product Backlog Item) work item, 76–77, 98–99
fixed-price contracts, 339–341
coaching, 301
inspecting and adapting, 304–305
SLE (service level expectation), 304
Cycle Time, 307
Throughput, 307
Work Item Age, 307
and Sprint Planning, 311, 312–313
and Sprint Retrospective, 318
forecasting, 21
Monte Carlo simulations, 312
PBIs (Product Backlog Items), 193–195
based on past performance, 195–198
renegotiating scope, 331
using the Capacity tool, 200–201
Fowler, M., “Flaccid Scrum”, 343–344
Git, 50, 57, 63, 65. See also software development
associating commits to work items, 279–280
group development
forming stage, 261
norming stage, 261
performing stage, 261
storming stage, 261
swarming stage, 261
hidden work item types, 74–75, 236
Hinshelwood, M., 154
hoarding, 281
hogging, 281
Impediment work items, 91–92, 93–94
importing, PBIs (Product Backlog Items), 150–153
Improvement work item, 345
in-Sprint bugs, 161–162. See also bugs
Integrated, 379
information radiators, 130
Summary page, 130
inheritance process model, 100
inputs, Sprint Planning, 190–191
inspection, 5
Kanban, 50, 56, 175, 233, 236, 295. See also flow
flow-based Daily Scrum, 314–315
flow-based Scrum events, 310–311
flow-based Sprint Planning, 311–313
flow-based Sprint Retrospective, 318
flow-based Sprint Review, 317–318
Professional, 295
and the Sprint, 311
Kanban board, 297–298. See also PBIs (Product Backlog Items)
columns, 299
inspecting and adapting workflow, 304–305
pull systems, 302
keyboard shortcuts, Azure DevOps, 142–143
licenses
Azure DevOps, 113
Basic + Test Plans, 235
Little’s law, 122
Live Updates, 213
managing
WIP (work in progress), 302–304
SLE (service level expectation), 303, 304
meetings, 267–269. See also collaboration; Scrum Team
organizing, 268
Microsoft Excel, importing PBIs, 151–153
Microsoft Test Manager, 49, 50
migrating, to Azure DevOps Services, 62–63
Monte Carlo simulations, 312
multi-organization billing, 114
artifacts, 377
configuring additional teams, 380–382
elements, 371
events, 373
Integration Team, 379
managing the Product Backlog, 385–386
Sprint Goal, 378
Sprint Planning, 374
Nexus Integration Team, 372–373
observer effect, 226
Open in Excel extension, 153
open-plan offices, 267
ordering the Product Backlog, 178–179
out-of-Sprint bugs, 162–163. See also bugs
outputs, Sprint Planning, 191
parent-child links, 149
PBIs (Product Backlog Items), 6, 7, 18, 20, 21–22, 25, 31–32, 49, 76, 77–78, 139, 141, 144
acceptance criteria, 166
adding in Azure Boards, 143, 144–146
aging, 300
Effort field, 169
based on past performance, 195–198
using the Capacity tool, 200–201
Increments, 7
INVEST, 34
poker planning sessions, 170–171
pull systems, 302
push systems, 302
removing from forecast, 194
velocity, 10
workflow states, 99
permission groups, 124
permissions, 66
anchoring, 171
poker planning sessions, 170–171
anchoring, 171
activities, 109
adding members to projects, 123–125
creating an Azure DevOps organization, 111–112
determining number of projects needed, 121–123
providing access to the organization, 112–114
setting up project development, 119
setting up the development environment, 110
administrative and configuration activities, 114–115
process(es), 72
Little’s law, 122
Professional Scrum, 100–101, 102–104
Fabrikan Fiber Case Study, 104
updating Product Backlog Item work item type, 101
workflow states, 102
Scrum, 75
PBI (Product Backlog Item) work item, 76–78
selecting for Azure Boards, 71–72
workflow states, 74
Product Backlog, 6, 31, 32–33, 34–35, 139, 190. See also PBIs (Product Backlog Items)
Backlog Priority field, 144–146
Basic access, 141
creating in Azure Boards, 140–142
developer interactions, 32
Fabrikan Fiber Case Study, 30, 36
PBIs (Product Backlog Items), 31–32, 34
proven practices for creating, 155
refinement, 7, 30, 164–166, 168
three C’s, 33
product development, 55–56. See also software development
setting up the development environment, 110
Product Goal, 6
Product Owner, 6, 8, 10, 11, 19, 35, 139, 160–161, 362
challenges of working with, 349–352
interactions with Developer, 11–12
ordering the Product Backlog, 178–179
productive collaboration, 270–271
Professional Kanban, 295
Professional Scrum, 5–6, 44, 54, 56, 97, 360–361. See also Nexus framework; process(es); Scrum Team; software development; Sprints
creating a system process, 100–104
high-performance teams, 366–367
Improvement work item, 345
Marketplace extensions, 117–119
elements, 371
events, 373
Nexus Integration Team, 372–373
scaling, 369
project collection, 111
project managers, 13
projects. See also Scrum Team
determining number needed, 121–123
information radiators, 130
Summary page, 130
permission groups, 124
promiscuous pairing, 282
proven practices
bug reporting, 159
creating Product Backlog, 155
PSD (Professional Scrum Developer) program, 344, 364–365
pull policy, 303
pull requests, 290
pull systems, 302
push systems, 302
reactivations, 163
Feature work items, 87
regression tests, 254–256. See also acceptance tests; software development
Reindl, S., 164
renegotiating scope, 331
proven practices, 159
in-Sprint vs. out-of-Sprint, 160–163
ROI (return on investment), 349
roles. See Scrum Team
rules, Scrum, 4
SAFe (Scaled Agile Framework), 97
Schollaart, K., 202
Schwaber, K., 4, 17, 44, 262, 370
Software in 30 Days, 321
science fair, 375
scope creep, 167
Scrum, 4, 49, 56. See also ALM (application lifecycle management); events; Nexus framework; process(es); Professional Scrum; software; Sprints
adaptation, 5
events, 5
and fixed-price contracts, 339–341
inspection, 5
elements, 371
events, 373
Nexus Integration Team, 372–373
activities, 109
adding members to projects, 123–125
administrative and configuration activities, 114–115
creating an Azure DevOps organization, 111–112
determining number of projects needed, 121–123
project configurations, 128–130
providing access to the organization, 112–114
setting up project development, 119
setting up the development environment, 110
Product Backlog, 6
refinement, 7
Product Goal, 6
Product Owner, 6
Fabrikan Fiber Case Study, 12
release models, 181
scaling, 369
Definition of Done, 7
waterfall development, 358–359
zombie, 344
Scrum Guide, 4–5, 10, 11, 12, 15, 20, 35, 44, 75, 97, 164, 169, 206, 233, 310, 341, 358
backlog levels, 98
forecasting, 21
PBI (Product Backlog Item) work item, 98–99
Scrum Master, 8, 12–13, 14, 15
challenges of working with, 355–357
Fabrikan Fiber Case Study, 14
services provided to Developers, 14
skills, 14
Scrum Team, 5, 6, 110. See also collaboration; Developers; events; Sprints; stakeholders
active listening, 269
being T-shaped, 271
collective code ownership, 274–277
development practices, 274
handling interruptions, 283
setting up a team room, 266–267
activities, 9
Fabrikan Fiber Case Study, 10
interaction with Sprint Backlog, 36–37
implementing a definition of ready, 175–177
information radiators, 130
Summary page, 130
making changes to, 10
Nexus framework, 55
poker planning sessions, 170–171
Product Backlog refinement, 164–166
Product Owner, 10, 11, 19, 35, 362
interactions with Developer, 11–12
roles, 8
challenges of working with, 355–357
Fabrikan Fiber Case Study, 14
services provided to Developers, 14
skills, 14
Scrum.org open assessments, 365–366
stakeholders, 15
challenges of working with, 353–355
Fabrikan Fiber Case Study, 16
interactions with Developer, 15
Team Administrator, 127
tracking members’ time, 37
ScrumButs, 360
Scrum.org open assessments, 365–366
SDLC (software development lifecycle), 49, 51
shuhari, 342
skills, building a cross-functional Scrum Team, 362–363
SLE (service level expectation), 303, 304
smells, 17, 41, 52, 63, 78, 91, 110, 114, 121, 140, 144, 147, 151, 156, 161, 163, 174, 178, 179, 196, 197, 199, 201, 202, 208, 210, 211, 213, 218, 219, 225, 226–227, 238, 245, 254, 272, 278, 280, 283, 284, 285–286, 300, 308, 318, 323, 324, 331, 335, 339, 343, 346, 353
software development, 3, 5–6, 18, 369
ATDD (acceptance test-driven development), 233–234, 244–245, 245–246
BDD (behavior-driven development), 245
CI (continuous integration) builds, 288–289
collaboration, 262
common challenges, 322
Daily Scrum, 7
Product Backlog, 6
Product Owner, 6
TDD (test-driven development), 233, 246–247, 247
collaboration, 38
creating, 192
Definition of Done, 37
Fabrikan Fiber Case Study, 38
Nexus framework, 378
Sprint Planning, 16, 19, 189, 190–191, 233
Definition of Done, 37
Fabrikan Fiber Case Study, 23
length of, 19
Nexus framework, 374
outputs, 191
topics, 190
how will the chosen work get done?, 21–22
what can be done in this Sprint?, 20–21
why is this Sprint valuable?, 19–20
whiteboards, 22
Sprint Retrospective, 17, 27, 345
Definition of Done, 41
Fabrikan Fiber Case Study, 29
flow-based, 318
length of, 27
Fabrikan Fiber Case Study, 26
length of, 25
offline, 375
Sprints, 5, 6, 7, 10, 17, 18, 18, 189. See also events
Backlog, 6
Definition of Done, 7
Sprint Retrospective, 7
Goals, 6
inspecting and updating progress, 222–225
and Kanban, 311
Planning, 6
velocity, 10
stakeholders, 5–6, 15, 19, 67, 180
challenges of working with, 353–355
Fabrikan Fiber Case Study, 16
interactions with Developer, 15
stashing code changes, 283–284
subscriptions, Visual Studio, 65
Sutherland, J., 4
Software in 30 Days, 321
taking ownership of tasks, 216–219
tasks, 205–206. See also Daily Scrum; events; PBIs (Product Backlog Items); Sprint Planning
assessing progress, 326
inspecting and updating progress, 222–225
tracking, 205
tracking actual hours, 325–326
TDD (test-driven development), 233, 246–247
Fabrikan Fiber Case Study, 247
Team Administrator, 127
team administrator, 381
Team Foundation Server, 50, 263. See also Azure DevOps Server
teams, 125–128. See also Scrum Team
Test Case work items, 237, 248. See also acceptance tests
test points, 244
test plans, 235, 236. See also acceptance tests
test suites, 235, 237. See also acceptance tests
testing, 233. See also acceptance tests; regression tests
acceptance tests, 233
TFVC (Team Foundation Version Control), 50, 63, 75
tracer bullets, 339
Nexus framework, 379
trunk-based software development, 287–288
T-shaped individuals, 271, 363
Vacanti, D., 295
velocity, 10, 307, 334–335, 349
Fabrikan Fiber Case Study, 64
subscriptions, 65
Visual Studio Online, 65
VSTS (Visual Studio Team System), 49
Wake, B., 175
waterfall development, 358–359
Weber, E., 375
WIP (work in progress)
Wolper, S., Remote Agile Guide, 265
associating with Git commits, 279–280
Fabrikan Fiber Case Study, 81
editing, 153
refining, 87
Impediment, 91–92, 93–94, 208, 322–323
Improvement, 345
parent-child links, 149
Product Backlog, 76
states, 78
workflow states, 99
searching, 165
tracking, 205
workflow, 304–305. See also flow, inspecting and adapting
zombie Scrum, 344