Using the API Project Assets Checklist
Design and Build Great Web APIs — by Mike Amundsen (124 / 127)
If you are a stand-alone “full stack” developer working on the project, I suggest you work through this assets checklist in the order presented. As you gain experience with the list, you might change up the order in a way that works better for you. For example, you may write your tests earlier and create smaller prototypes that you can test before completing all your design elements.
If you’re working on a team that divides responsibilities between roles — for example, designers, developers, and operations staff — then you can arrange the list in a way that allows all roles to operate in parallel. I’ve worked on several teams where the person in charge of deployment writes an initial working script the first day of the project and continues to update and modify it as needed.
No matter your method of working, you should have an API assets list that’s shared with all members working on the project and that’s referred to frequently throughout the life of the API.