technical debt in scrum

Now the software development is everywhere agile, everyone speaks only fast not broken era, who has time to think about code quality, design quality? Which one doesn't kill crowd from a bunch of code to implement another feature? A product can not survive a few years, why consider what maintainability?When we pursue progress, we always sacrifice something or destroy something and wait for it to be mended. This is technical

English Original: Technical debt:a Repayment Plan　　What is technical debt?Many teams are plagued by technical debt, but few teams can really design a plan to break free from it. In order to better understand how to get rid of debt

A fairy Tale A long time ago, a software development team found their manager. "Our project has quite a bit of technical debt (technical debt) and we should do something about it." "The team said. They showed a picture (Figure 1) to illustrate the technical

The word "debt", I believe that we have been deeply aware of it, especially like me as a "house slave" people, every month to go to the bank to pay money, that is debt ah. In the process of software development, we tend to borrow, people call it technical debt, in fact, in order to quickly solve the problem, and the ad

Technical debt is widely regarded as a bad thing and it should be avoided or repaid as soon as possible. Is that what you should do? We don't think so. First, we compare the technical debt with the financial debt, and expound its similarity with the strategic Design (strate

Original article: http://www.infoq.com/cn/news/2009/10/dissecting-technical-debt The term "technical debt" is developed by Ward cunnheimFor the first time, it indicates that the development team selects an easy-to-implement solution from the perspective of short-term effects during design or architecture selection. How

We have had the deadline coming and the time is very tight. At that time, we must fix the bug as soon as possible, but one of the bug is particularly tough, let us make every effort also helpless! Then, one of my colleagues took over the debugging work. He was forced to write values that should be retrieved from the database-they would not change during the first few months of the system's operation-and then ... The system magically works! For this kind of "inexplicable code", my colleague call

Technical debt in Sonar The computing of technical debt in sonar is based on SQALE (Software Quality Assessment based on Lifecycle Expectations, based on the Software Quality Assessment expected by the Life Cycle) methodology. SQALE methodology was developed by in‑it and later open-source. If you have read the relevant

A friend of my technical blog may have noticed that a series of articles related to CEF, PPAPI and Skia have recently been updated. In the process of studying them, there are some interesting experiences, very typical, can explain the origin of " technical debt " from one aspect.Next I will talk about this experience, and then start to see the reasons for the for

was incurring some "technical debt" that must be repaid lat Er. means going back and making the "repayment" in the the the "the" and "would" Ces to doing it right the first time.So, the concern over making changes properly now versus later? It's because there ' s a hidden cost to making these quick and dirty fixes. For financial debts The hidden cost was called "interest," and most anyone with a credit car

The calculation of technical debt in sonar is based on the methodology of Sqale (Software Quality assessment based on lifecycle expectations, software quality assessment based on life cycle expectations). Sqale methodology was developed by Inspearit, which was later open source. If you read the relevant documentation on the sqale.org, you will see that it is about "organization-related non-functional line r

Technical debt refers to the rush to implement a function, but damage the existing library (the design of the code library is contaminated in the implementation process ), for some project managers/customers, this is like a rare talk. Maybe they understand, but they don't want to admit it. I guess so. In any case, I think of a small story. When this happens next time, I need to explain to them the cost of a

Technical debt is a rush to achieve a function, but the existing library has been destroyed (in the process of implementation of the code to pollute the design of the library), which for some project managers/customers like a heavenly book yarn. Maybe they understand, just don't want to admit it, I guess so. Anyway, I came up with a little story, and when it happens next time, I need to explain to them the

Technical debt refers to the damage to the code library due to the rush to implement certain functional features in the face of requirements (in this process, the architecture design of the code library is also damaged ). For some managers or customers, technical debt seems a strange concept. Maybe they know, but they

factors also on the results haveVery big impact. However, as programmers grow in maturity, TDD is able to help programmers find more problems before they are delivered to QA, or to stifle defects in TDDRing process.AnywayTypically, the project itself is developed much less than its long-term operational use time, and changes in demand as the business grows, as programmers become more adept at using TDDand team agility maturity, which can be earned by reducing the time of defect modification and