Embed Size (px)
DESCRIPTION
Features often get delivered quickly on new software projects and slow to an exponentially slower pace over time. Teams are usually on their own to discover, implement, and even get buy-in for improving the technical capability to deliver. In this session we'll discuss how technical debt accrues and impacts the flow of features over time as well as how Product Owners can encourage and support teams to improve. We will run a simulation of a software project that demonstrates the impact of employing technical practices and addressing other technical debt.
Citation preview
As you come in, find someone in the room and discuss what
you know about Technical Debt
HOW TO KEEP YOUR PRODUCT DEVELOPMENT TEAMS GOING FAST
Product Camp Austin 11
We’d prefer a fast, steady stream of new features…
But sometimes it feels more like this
Long Delivery Times
Mounting Defects
Rising Development Costs
Poor Customer Responsiveness
Late Deliveries
Frustrated and Poor Performing Teams
Intentional Debt
Temporary
Code
Business Pressure
Delayed Testing
Other Conscio
us Tradeoff
s
Unintentional Debt
Poor Code or Design
Business PressurePoor Practices
Inflexible Software
Lack of understanding
Poor design/architectur
e
Unintended
Complexity
Poor design
A Vicious Cycle
Time Pressure
Poorly Implemen
ted Features
Late Delivery
Continuous Integration
Test (and other) Automation
Refactoring - would you trust delivery of your products over
this road?
Peer Review
http://jimhighsmith.com/the-financial-implications-of-technical-debt/
Jim Highsmith’s Technical Debt Graph
Rewrite!
Let’s do an exercise to understand the concept further.
Form into Teams of at least 4 people.
FeatureCost: 15
FeatureCost: 10
FeatureCost: 5
Technical DebtCost 15
Impact -10
Technical DebtCost 15
Impact -10
Technical DebtCost 10
Impact -5
Technical DebtCost 5
Impact -5
Technical DebtCost 5
Impact -5
Iteration Card
Setup your board as follows
FeatureCost: 15
FeatureCost: 10
FeatureCost: 5
Technical DebtCost 15
Impact -10
Technical DebtCost 15
Impact -10
Technical DebtCost 10
Impact -5
Technical DebtCost 5
Impact -5
Technical DebtCost 5
Impact -5
Iteration Card
Add up the total impact of all technical debt items
-35
-35
25
X
FeatureCost: 10
FeatureCost: 15
FeatureCost: 10
Technical DebtCost 15
Impact -10
Technical DebtCost 15
Impact -10
Technical DebtCost 10
Impact -5
Technical DebtCost 5
Impact -5
Technical DebtCost 5
Impact -5
Iteration Card
You have 25 Points to SpendSelect the cards you want to spend your points on.
No partially done work.
FeatureCost: 5
FeatureCost: 5
-35
25
10
15
15
X
The goal is to complete as many feature points at the end
of 5 iterations.
Go!
The goal is to complete as many feature points at the end
of 5 iterations.
Stop!
Theoretical Capacity
Technical Debt
Productivity
Time
In order to go fast we need a focus on Craftsmanship
Capture your debt
Visualize and estimate
Need to invest time, team needs slack
Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
Discuss how you could apply theses concepts to help your
teams go fast.
