FinTech API: Mandatory Regulatory Scope Expansion Mid-Project

Simone’s approach

What is not fully clarified in the scenario above is whether this new regulatory requirement must be included in the current delivery timeline. In most cases, regulators provide a grace period for implementation, which is often longer than the proposed 8-week delivery window.

The next step would be to understand whether this new requirement is aligned with the API initiative currently being developed or if it is an unrelated enhancement. If it is unrelated, I would prioritize delivering the API on time and position the regulatory functionality as the next item on the roadmap.

If the requirement is related and can be integrated into the planned API with minimal effort and without impacting timelines, then it makes sense to include it in the current scope. However, if adding it risks delaying delivery, then this becomes a classic technology trade-off and prioritization exercise.

In that case, I would revisit the scope and identify which lower-priority features could be deferred in favor of meeting the regulatory requirement within the 8-week timeframe. The outcome would likely be a revised MVP: fewer planned functionalities, but one that remains compliant and delivers the most critical customer value.

This is where customer feedback becomes essential. Customers should help determine what is truly mission-critical when scope creep occurs. It is also important to communicate transparently that delivering every requested feature within the same timeline is unrealistic, and that trade-offs are necessary to balance compliance, customer value, and delivery commitments.

Ishant Juyal’s approach

First, a clarifying question: Is this deadline tied to the critical launch from the bank partner's side? Is there a campaign with the main partner where being late could jeopardize the partnership? I want to understand the context of the timeline, which is eight weeks. As the PM, I already know the final output or aim you want to achieve, but I’ll break it down to the single most important outcome that must happen from this critical API integration launch.

My approach:

1. Understand this new non-negotiable financial reporting regulation and how it affects the functionality and scope of our current project.
2. If our project already aligns with most requirements, adjust the remaining effort in the timeline. If a minor deviation extension is possible, I’ll try to accommodate that.
3. If the change is large and everything needs to change, I’ll revisit the scoping document and minimize the scope while preserving the achievable outcomes.
4. If there are parts of the requirements that are low priority, remove them and still deliver the desired output while complying with the regulation.

In short: modify the scope according to the requirement.