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.

7.1 Which minimum are we talking about?

During your career, you have probably heard about at least a few different minimums, such as

7.2 Preparing for the MVP

7.3 Building out the /files APIs

7.3.1 Testing the API

7.4 ACH batches APIs

7.4.1 Adding the /files/id/batches API

7.4.2 Supporting ACH batches in the dashboard

7.4.3 Uploading files

7.5 Putting the puzzle together

7.5.1 Cleaning up the configuration files

7.5.2 Ensuring APIs are accessible

7.5.3 Programming challenges

7.5.4 Exploring the dashboard

7.6 Gotta have more files

7.7 Adding a basic login page

7.8 Adding TLS to our dashboard