1. Start with a product/project brief that explains the who, why, and what if the project at a high level to ensure the business is aligned. 2. Architecture an

1. Start with a product/project brief that explains the who, why, and what if the project at a high level to ensure the business is aligned. 2. Architecture and design docs explain the “how” to engineering. 3. The work gets broken down to stories and sub-tasks and added to a Scrum/Kanban board. I like Jira, but have also used Asana and Trello. Testing is just another sub-task, and part of the general definition of some for a story. For larger projects, a project-specific test suite may be useful. Write failing tests. Once they all pass, you have an indication that the project is nearly done. You can skip to #3 if everyone is aligned on the goals and how you’ll achieve them.