1.

In the first part of the meeting, the main issues related to the FLASH app from 2018 to 2023 has
discussed with the vendor such as unavailability of the FLASH app more than 48 hours ,
functional breakdown when releasing a new feature/release most of the time, Quality issues in
the application side, no proper control releases/versions etc.

2. Vendor explained how the instability UAT environment is affect to their releases and requested
a stable UAT environment, which similar to the LIVE environment in order to avoid such kind of
delays and testing issues.

Action plan : Bank requested vendor to inform if there are any test environment issues right away and
bank takes the necessary action to resolve it without further delays.

Further Lasantha suggested to take the necessary action from bank side to assemble a stable UAT
environment as long-term plan.

3. Vendor explained the card related services are not working which integrated to the FLASH app,
sometimes but the bank side confirm that same card related services use by the FDA is working
without issue unless a common platform(Euro net) issue.

Action plan: Bank requested the vendor to recheck the card related integrated service in the FLASH, and
if there are any issues/clarifications bank is willing to help.

4. Vendor explained about the FLASH versions they have so far, 1.0 is the first released version and
1.2 is the current version of the FLASH in the markets. Further version 4.3 will be a new release
of FLASH including many features/Improvements such as widgets in the dashboard..etc)

Action plan : Bank requested vendor to share the 4.3 version feature/requirement documents and the
release plan.

5. Bank explained they need a visibility of the vendor code in order to confirm whether the same
develop version is release to the live environment.

Action plan : Vendor requested a development environment from the bank side so the bank can
access/check the code if needed. The Bank has agreed to do the needful to establish a dev environment
for the FLASH vendor.

Further bank explain all the live deploy should go through the server team and vendor has to share the
relevant information regarding the release, if needed the vendor has to be in the line until the live
deploy is completed.

Further Bank explain that the vendor release note which receiving from the FLASH vendor doesn’t
include most of the importance details such as new feature, fix for a defects, known issues…etc.

Action plan: Bank agreed to share a format of a release note to the vendor and without the complete
release note, bank won’t be accept the any vendor release.

6. Bank explained there are some issues in the vendor projects delivery process, how it’s
communicate with the business units.
Action plan : Vendor agreed to share the each 2 weeks(sprints) delivery plan with the bank and the
priority project order which business unit request and the development pre requites which they need
from bank side in advance to achieve the delivery target date as planned.

Further bank requested to share a proper CRS/BRD with the bank BA and the business unit before
starting the development and the same document should share with the bank QA team when releasing
a project for the testing.

7. Vender explained they are using both old and new SOAP services and question about if there are
any support issue to the old SOAP services with the micro services. The bank explained that
there are no immediate impact to the existing app but need to come up with the plan.

Action plan : Need to schedule a meeting for further discussions and until that the vendor agreed to
continue the development which doesn’t have direct impact with the micro services.

8. Bank explained the shared road map for the FLASH App need to include the feature list with the
target release plan.

Action plan : Vendor has agreed to share the updated road map with the requested details.