Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Product Manager
  • Reviewing is done by peers (other Products Managers), Stakeholders and the scrum team.

Process steps - Theme, Epic, User Story and Requirements Writing

All steps below are the responsibility of the Product Manager,  but you want to work in parallel, and together with UX&UI Designer(s) so that i.e. user stories and UX stays aligned and is consistent at the end of the process.


  • Title  - I.e. View Authors. 
  • Description containing:
    • Full User story - i.e. As a Blog Administrator I want to see all Authors so I know who has access to Blog Writing functionality
    • Link to clickable Design - i.e.
    • A table with texts that are not visible, i.e. error messages in the primary language of the app (Responsibility of the UXUI Designer)
    • Other information that will help both stakeholders and the team understand the user need.
    • Acceptance criteria (See: Writing Acceptance Criteria). Limit yourself to circa 1-3 acceptance criteria the cover the most important outcomes of the story (not the function, i.e. not which fields should be mandatory, default values, etc)
    • Detailed requirements. If needed, detailed requirements.
      • Do not include things that can be seen in the UI Design (i.e. which fields/buttons are present). You can include details like which fields are mandatory (if not clear from i.e. data definition table) or what their default values are. An example requirement is: The email address should be validated against ISO-1234.  


Improvement points

  • Requirements writing could use it's own page (check what's already on acceptance criteria writing)
  • Subtasks (only use when needed, ie 2 people on 1 story)
  • Design User stories (user different ticket type for design user stories, that you convert to normal user story before development starts)
  • Jira Boards and backlog filter for the dual track agile (doing design before dev).