Afonso de Gouveia

← Planning

Low-Level Project Requirements

After defining the abstract requirements in step 1, and determining what the bare-bones functionalities of our product are in step 2, it's time to break the requirements down into actionable tasks.

If the requirements defined in step 1 are insufficient or need to be updated, repeat step 1 and come back.

Once you have proper requirements, break them down into actionables-“features” and “epics” in Scrum. Basically, turn the abstract goals into concrete, doable goals.