How to Run Fit-Gap in Canias ERP

Fit-gap is not a slide title; it shapes project outcomes. If standard vs gap, acceptance criteria, and cost/schedule impact are not clear, the project drifts later. This guide summarizes the fit-gap logic and what to watch on the Canias side.

Within the Canias cluster

This guide is strongest when read as part of the wider Canias track: landing, steering, fit-gap, and go-live together form a clearer decision framework.

Table of contents

Standard, gap, development, process change

Standard: the need is covered by the product. Gap: not covered; response may be configuration, customization, or process change. Decisions must be written.

  • Fit: business need covered by standard.
  • Gap: not covered; options must be compared.
  • Customization raises cost and maintenance; prefer standard where reasonable.
  • Process change is sometimes the healthiest option.

Link to acceptance criteria

Each gap needs clear acceptance criteria; when delivery is accepted must be written.

  • Gap decision is tied to acceptance criteria.
  • Vague criteria lead to disputes later.

What to watch on the Canias side

Module scope, TROIA needs, integration points, and the data model all affect gaps.

  • Module and license scope explicit.
  • TROIA development cost evaluated separately.
  • Integration points on the gap list.

Common mistakes

Not writing gaps; not showing cost/schedule impact; leaving decisions verbal.

  • Gap list vague or incomplete.
  • Cost/schedule impact not reported.
  • No decision record.

Related pages:

FAQ

When should fit-gap run?
Early, while scope is forming—so cost and schedule impact surface in time.
Who decides on a gap?
The sponsor or delegated authority; all options and impacts should be presented.

Related pages

Related posts will be listed here.

How to Run Fit-Gap | Canias ERP | Fatih Görgülü