Skip to main content

Review a stage's mockups

When the work changes anything a person sees, a Business analyst or Architect stage does not only describe the new screens: it hands over a mockup of each changed screen. A mockup is one clickable page whose buttons, tabs and links really switch between screens and states, filled with made-up data. Reviewing them before the build starts is the cheapest moment to say "not like that".

Mockups come from an epic's Analyze and Design subtasks, and from any stage of your own playbook whose expert is Business analyst or Architect. Work that changes no screen gets no mockup.

  1. Open the epic (or the task running your playbook) and select its Subtasks tab.
  2. Select the Analyze subtask, or Design once it has run, to open it.
  3. Select the Artifacts tab. The stage's document is listed there, and each mockup beside it as a File that is a web page. The document names each mockup it made.
  4. Select a mockup in the list. It opens below the list, live: click its buttons, tabs and links to move between its screens. Nothing in it is saved or sent anywhere.
  5. To look at it at full size, select Download beside its name and open the saved file in your browser.
  6. Repeat for each mockup. Design builds on the screens Analyze already mocked up and adds only the ones they don't cover, so read both.
  7. Say what should change. If the stage stopped with a question, answer it (see Answer a task's question); otherwise leave a comment on the subtask (see Comment on a task) before the build stages start.

A mockup is a picture of the intended screens, not the change itself: what ships is built by the later stages and arrives as a merged change.