Jira Working Agreements & Budget Tracking

Owned by Sarah Jackson (Deactivated)
Apr 10, 2014

Budget Tracking

  • All items need a Budget Line Item code
  • All items need an Original Estimate
  • Items "In Progress" are updated daily using Log Work
    • Time Spent: Actual number of hours you worked on the item today
    • Remaining Estimate: Set to number of hours you estimate you still need to do to complete the task. Should be 0 for Resolved items.
    • Time Spent in JIRA ticket you work on in a day should be close to the number of SELV hours recorded on your timesheet. Timesheet will by synched up with JIRA budget report monthly.
  • Items that have not been triaged should not be worked

Status Fields

  
Waiting for TriageNew items not yet approved for work
BacklogItem that is not required for launch
To DoItems with pre-approved budget, or new (unidentified) items determine critical for launch during triage
In ProgressActive work in progress
Resolved

Work complete. QA may still be needed

Tickets should be resolved back to the originator (chose "Automatic" as assignee to have system do this for you)

Resolution type:

  • "Done"     Task not requiring QA 100% complete.
  • "Fixed – Needs QA"  Development done. Select "automatic" for assigned to have it return to the originator for testing.
  •  "Fixed – QA Done"  QA complete.
Closed / ReleasedDeployed

Triage Process

  • We will meet twice weekly to review new work items (T/TH)
  • A list of new items and ISG recommendation will be sent prior to the meeting
  • Decision maker in triage process is HSG

Releases

  • Releases are used to track software development items intended to be released together

 

Â