Fragile | Glossary

Definition

In the last few decades, Agile has become the most prominent  approach for modern day Product Development. However, it’s core values are often misrepresented and abused. This is such a commonplace practice, that there is an official name for it aka ‘Fragile’ (or frAgile). It’s meant as a warning shot for developers to handle their software product with care, else it’s crash and burn and cause detrimental impact to the entire team.

Elements like Technical Debt, and teams consistently carrying over their work on to the next sprint, Product Manager/ Leader who is quitting, or any miscommunications with customers etc. makes a Software product ‘Fragile’, and must be avoided at all costs.

Further Reading

  •  “Agile Project Management”(book), by James Shore.

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