Introduction
When implementing solutions, it's not uncommon to encounter requirements that go beyond our software's current configuration capabilities. These issues can arise at any project stage, including scoping, configuration, QA testing, and user acceptance testing. Following a clear process helps balance the needs of our customers with project timelines and outcomes.
Let's see how we can identify functionality gaps in the system and consider practical ways to address them.
Actions to take
1. Confirm and document requirements
Identify gaps: Carefully review customer requirements to identify functionality the system cannot currently support.
Document findings: Clearly record each identified gap for reference and decision making.
2. Explore solution options
Depending on the gap, consider the following approaches:
New feature development: If the requirement aligns with Affinity’s strategic roadmap, propose adding the feature. This will require consideration, approval and prioritisation by the product team based on customer impact and resource availability.
Customisation: If a new feature isn’t feasible, explore whether customisation can meet the requirement. Customisations can be scoped to meet needs that are critical to the customer but beyond standard configuration. Customer-specific customisations should remain the exception not the rule.
Manual process referral: For requirements that are infrequent, complex, or unique to a specific customer, recommend a manual process as an alternative.
By thoughtfully assessing and documenting each requirement, you can ensure that the proposed solutions align with the project scope and the customer's operational needs.