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

Story | Glossary

Definition

User Stories (or stories) in Agile form the building blocks of Software Development. It is a simple description of a feature, that’s told from the perspective of the user of the system, aka the person who desires/requires the feature. The focus is overall to move away from writing about requirements, and instead talk about them. All User Stories are usually 1-2 written sentences in form.

Further Reading

  • User Stories Applied: For Agile Software Development” (book), by Mike Cohn