The information in this Readme should give anyone enough information to understand how a buy using the MPT works, how someone can participate in the process, and how to replicate it and adapt it for their own purposes. However, we also included the Presentations we've put together as an additional resource. Please give any and all feedback you have through our "indefinite RFI", which we will never close. Thank you!

With the increase in the MPT from $3,500 to $10,000, various project teams throughout the Government can build a community of private sector partners that can assist them on a per sprint basis, completing work associated with individual and unique user stories. This includes help developing and testing application programming interfaces (APIs), building out existing applications, creating documentation, and developing standards and policies.

Additionally, the minimum requirement that participating contractors register with SAM.gov, the government benefits from expanding the SAM.gov network while also encouraging non-traditional government contractors to take the first step to join the contractor ecosystem, whether through IT Schedule 70 using FASt Lane or Springboard, or any other Governmentwide Acquisition Contract.

This repository is not unique in the fact that documenting and sharing best practices in an open and transparent fashion is a key part of what brought it to be and part of what makes the process repeatable and scalable. Examples of previous effforts that we built upon include the following:

1. Class Deviation 2018-01, which increased the micro-purchase threshold to $10,000.
2. FAR Part 13, which provides the framework for a FAR-based micro-purchase.
3. VA Micropurchase Repo on GitHub.
4. cloud.gov’s micro-purchases on GitHub.
5. 18F Micro-purchase Marketplace, which is currently archived.
6. 18F Micro-purchase insights, which provides data related to the marketplace’s operations.
7. 18F Blog posts tagged with "micro-purchase platforms".

As always, we look to improve what we do as often as we can. Any feedback through the form above would be greatly appreciated!

Using the MPT in this manner isn’t for every project or every team. In order for this process to be successful for you, your team must operate in either one- or two-week sprints, have well defined user stories, and strictly adhere to the idea that no individual request should span more than one sprint. Additionally, there will have to be two "Teams of 3" that will be responsible for executing the buy.

Each member of the both teams should be familiar with the