This tracks well with the issues of assessing developer productivity on an individual level rather than the team level.
For example, even if social type had a productive day in their book they wouldn't have much code or Jira movement to show for. However, on a team level they might have prevented task blockers or ensured knowledge transfer to more inexperienced team members.
Thanks for the apt summary, as always.
This tracks well with the issues of assessing developer productivity on an individual level rather than the team level.
For example, even if social type had a productive day in their book they wouldn't have much code or Jira movement to show for. However, on a team level they might have prevented task blockers or ensured knowledge transfer to more inexperienced team members.
I like this model. Somewhat reminiscent of the Julia Evans cartoon - https://wizardzines.com/comics/some-people-who-make-programming-easier/