Gap Analysis | Glossary

Definition

Gap Analysis is used to assess and identify gaps in the process of an organization. It results in a strength and weaknesses report, and an initial set of recommendations that can eventually help the organizations improve their process and meet their goals.

Executing a Gap Analysis is important for any organization because it facilitates the most effective measures, based on the priorities set. The procedure involves collecting documentation of the organization’s products, and interviewing people involved in those processes( in groups or individually) to identify gaps.

Further Reading

  •  “Integrating CMMI and Agile Development: Case Studies and Proven Techniques for Faster Performance Improvement” (book), by Paul E. McMahon.

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.