The developer summary provides a report of an individual developer's work patterns for a period of time. 

The developer summary provides a deeper level of understanding and context on a developer’s performance. 

You can look at daily code commits, new work vs. churn, and you can see the team players or if a developer is stuck. It’s compelling to know what each team member is doing well or could improve upon. 

You can use it to identify weaknesses and find opportunities for growth. You can use this report in stand-ups, every day.

With the Developer Summary, it’s now possible to have a better understanding of what’s going on before you enter a meeting, or before you go ahead and shoulder-tap someone to ask. Now, when a manager asks you why you want to promote someone, you can simply pull up a report and use the data to help you tell the story.

Did this answer your question?