Loading Profile...
Report for Points by Member
Is there a way to view the points completed by each member of the team?
I’m indifferent
7
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hi...Tracker works mostly at the team level, but it is possible to search for all stories owned by a developer, with the following syntax: "owner:username". The search results panel will show a point total at the top.
-
Inappropriate?It would really help a lot if results could be split out and presented down to the level of a team member. Ultimately, it would be great to see velocity per developer, and total (weighted) points per developer.
If rather than just knowing who accepts a story, you knew the composition of the pair working on a story, then you could use actual costs for each developer to measure financial performance. This could be very helpful in a diverse team where some people are consultants, others are employees, and others are offshore developers.
Financial measurement, or even just points, allocated to individuals could be useful even when everyone is working for free on a few venture. This could be used to automatically allocate "equity" based on contributions. Using points assumes everyone's time is of equal value, using nominal dollar amounts (one person works for $1/hr, another works for $1.25/hr) could allow weighting to reflect other factors.
I’m a bit disappointed
-
Inappropriate?Yes, this information would be much usefull if it could be compared with all members of the team
I’m bit disappointed also
-
Inappropriate?Yes, this would help tremendously for resource planning and work allocation. Could you just include the query "owner:username" that shows the number of points in the report screen? -
Inappropriate?The search results panel shows a point total at the top, as well as the # that have been completed.
Every project is different, but we've found that project planning at the team level is more effective than managing/allocating individuals on the team. Stable teams tend to have fairly predictable velocity, and with a prioritized backlog of estimated stories, work allocation happens without any overhead (people grab stories as they free up). -
Inappropriate?I'd be into a report of story points per member per iteration. The data are there to compute this, and it seems quite useful.
I’m also disappointed.
-
Inappropriate?Just added this as an idea.
Re jessica and danp's comments: I think the utility in it would be for assessing member contribution to date rather than determining work allocation going forward. It would be very useful feedback for project owner and individual members alike. -
EMPLOYEE
