Deep dive & Edge Cases

Long-running work and edge cases

1. What if an employee works on very few tickets in a month?

   • More tickets provide a more granular ratio. If a user completes few tickets but estimates them then the story point approach 

2. What if an employee works on very few tickets in a year?

   • This is not as much of a concern because the month ratios are generated and then averaged together. If one month has no effort it should be note that the year only had 11 active months and not 12.

   • A link explaining how the year could be totaled

     •  n.b this total is not generated in the report; generally people want to see the month breakdown and totaling the year is not difficult if they want to do that.

Holidays, vacation, and OOO

4. How to account for salary changes for people during the year?

   • We have no direct way of reflecting salary changes at this time.

5. How to account for people who go on vacation?

   • If a developer is out for an entire month then that month can be omitted (by reducing the number of months worked in a year.)

   • If a developer is out for 2 weeks of a month, however, and only does a few tickets we do not need to account for this: A salaried worker would make the same salary that month despite their vacation and therefore the ratio of the work they did that month (while they were at work) is still valid

Assigning credit

6. What if an employee only spends a portion of their time on development work?

   • Improvements to Jira data and processes tracking work.

7. How is credit assigned if a ticket is worked on by more than one employee?

   • We have to allocation methods that address this: Full credit to all and split credit

8. What if a ticket is assigned to an employee only briefly and that user did not really work on this issue?

   • They will get credit as if they did work on it earnestly.