I know it may sound like I’m painting a rosy,Â infallibleÂ picture of Scrum. Â It’s the truth, though, and I feel like it solved most of my project problems. Â There is, however, one main problem I saw that made Scrum, and Iterative Development in general, fall flat on its face. Â It’s called Technical Debt, and it’s a problem with programming in general, not Scrum/Agile. Â When it rears its head in Scrum, the effects are devastating, and I believe one of the main reasons Scrum fails for a lot of people.
This article will discuss what Technical Debt is from a Flash/Flex developer perspective, how it negatively affects my Scrum projects, and what are some of the prescribed ways to prevent it. Â Nothing ground breaking here folks, justÂ corroborationÂ that TD IS a major problem, and not even Scrum is immune.