Technical Debt | Glossary

Definition

Technical Debt represents that extra rework caused when a faster, seemingly-easier solution is chosen to accomplish a task, instead of a more reliable one that takes a long period of time. The carry over work accumulates as ‘debt’ and can cause problems for the development team in the long run. It is also referred to as Design Debt, and is commonly associated with extreme programming.

Further Reading

  •  “Refactoring for Software Design Smells: Managing Technical Debt”(book), by Mike Cohn

Kaikaku | Glossary

Definition

Despite Lean Software Development’s focus on incremental improvement, it also recognizes the importance of drastic, radical step in some instances. This is known as Kaikaku. It is a revolutionary change to an existing system. In Software Development terms, it leads to the upgrade of an application currently in use from a release level to the next release level. This means a big change for both the development team and the user community.

Origin

Is a Japanese word. Kaikaku stands for ‘Radical change’ in a business or organization. Which makes it the polar opposite of Kaizen, which stands for incremental growth.

Further Reading

  • “Kaikaku: The Power and Magic of Lean : a Study in Knowledge Transfer”(book), by Norman Bodek