JIRA Orientation

Edit Answers
123456789101112131415161718
Across
  1. 3. Chart , shows the actual and estimated amount of work to be done in a sprint.
  2. 6. , a tool to visualize units of work moving through their specific workflow.
  3. 7. , also known as an iteration ; is a short (ideally two to four week) period in which the development team implements and delivers
  4. 9. , can be a "child" of any issue type, depending on the Issue Type Scheme of the project.
  5. 12. a software to support agile development. A product of Atlassian.
  6. 14. stand,up , Also known as a daily scrum, a 15,minute mini,meeting for the software team to sync.
  7. 15. Time , is the time spent working on an issue typically, the time taken from when work begins on an issue to when work is completed
  8. 18. , an Agile development methodology where the product is built in a series of fixed,length iterations called sprints.
Down
  1. 1. , a system for visualizing the flow of work and limiting work in progress. Not oriented towards sprints, like Scrum development methodology, as it is more ongoing.
  2. 2. , the logic that drives movement of a stories / sub,task along their development journey on a scrum or kanban board.
  3. 4. planning , A meeting that determines what to complete in the coming sprint.
  4. 5. , determine what is visible on each of your boards. Using Jira's simple query builder (JQL), you can customize exactly which issues are displayed on your board.
  5. 7. retrospective , A review of what did and didn't go well with actions to make the next sprint better.
  6. 8. , another out,of,the,box issue type in Jira.
  7. 10. , A means of categorizing issues so that agile teams can see which issues they should work on next.
  8. 11. , a list of the outstanding issues
  9. 13. , captures a large body of work that needs to be broken down into a number of smaller stories. It may take several sprints to complete an epic. The hierarchy: Project > Epics/Components > Stories > Tasks > Subtasks
  10. 16. Chart , can show the cycle time or lead time for your product, version or sprint.
  11. 17. , simply a unit of work within Jira that will be traced through a workflow, from creation to completion.