SDS JIRA Guide

Owned by Marjorie Lucas
Last updated: Jul 15, 2020
2 min read

Sprint Board: https://jira.jpl.nasa.gov/secure/RapidBoard.jspa?projectKey=ARIA&rapidView=1348

Sprint Planning/Closing

Sprints are two weeks long and sprint planning/closing is nominally held on Wednesdays between 11am - 12pm PST, with the sprint closing around 11am and the following sprint starting around 12pm. The Wednesdays when sprint planning is not held will be used for backlog grooming and as a hackathon. The first hour of the sprint meeting is devoted to sprint closure and the second to sprint planning:

Sprint Closing:

  1. Review Done tickets and move to Resolved if they meet their done criteria.

  2. Review In-Progress and To-Do tickets to identify any blockers or additional work that needs to be scoped.

Sprint Planning:

  1. Pull incomplete tickets from the previous sprint to the current sprint unless tickets have been moved to the Backlog.

  2. Specify/update effort estimations.

  3. Pull highest-priority tickets from the Backlog to the current sprint to fill each team member’s expected effort for the coming sprint.

Sprint Standups

Daily standups are held on the #hysds-aria-dev-standups channel every morning at 9am. Team members are asked to answer the following questions:

Post daily update to the 3 questions: 1. What did you get done yesterday? (answers need issue numbers) 2. What are you working on today? (answers need issue numbers) 3. Is there anything blocking you? (reference issue numbers if applicable)

Answers should be a direct reply to the thread, making sure to list relevant ticket numbers.

There is also a face-to-face weekly standup on Tuesday mornings at 9:45am, for which a WebEx link is posted in the #hysds-aria-dev-standups channel.

Ticket Anatomy

This is a short list of required input fields for tickets and how to enter the information to instill consistency throughout the team.

Description

Description of the ticket, why it exists, and what it plans to accomplish – is this a new feature? Bug fix? Operations?, etc.

Estimation

An estimate of the effort it will take to complete the ticket. We are loosely using the Fibonacci sequence as a reference i.e. an effort of 1 is reserved for small tasks and an effort of 8 would be a large, day-long task.

Definition of Done

List of criteria that need to be met before ticket may be moved to Done status. This information shall be listed in the Description input field as an itemized list. Items completed on the list shall be indicated as such by strikethrough.

Ticket Work-Flow

To-Do: Work on ticket has not started. Default state upon ticket creation.

In-Progress: Work on ticket has started.

Done: Ticket has met its done criteria.

Resolved: Ticket has been reviewed against its done criteria by team.

Resources

New to JIRA? Check out the documentation on the Atlassian page: https://www.atlassian.com/software/jira/guides