Modularization, testing and technical debt (in a large agile project)

© Computas AS 04.06.2010
Modularization, testing and technical debt
in a large agile project
Morten Forfang, Harald Søvik
{mfo, hso} @ computas.com

Speakers
Morten Forfang
Architect, Ph.D.
mfo@computas.com
Harald Søvik
Tech Lead, M.Sc.
hso@computas.com
2

3
Computas
work support systems (bpm)
knowledgemanagement
consultancy services
custom software solutions
180 employees w/ M.Sc. or Ph.D.
100% owned by employees

4
The customer
Mattilsynet
NorwegianFood Safety Authority
consolidationof 4 gov. bodies
1300 employees

5
The project
challengescreated by merger
model business processes
consolidate 40 legacy systems
reducenumberoftech. platforms
reduce data duplication

Mats !
6

7
Scrumish
waterfall ~> iterative
4 teams á 5 devs
sprint
backlog
burndown
retrospective

8
Somelessionslearned
coupling and modularization
testing environments
technicaldebt

9
Subject 1
Coupling and modularization

10

11
My code
Maven2
IDEA
FrameSolution
WebServer
Client
AppServer

12
Lessionslearned
Abstractions is not a substitute for decoupling and formally controlled module interfaces.
Abstraction and generalization should been driven by necessity and experience, not guesswork and intentions.

13
Subject 2
Testing environments

14
client / terminal
web server
ws front end
ePhorte
app server
integration server
Agresso
…

15
environment 1
build server a
environment 2
environment 3
environment 4
build server b
environment 5
environment 6

16
2 x 3 environments
Staging levels
Availability and stability
Monitoringand SLA
Automated build and deployment
Staticcodeanalysis

17
Lessonslearned
Treat your testing environment like a small production
environment.
Define a Service Level Agreement for your domain
experts and testers.
Automate everything.

18
Subject 3
Scrum and technicaldebt

19
Priority
newfunctionality
vs.
technicaldebt

20
Scrum, you say ?
Productowner
Project manager
Test manager
Solutionarchitect
Scrum master
Developer

21
In thebacklog ..
Easilydefineableuserstories
priority
estimate
value
Technical stuff
new or changed
= Business stuff

22
Outsidethebacklog (1)
Smallthings
Useradministration
Developmentplatform
Merging and conflicts
Scripts, tools and utils
..

23
Quick, dirtysolutions
integration
domainmodel
initcode
plugins
framework

24
Lots of code
proprietary patterns
new patterns
retroactive decisions
Tests
didn’t write it first
overdue
no time

25
Technical debt punch lines
Bad time ..
In the middle of ..
Very important ..
Unsure of the cost ..
Unsure of the consequence ..
Not my problem ..

26
Consequences
Inexpectability
wrong estimates
No reuse
Duplicate code
Bugs and defects
Unhappy developers

27
Nowwhat ?
transparency
easy to tell ..
responsibility
nopunishment
priorization
right person

28
Lessionslearned
Do not underestimate the accumulated overhead caused by small problems being ignored over a lengthy period of time.
Do not underestimate the seriousness of technical debt.

29
Summary
coupling and modularization
testing environments
technicaldebt

Questions ?
Morten Forfang
Web Architect, Ph.D.
mfo@computas.com
Harald Søvik
Tech Lead, M.Sc.
hso@computas.com
30
jobopenings for experienceddevelopers !
www.computas.com

Modularization, testing and technical debt (in a large agile project)

by Harald Soevik on Jun 16, 2010

Accessibility

Categories

Upload Details

Usage Rights

Statistics

Modularization, testing and technical debt (in a large agile project) — Presentation Transcript