Develop a product requirements document describing a feature or improvement that responds to a business problem of our choosing.

Introduction:

In the rapidly evolving financial technology landscape, there is a discernible gap in user experience and accessibility across diverse financial services. Existing standalone applications often fail to provide users with a seamless, integrated platform to manage their financial activities comprehensively. Users are compelled to navigate multiple applications for banking, investments, insurance, and payments, resulting in a fragmented and inefficient financial management experience.

Objective:

Kunye currently provides a financial technology application where users can perform specific cross-border financial transactions such as remittance and bill payments. We would like to integrate other financial services into our application to offer single-point access for users to seamlessly manage banking, investment, insurance, and payment services within a unified application.

A product requirements document covering:

1. Research into the issue, including internal stakeholder feedback, customer feedback, data and market research.
2. Any assumptions being made.
3. Intended outcomes, and the metrics that will be used to track that outcome.
4. Requirements documented as user stories, with specification on the requirements and implementation of each.
5. No designs are expected, but wireframes can be included.

Students will be supported by a team of two senior software developers throughout the project. We will be able to provide answers to questions such as:

• Current product understanding
• Industry-standard design tools and applications
• Any sort of branding or styling advice
• Input on choices, problems or anything else the students might encounter