2022-12-08 Resource Access Meeting Notes

... shares experiences with assisting in creating a user story in Jira

• it helped to look at similar looing Jira issues and coping them

• it would be good to talk about the relations between different Jira elements (issue links etc.)

• POs will help with choosing the correct descriptions and lables

Julie gives an introduction into how the development team is working in regard to embedding the user story into Features

• "Stories are the product backlog items that are used by developers to guide their work", i.e. this is what gets programmed.

• Stories also provide the basis of the test cases for Bugfest.

• All stories should be tied to a feature (itself to be tied to an epic), to help organise the tickets and provide context, why this story is needed and what it relates to.

Tips:

• User Stories: get as many details in as possible

• A story per Feature element will be helpful

How do we find more features/user stories to work on:

• "Easy" jiras for RA PO group discussion
  
  

  • feel free to add to this list

• feel free to take ownership of these

• Jira Workflow Statuses:

  • • Draft means it is not yet in the backlog

    • Open means it is ready for development