Planning a project

Knowledge Videos

Short animated explainers, organised by subject.

Planning a project

Plan before you code: user stories, wireframes on paper, a list of tables and endpoints, and small steps with a done-when for each.

Transcript

Before you write code, plan. Start with user stories: sentences that say, as a who, I want what, so that why. For example: as a pet owner, I want to add my pets, so that I can see them all in one place.

Next, sketch the screens on paper: boxes for the list, the form and the buttons. This is called a wireframe. It is quick to change, which code is not.

From the sketch, list what you need. Each screen needs data, so write the table. Each action needs a request, so write the endpoints, like GET slash api slash pets.

Finally, cut the work into small steps, each with a done when. Build the smallest step that works, then the next. Three must haves first, nice to haves later.

Remember: a user story says who, what and why. A wireframe sketches the screens, a plan lists the tables and endpoints, and small steps get you there.

More in this series