Presented at Global Scrum Gathering Orlando 2016
Because of benefits like predictability, better quality of products, and faster delivery, many companies have adopted or in the process of adopting Agile. However, there are challenges.
David Hawks, CST and Agile Evangelist, explains the common antipatterns of Agile adoption.
3. 64% of Features are Rarely or Never Used
45%$
19%$
16%$
13%$
7%$
Never$
Rarely$
Some5mes$
O8en$
Always$
From:A Standish Group study
Feature/func+on usage in the so2ware industry
Find a Partner and Discuss the following Question:
What causes us to build features which are rarely or never used?
4. PROBLEM #1
WE MAKETOUGH DECISIONSTOO EARLY AND
LOCKTHEM IN
Image Credit: http://i.qkme.me/3unlv7.jpg
20. We want to Shift away from a Requirements Delivery Process…
21. We want to Shift away from a Requirements Delivery Process…
False Assumptions:
22. We want to Shift away from a Requirements Delivery Process…
False Assumptions:
1. The customer knows what they want
23. We want to Shift away from a Requirements Delivery Process…
False Assumptions:
1. The customer knows what they want
2. The developers know how to build it
24. We want to Shift away from a Requirements Delivery Process…
False Assumptions:
1. The customer knows what they want
2. The developers know how to build it
3. Nothing will change along the way
26. …To a Requirements Discovery Process
Reality:
1. The customer discovers what they want
2. The developers discover how to build it
3. Many things change along the way
41. Assume the team was working in value order, when would you release this product?
What would be the benefit of releasing early?
45%$
19%$
16%$
13%$
7%$
Never$
Rarely$
Some5mes$
O8en$
Always$
49. WORKING SOFTWARE ISYOUR PRIMARY MEASURE OF
PROGRESS
Requirements
Design
Development
Sprint 1
Test
Requirements
Design
Development
Sprint 2
Test
Requirements
Design
Development
Sprint 3
Test
Requirements
Design
Development
Sprint 4
Test
Potentially Shippable Product Increment
60. How we Normally Assign Work
Carter
Alex
James
Camryn
Janet
Will
61. How we Normally Assign Work
Project 1
Carter
Alex
James
Camryn
Janet
Will
62. How we Normally Assign Work
Project 1
Carter
Alex
James
Camryn
Janet
Will
63. How we Normally Assign Work
Project 1
Carter
Alex
James
Camryn
Janet
Will
64. How we Normally Assign Work
Project 1
Carter
Alex
James
Camryn
Janet
Will
65. How we Normally Assign Work
Project 1
Project 2
Carter
Alex
James
Camryn
Janet
Will
66. How we Normally Assign Work
Project 1
Project 2
Carter
Alex
James
Camryn
Janet
Will
67. How we Normally Assign Work
Project 1
Project 2
Project 3
Carter
Alex
James
Camryn
Janet
Will
68. How we Normally Assign Work
Project 1
Project 2
Project 3
Carter
Alex
James
Camryn
Janet
Will
69. How we Normally Assign Work
Project 1
Project 2
Project 3
Everything is a High Priority.
How does Alex decide what to work on First?
Carter
Alex
James
Camryn
Janet
Will
70. How we should prioritize work in Agile
Carter
Alex
James
Camryn
Janet
Will
71. How we should prioritize work in Agile
Carter
Alex
James
Camryn
Janet
Will
Agile Team
Prioritized
Team Backlog
72. How we should prioritize work in Agile
Project 1
Carter
Alex
James
Camryn
Janet
Will
Agile Team
Prioritized
Team Backlog
73. How we should prioritize work in Agile
Project 1
Carter
Alex
James
Camryn
Janet
Will
Agile Team
Prioritized
Team Backlog
74. How we should prioritize work in Agile
Project 1
Project 2
Carter
Alex
James
Camryn
Janet
Will
Agile Team
Prioritized
Team Backlog
75. How we should prioritize work in Agile
Project 1
Project 2
Project 3
Carter
Alex
James
Camryn
Janet
Will
Agile Team
Prioritized
Team Backlog
76. David Hawks
Agile Velocity
Agile Coach
david@agilevelocity.com
Role
Name
Company
10 yrs
Email Address
If you would like to receive a White Paper
on the top 10 pitfalls of an Agile Transformation
Please leave a card
Years of Agile Exp