The document is a presentation deck about technical debt that covers:
- What technical debt is and how it occurs through bad design decisions or quick development approaches that sacrifice quality
- How to identify technical debt through indicators like comments mentioning certain developers' code or difficulties with setup, deployment, or testing
- Sources of technical debt like time pressure, maintenance neglect, or using outdated libraries
- Why technical debt should be addressed to avoid issues like an uncontrollable codebase and development risks
- How to manage technical debt through practices like refactoring, continuous integration, and prioritizing technical debt in estimations
17. External qualities.
● External qualities can be related to features.
● External qualities deliver business values
● External qualities can be sponsored
Stakeholder
18. Internal qualities.
● Internal qualities does not relates to features.
● External qualities does not deliver business values
Stakeholder
19. Learning of the millennium
Although messy code or code
without tests works perfectly for
customers if it delivers the desired
business value.
28. Ward Cunningham used the metaphor ‘Technical Debt’ for the first time in 1992 to communicate this problem with non-technical
stakeholders.
29.
30.
31. “Code with low quality and no automatic test coverage can be compared
with financial debt.”
● Principal: The cost of refactoring the codebase to a clean design,
which allows easy future changes.
● Interest : Extra costs, which have to be paid in the future if the team
has to work with a messy codebase.
31
32. To explain non-technical stakeholders in the financial term
To communicate the problem of poor quality that might otherwise go unnoticed
until it is too late
A sufficient amount of messy code may bring a whole engineering department
to a stand-still.
Technical Debt metaphor is good for
33. ● Why should business sponsor spend money on the
features that don’t deliver business value?
34. ● Why should business sponsor spend money on the
features that don’t deliver business value?
● Why should the business sponsors accept a project of
higher cost?
37. Indicators
“This is Karl’s Code. Don’t touch it” “I think last added feature, introduced the new
bug, I am dealing”
“I wrote this last week, Let’s copy that code” “Does anyone know, how to setup workspace”
“Deployment takes more than 2 hours. Just
wait for next Monday”
“TODO/FIXME: This should be fixed before next
release”
“This library is outdated. We don’t have time
to upgrade now”
“I am pretty sure, If I touch it will break
somewhere else”
“Lets finish the testing by next release” “Does anyone knows where we store the
password?”
43. Teams with plenty of time also makes
Technical Debt.
Realization is at the end.
It’s too late!!!
Martin Fowler
"Now we know how we should have done it"?
47. Technical debt is a strategy.
Quickly reach to the business goal and
to the market, and see if the
functionality is useful at all.
Ward Cunningham
48. Spotify see a perfect code as a waste,
if we don't know the functionality we
create is really really useful.
Spotify come up with a functionality
very quickly to the user and they
refactor to make it nice.
Spotify Engineering
49. Eric Evans(Domain Driven Design)
You cannot have same quality
throughout the system
There will be always Technical Debt
Less important implementation may
not need any refactoring
50. Eric Ries(Lean Startup)
“I was always happy to write perfect
code but at the end no one used it.”
Build quickly and bring in front of user.
51. 51
Technical Debt is really Bad???
Yield of investment by entering into the market is very big than the
principal and interest amount.
Technical Debt might give an advantage of an early release and profit
the organization more than it costs to pay back the debt.
Amazon was a behemoth application once upon a time.
Twitter was built on Ruby on Rails, now it’s all messaging queues.
58. ● Buffer Task : 10% of the available time.
● Quality Releases: Technical release focused on quality improvements.
● Cost: Include cost for Technical debt in requirement estimations.
● Prioritization:
○ Technical Debt Backlog
○ Technical Debt Items
Fix development process
61. ● Developer knows quality issues.
● They have to work on
○ Getting Domain Knowledge.
○ Sell Technical Debt to business decision makers.
Developers... “Build the Trust.”
64. Summary
● Technical debt is a metaphor that describes a very real
phenomenon.
● Technical debt comes in variety of the forms.
● Lower maintenance cost
○ Avoiding interest payments.
● Increase productivity
○ Better prioritization
● Avoid Surprises
○ Fewer failures
○ Better estimation
65. June 1, 2014
Standard presentation deck version
45 Main St #220 BKLN / 718 625 4843 / hugeinc.com
66. Ad Age A-List:
4 times in the last 5 years.
Most Innovative:
According to Digiday & Mashable.
67. 4 times in the last 5 years.
Ad Age A-List
As voted by our peers in the UK’s Drum Digital Census.
2013 Elite Agency
Named by Haymarket Media’s ‘The Hub’
2014 Best Digital Agency
According to both Digiday and Mashable
Most Innovative Agency
Recognized for mobile by Ad Age.
3rd Largest Mobile Agency
68. 750 employees worldwide.
ATL
50 people.
BKLN
425 people.
DC
40 people.
LND
50 people.
LA
90 people.
PDX
15 people.
RIO
45 people.
SF
35 people.
Our offices.
69. Research & analytics.
Focus groups & surveys
Ethnography & usability studies
Social listening & trends spotting
Website, social & campaign analytics
Strategy & planning.
Brand planning & marketing
Product strategy & business consulting
Communications planning
Search strategy (SEO, SEM)
Discipline specialists
(e.g., CRM, mobile)
User Experience.
Content strategy
Information architecture
Interaction design
Mobile experience
Creative.
Visual Design
Copywriting & editorial
Campaign development
Mobile, emerging & in-store digital
Technology.
Ecommerce
Technical leadership/architecture
User interface development
Mobile & emerging platforms
Social platforms
Rapid & enterprise development
Quality assurance & deployment
Social engagement.
Content strategy
Information architecture
Interaction design
Mobile experience
Studio.
Photography
Motion
Video creation & production
Animation & illustration
Production
Media.
Media planning
Media buying
Campaign management,
optimization & analysis
Media partnership development
Program Management.
Project management
Planning & roadmap development
Resource management
Risk mitigation
70. Discover
Stakeholder interviews
Consumer research &
insights
Brand & content audit
Competitive & market
Landscape analysis
Platform & technology
assessment
Plan
Goal prioritization
User personas & journeys
Creative brief
Communications strategy
Roadmap
Asset matrix
Measurement plan
Create & iterate
Creative concepts
Campaign architecture
Wireframes
Digital experience design
Prototyping & user testing
Implement
Creative assets
Style guidelines
Functional specs &
annotations
Development & infrastructure
setup
Testing & analytics
Implementation
Deployment management
Measure & evolve
Tracking analysis
Media optimization
Measurement of success
Future enhancements
Plan & research
Our process.
85. Strategy
.Lorem ipsum dolor sit amet, consectetur
adipiscing elit.
Unmet user need.
Lorem ipsum dolor sit amet,
consectetur adipiscing elit.
Real marketing challenge. Lorem
ipsum dolor sit amet, consectetur
adipiscing elit.
True brand capability.
Lorem ipsum dolor sit amet,
consectetur adipiscing elit.
88. If a thought needs more clarification, use
an extra sentence or two.
88
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur
consectetur elit a nulla egestas, quis ullamcorper mi suscipit. Donec
convallis tortor a iaculis lacinia.
90. A simple list with on state:
1. Relevant.
2. Findable.
3. Portable.
4. Huggable.
5. Reusable.
91. 91
This is your team.
Ice Cube – Managing Director
MC Ren – Director Content Strategy
Eazy E – VP Strategy
DJ Yella – Director User Experience
Arabian Prince – Creative Director
Dr. Dre – VP Technology
92. 92
This is a common slide.
Lipsum dolor sit amet, consectetur adipiscing elit. Curabitur
consectetur elit a nulla egestas, quis ullamcorper mi suscipit. Donec
convallis tortor a iaculis lacinia. Maecenas quis massa tortor. Duis
pretium rutrum tellus, ac fringilla metus. Nulla facilisi. Morbi ut blandit
lectus. Morbi mattis vehicula nisi sit amet rhoncus. Nulla auctor magna
vel aliquet hendrerit. Curabitur semper sollicitudin magna vel dictum.
• Then it could be followed up by a few points.
• That are even bulleted for fun.
• Also for pulling out great contextual points.
96. If a thought needs more clarification, use
an extra sentence or two.
96
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur
consectetur elit a nulla egestas, quis ullamcorper mi suscipit. Donec
convallis tortor a iaculis lacinia.
101. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur consectetur elit
a nulla egestas, quis ullamcorper mi suscipit. Donec convallis tortor a iaculis
lacinia.
If a thought needs more clarification, use
an extra sentence or two.
101
107. 150%Increase in monthly Facebook
virality.
120%Increase in monthly
Facebook virality.
216%Increase in monthly
Facebook virality.
Results
108. This is a table with rows.
Objective KPI Features
Laugh a lot and then get
drunk.
Hiccups • Something here
• Something here
Run around in the sprinkler. Speed • Something here
• Something here
Shoot each other with water
guns
Load time • Something here
• Something here
Make new friends Friend requests on Facebook • Something here
109. Objective KPI Features
Laugh a lot and then get
drunk.
Hiccups • Something here
• Something here
Run around in the sprinkler. Speed • Something here
• Something here
Shoot each other with water
guns
Load time • Something here
• Something here
Make new friends Friend requests on Facebook • Something here
Ladidah Falala • Here you go
127. A couple photos and copy.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur
consectetur elit a nulla egestas, quis ullamcorper mi suscipit. Donec
convallis tortor a iaculis lacinia. Maecenas quis massa tortor. Duis
pretium rutrum tellus, ac fringilla metus. Nulla facilisi. consectetur
adipiscing elit. Curabitur consectetur elit a nulla egestas, quis
ullamcorper mi suscipit. Donec convalli.
• This guy has done this.
• And also he did something else
• And there was another time that he did this really cool thing.
128. This is your team.
Ice Cube – Managing Director
MC Ren – Director Content Strategy
Eazy E – VP Strategy
DJ Yella – Director User Experience
Arabian Prince – Creative Director
Dr. Dre – VP Technology
129. Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Curabitur consectetur elit a nulla
egestas, quis ullamcorper mi suscipit. Donec
convallis tortor a iaculis lacinia. Maecenas quis
massa tortor. Duis pretium rutrum tellus, ac
fringilla metus. Nulla facilisi.
• She has done this
• And also she did something else
• And there was another time that she did this
really cool thing
A persona.
130. Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Curabitur consectetur elit a nulla
egestas, quis ullamcorper mi suscipit. Donec
convallis tortor a iaculis lacinia. Maecenas quis
massa tortor. Duis pretium rutrum tellus, ac
fringilla metus. Nulla facilisi.
• This page is good for this
• And a feature is this
• We could also talk about some other
features here
The home page.
132. June 1, 2014
Standard presentation deck version
45 Main St #220 BKLN / 718 625 4843 / hugeinc.com
133. 133
Make your copy work harder.
• Use concise language. The template works best with short text.
• Headlines should make a point; not just describe the page content.
• We use sentence case, not title case.
• Use punctuation & ampersands: they look cool.
• We only use 2 fonts. Huge AVG Bold & Copernicus. Character
spacing should be tight for AVG and normal for Copernicus.
• Do not change the type size in the text boxes.
134. 134
Make it beautiful.
• Less is better: white space, simplicity, and clean imagery rule.
• Mix up the background color to avoid deck fatigue.
• Use the .jpg art templates to place art.
• Don’t change the device art – place screens within the devices.
• Make sure styles do not change with copy & paste.
• We work at a design agency; if you think your deck is not as
beautiful as it should be ask a designer for help.
136. When there are too many icons drop the circle and keep it clean.
Social Icons
Twitter Facebook Pinterest Google + Linked-in Vine Instagram
Flickr Vimeo Skype Pay Pal Tumblr You Tube RSS
Stumble Upon Rdio Drop Box Cargo Collective Dribble Etsy Four Square