Engineering Productivity Metrics

Question 1

resolvedIssues

Answer 1

Issues Resolved - Number of c resolved with a positive outcome (i.e., not duplicate, not won’t-fix) during the selected time frame.

Question 2

resolvedEpics

Answer 2

Epics Resolved - Number of Epics resolved with a positive resolution during the selected time frame.

Question 3

mergedPrs
smartMergedPrs

Answer 3

Pull Requests (PRs) Merged -Number of PRs merged back to the main branch of all repositories. When looking at this in a team context, this will be the number of PRs merged linked by that team (via Jira).

*Merges can happen without a Approve or Rejection, if merge protection is not in place.

Question 4

resolvedIssuesStoryPoints

Answer 4

Story Points - Number of story points on Issues Resolved with a positive outcome (i.e., not duplicate, not won’t-fix) during the selected time frame.

Question 5

daysWithCommits
smartDaysWithCommits
v2DaysWithCommits
v2SmartDaysWithCommits

Answer 5

Days With Commits - Average number of days per week with commits per person. One day with five commits only counts as one coding day, whereas five days with one commit accounts for five coding days. Coding days can be a great representation oaccountcused a team is. Example: if a team is bogged down in meetings or dealing with crises, theiFor exampleg days typically are lower than a team that does a great job creating and prioritizing consistent, focused time to work. Typically Jellyfish customers average between the range of 1.5-3.5 coding days.

Question 6

assignedIssues

Answer 6

Issues Assigned* - Number of issues that were put into “in progress” over the specified time frame

Question 7

workedIssues

Answer 7

Issues Worked - Number of issues “worked on” over the specified time frame.

Question 8

openedPrs

Answer 8

Pull Requests Opened - Number of Pull Requests opened over the specified time frame.

Question 9

workloggedHours

Answer 9

Hours Logged - Total number of hours logged on issues over the specified time frame.