Author: Karan Negi

Naive Technical Debt | Glossary

Karan Negi Leave a comment

 

Definition

Technical Debt is the extra cost incurred during development period, when a short and quick solution is used, instead of a safer one that would take more time. Naive Technical Debt  occurs where a specific best practice is not followed due to junior level developers being unaware of the best design pattern, documentation or guidelines.

Further Reading

  • “Refactoring for Software Design Smells: Managing Technical Debt”(book), by Girish Suryanarayana.
  • For more on Known Technical Debt, read here,

Milestone | Glossary

Karan Negi Leave a comment

 

Definition

Milestones are used as indicators to track progress toward a specific goal or event. There are three types of SAFe milestones:

  • Program Increment (PI):  They’re used to help objectively evaluate progress towards the technical/business hypothesis. Occur on PI cadence.
  • Fixed-date: Do not occur on cadence. Used for factors that rely on external events, third-party deliverables, and external constraints.
  • Learning milestones: They’re used to help validate business opportunities and hypothesis.

Further Reading

For more on Milestone, read here and here.