Skip to content
Tutorials Center
My learning

Topics

Lesson 21 of 36 ยท Implementation and Change

Requirements and Fit-Gap Analysis

Learn how to gather requirements, classify each as fit, configuration, extension or gap, and decide how to close gaps, with a Python fit-gap tracker you can run.

A package system never matches a company's processes perfectly. Fit-gap analysis is the structured comparison between what the business needs (requirements) and what the standard software already does (fit). Every difference is a gap that needs a decision. Done well, this analysis keeps customization small, budgets honest and upgrades painless.

This lesson shows how to write good requirements, classify them and decide what to do about gaps. The ERP or CRM product is not available on the site, so the examples use a Python tracker to organize the analysis.

Writing useful requirements

A requirement describes a business need, not a screen. Compare:

  • Weak: "The system must have a dropdown for payment terms."
  • Better: "Sales users must select payment terms on a quotation, and the terms must flow to the invoice and to the due-date calculation."

Good requirements are specific, testable, prioritized and traceable to a business process. Collect them in workshops organized by process (such as order to cash and procure to pay, see the Business Processes chapter of the track), by interviewing process owners and by observing real work. Distinguish needs from wishes: use a priority scheme such as MoSCoW (Must, Should, Could, Won't now).

Field Example
ID REQ-042
Process Order to cash
Statement The credit limit of a customer is checked when a sales order is saved
Priority Must
Owner Head of credit control
Acceptance test Order above the limit is blocked and routed for approval

The fit-gap categories

Each requirement is compared with the product's standard capability and placed in a category:

Standard coverage

Fit Works out of the box.
Configuration Works after settings, no code.

Cheap, supported and upgrade-safe.

1 / 3
  • Fit: the standard function does it.
  • Configuration: it works after setting parameters, creating fields, workflows or rules.
  • Extension: it needs a low-code app, a script, or a side-by-side extension that lives outside the core system.
  • Custom development: new code inside the product. Most expensive to maintain.
  • Third-party product: a certified add-on from a partner.
  • Process change: the company adapts to the standard.
  • Drop: the requirement is not funded.

The golden rule: keep the core clean

Every customization must be designed, tested, documented, migrated at upgrades and supported. Studies and consultants' experience differ on exact numbers, but the pattern is stable: a small number of customizations drive a large share of long-term cost. Ask three questions of every gap:

  1. Is the process unique and a source of competitive advantage? If not, adopt the standard.
  2. Can the need be met by configuration or an extension that does not touch the core?
  3. What is the cost of ownership over five years, not just build cost?
Python A fit-gap tracker (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice the last report. A Must that needs custom code deserves extra scrutiny: is the requirement real, and is there a standard alternative?

Scoring gaps

When many gaps compete for a limited budget, rank them by value and cost. A simple score is business value divided by estimated cost over its lifetime. The stand-in below ranks a list and applies a budget.

Python Rank gaps by value for money

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The method is crude, but it forces a conversation: the label layout scores poorly and the team can say "no" with data.

Documenting decisions

Keep a gap register with the requirement, the options considered, the decision, the owner and the reason. When a new manager asks "why did we customize this?" the answer is on record. Revisit the register at every phase gate (see the implementation lifecycle).

Common mistakes

  • Writing requirements as solutions ("add a button") instead of needs.
  • Letting departments copy their old system's behaviour into the new one.
  • Counting only build cost, not support and upgrade cost.
  • Classifying everything as "fit" to please the vendor, then discovering gaps in testing.
  • Missing non-functional requirements such as volumes, response time, audit and data retention.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a fit-gap analysis compare?

    Each requirement is checked against standard functionality; the differences are the gaps that need decisions.
  2. 2. Which resolution of a gap is usually the cheapest over the long term?

    Adopting the standard avoids build, support and upgrade cost entirely.
  3. 3. Which is a well-formed requirement?

    It is specific, testable and states a business need rather than a screen.
  4. 4. What is a side-by-side extension?

    Keeping extensions outside the core makes upgrades safer.

Summary

  • Requirements describe needs in a testable way and carry a priority.
  • Each requirement becomes fit, configuration, extension, custom, third party, process change or drop.
  • Prefer standard and configuration; justify every custom item over five years of cost.
  • A gap register records decisions and reasons.
  • Rank gaps by value for money, and be ready to say no.

Next: Change Management and Training