Sprint / task Velocity

Hello,
Probably this question is silly, but I'm not being able to find how to assign / see the complexity to a task and the velocity of the sprint.
I've search for the help, documentation and forum and it seems that there exist a "complexity" parameter on the agile board settings, but I'm not able to find it.

Anyone can help me?
Thank you in advance.
Gabriel
5 comments
Comment actions Permalink
Hello Gabriel,
On the agile board, you can assign issues by means of the command window. Press ctrl+alt+J or just start typing when a card is in focus. In order to assign an issue, start typing a users's login or full name and then pick the appropriate user from the completion combo. To assign to yourself just type me.
BTW, the same applies to issues list.

In order to observe sprint burndown, just press the button on top right corner of the board.

As for "complexity" parameter, I'm not sure I understand what's this about. Could you please share a link on a page mentioning it?

Regards,
  Alexander
0
Comment actions Permalink
Hello Alexander,
Thanks for the tips.

About the scrum velocity concept, the idea is to assign a "complexity" value to the issues, and try to compute the team velocity, and asign task from the backlog to the sprint until the previously calculated velocity is reach.
To automate that, a sprint velocity value should be needed and a way to assing a complex estimation for each task.
I find some references to such field here:
http://youtrack.jetbrains.com/issue/JT-13687
http://youtrack.jetbrains.com/issue/JT-13687
Also on the original jetbrains concept of an agile board (or discussion about it)
http://forum.jetbrains.com/thread/YouTrack-107

Is there any way to measure and track such concepts?
Thank you

Gabriel
0
Comment actions Permalink
Gabriel,
I'm aware of the concept, but it's not directly supported yet. You can have a field of int type for your issues, but there's no way to automatically calculate a sum of such fields.

Alexander
0
Comment actions Permalink
I mean it will be calculated, but only for the single sprint.
0
Comment actions Permalink
I second the need for complexity based estimations (S, M, L, XL) and a velocity line drawn in the burndown chart.

As a work-around I just set the estimation of effort in scrum points as days to: half a day (S), full day (M), two days (L) or four days (XL) to create the same effect similar to a normal burndown chart. While it's easy to see what the velocity is, a velocity line would already help here as well.

Despite some small things like these I really love youtrack in general, and we've only been testing the 10 user downloadable for about a week now. Other nice to have's would be svn integration to relate commits to tasks and to auto-trak time spend on a task somehow (e.g. when it's on a 'in-progress'-column).
0

Please sign in to leave a comment.