Anti-patterns
6
Very long sprints with very large
pieces of work – testing
backloaded to the very end
Slide 7
Slide 7 text
Anti-patterns
7
Developers not allowed to talk to
business, not responsible for
estimates, not allowed any
responsibility for low-level technical
decisions
Slide 8
Slide 8 text
Anti-patterns
8
Estimates produced only by
Product Owner, Architect or an
other single person
Slide 9
Slide 9 text
Anti-patterns
9
Multiple Product Owners working
on the same product
Slide 10
Slide 10 text
Anti-patterns
10
Stagnant technical practices
Slide 11
Slide 11 text
Anti-patterns
11
Not paying off technical debt
Slide 12
Slide 12 text
Anti-patterns
12
No retrospectives
Slide 13
Slide 13 text
Anti-patterns
13
Turning people off with too many
radical changes
Slide 14
Slide 14 text
Anti-patterns
14
Ultra-detailed user stories
Slide 15
Slide 15 text
Anti-patterns
15
Scrum Master as boss - assigning
tasks and giving orders rather than
facilitating and coaching
Slide 16
Slide 16 text
Anti-patterns
16
Acquiring an agile process and then
dictating that it can never be
changed
Slide 17
Slide 17 text
Anti-patterns
17
Using an ‘agile tool’ to define the
process
Slide 18
Slide 18 text
Anti-patterns
18
Product Owner == Scrum Master
Slide 19
Slide 19 text
Anti-patterns
19
Product backlog determined at
outset and forever fixed
Slide 20
Slide 20 text
Anti-patterns
20
Product Owner with no authority to
decide priority, change features etc
(e.g. proxy PO)