Status checklist
This part is where you create a list of all the UI components, UI screens, and features that are or will be included later on in the product, so both you, as a designer, and the developers can check the status of these components, features, and screens.
Usually, the status checklist document is divided into five different columns, and each column represents the data related to that task.
For example, in this document, you have the Action Item, the link to the design (from Zeplin, Sympli, or Invision), the Dependency that tells you whether it is a backend task, frontend, or design, the comments column, and also the status:
If any feature or component is missing from the status list, then the developer will not consider themselves ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access