7 Our minimum viable product
This chapter covers
- The purpose of minimum viable product (MVP)
- Putting everything together into an MVP
- Security concerns
- Testing with Playwright
Over the previous sprints, we worked on spike stories examining our project’s various components. You were introduced to generative AI and different tools that can expedite software development. We also reviewed specific technologies, such as Python/FastAPI, Postgres, Docker, and Next.js. Now, the line of business would like to see the fruit of our labor. This chapter focuses on putting everything together into a minimum viable product (MVP), which allows a user to
- Upload an ACH file
- Parse an ACH file and store it in the database
- Visualize the results in our dashboard
The functionality will not expand significantly from what was developed in the previous sprints. Instead, we want to ensure those individual components are now integrated seamlessly. Along the way, we will explore what happens in the system demo and validate our MVP using Playwright. Having the MVP will allow us to release something to our customers and gather feedback, which we’ll use to enhance our project in the coming chapters.