Modularization, testing and technical debt (in a large agile project)
Download as PPTX, PDF1 like520 views
This document discusses lessons learned from a large agile project at Computas for a customer consolidating multiple government agencies. It covers challenges with coupling and modularization, the need for robust testing environments with service level agreements, and managing technical debt in an agile process. Prioritizing technical debt remediation work is important to avoid issues with estimates, duplicate code, bugs and developer morale over time. Transparency into technical debt is key along with shared responsibility for remediation.
Modularization, testing and technical debt (in a large agile project)
- 1. © Computas AS 04.06.2010Modularization, testing and technical debtin a large agile projectMorten Forfang, Harald Søvik{mfo, hso} @ computas.com
- 2. SpeakersMorten ForfangArchitect, Ph.D.mfo@computas.comHarald SøvikTech Lead, M.Sc.hso@computas.com2© Computas AS 04.06.2010
- 3. 3© Computas AS 04.06.2010Computaswork support systems (bpm)knowledgemanagementconsultancy servicescustom software solutions180 employees w/ M.Sc. or Ph.D.100% owned by employees
- 4. 4© Computas AS 04.06.2010The customerMattilsynetNorwegianFood Safety Authorityconsolidationof 4 gov. bodies1300 employees
- 5. 5© Computas AS 04.06.2010The projectchallengescreated by mergermodel business processesconsolidate 40 legacy systemsreducenumberoftech. platformsreduce data duplication
- 6. Mats !6© Computas AS 04.06.2010
- 7. 7© Computas AS 04.06.2010Scrumishwaterfall ~> iterative4 teams á 5 devssprintbacklogburndownretrospective
- 8. 8© Computas AS 04.06.2010Somelessionslearnedcoupling and modularizationtesting environmentstechnicaldebt
- 9. 9© Computas AS 04.06.2010Subject 1Coupling and modularization
- 10. 10© Computas AS 04.06.2010Coupling and modularization
- 11. 11© Computas AS 04.06.2010Coupling and modularizationMy codeMaven2IDEAFrameSolutionWebServerClientAppServer
- 12. 12© Computas AS 04.06.2010LessionslearnedAbstractions 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. 13© Computas AS 04.06.2010Subject 2Testing environments
- 14. 14© Computas AS 04.06.2010Testing environmentsclient / terminalweb serverws front endePhorteapp serverintegration serverAgresso…
- 15. 15© Computas AS 04.06.2010Testing environmentsenvironment 1 build server aenvironment 2environment 3environment 4build server benvironment 5environment 6
- 16. 16© Computas AS 04.06.2010Testing environments2 x 3 environmentsStaging levelsAvailability and stabilityMonitoringand SLAAutomated build and deploymentStaticcodeanalysis
- 17. 17© Computas AS 04.06.2010LessonslearnedTreat your testing environment like a small production environment. Define a Service Level Agreement for your domain experts and testers. Automate everything.
- 18. 18© Computas AS 04.06.2010Subject 3Scrum and technicaldebt
- 19. 19© Computas AS 04.06.2010Prioritynewfunctionalityvs.technicaldebt
- 20. 20© Computas AS 04.06.2010Scrum, you say ?ProductownerProject managerTest managerSolutionarchitectScrum masterDeveloper
- 21. 21© Computas AS 04.06.2010In thebacklog ..EasilydefineableuserstoriespriorityestimatevalueTechnical stuffnew or changed= Business stuff
- 22. 22© Computas AS 04.06.2010Outsidethebacklog (1)SmallthingsUseradministrationDevelopmentplatformMerging and conflictsScripts, tools and utils..
- 23. 23© Computas AS 04.06.2010Outsidethebacklog (2)Quick, dirtysolutionsintegrationdomainmodelinitcodepluginsframework
- 24. 24© Computas AS 04.06.2010Outsidethebacklog (3)Lots of codeproprietary patternsnew patterns retroactive decisionsTestsdidn’t write it firstoverdueno time
- 25. 25© Computas AS 04.06.2010Technical debt punch lines Bad time ..In the middle of ..Very important ..Unsure of the cost ..Unsure of the consequence ..Not my problem ..
- 26. 26© Computas AS 04.06.2010ConsequencesInexpectabilitywrong estimatesNo reuseDuplicate codeBugs and defectsUnhappy developers
- 27. 27© Computas AS 04.06.2010Nowwhat ?transparencyeasy to tell ..responsibilitynopunishmentpriorizationright person
- 28. 28© Computas AS 04.06.2010LessionslearnedDo 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. 29© Computas AS 04.06.2010Summarycoupling and modularizationtesting environmentstechnicaldebt
- 30. Questions ?Morten ForfangWeb Architect, Ph.D.mfo@computas.comHarald SøvikTech Lead, M.Sc.hso@computas.com30© Computas AS 04.06.2010jobopenings for experienceddevelopers !www.computas.com