Tasks, Estimate, assignment, Labels... feedback :)

Thread is closed for posting
3 posts, 0 answers
  1. Jean-Yves
    Jean-Yves avatar
    69 posts
    Member since:
    Feb 2009

    Posted 13 Sep 2010 Link to this post


    Since few days I'm working with the great tool : TeamPulse. And i'm Sooooooooooo good. Very nice job.
    I think that for now it's a great tool to manage a team, but for people in the team, you can improve a bit with feature juste for them.

    I have some ideas to help me more, and it can be some great feature to add for every one.

    1) A view : My Tasks
    It could be great to have like a 'storyboad', a 'taskboad'. Like this i will know that I have to do today and in the future.

    2) Progress Time for Tasks
    Yes, we have a lot of informations about task (Estimate optimistic, probable, pessimistic), but we can't compare with what happened (real time to do this task). I would like every day to update how long I worked on each task. Of course after you can imagine that we can see the profil of the developper optimist, realist or pressimist.
    And I think that after time people will be better and better in estimate if they have some feedback on this.

    3) I don't have any legende for the storyboad (not event in the documentation). So, I see for example the priority with a progress bar, but what mean this progress bar ? Same for the estimate ?

    4) I would like to configure my project a bit more. Like :
    • What is the default 'assigne to', if there is one developper, it's very usefull :)

    • An automatique calculate of the estimate of stories. Let me explain a bit more. I would like to see 3 kind of calculation.
    1. Sum of Estimate optimistic task
    2. Sum of Estimate probable task
    3. Sum of Estimate pessimistic task
    Like this, the estimate story would be a read only field if the calculation mode is activate.
    And we can see what are the impact on the planning and the min max... I would like something like this so much.
    For the moment I use 1 script to do this it can help some people so i put it : 
    UPDATE [TeamPulse].[dbo].[Story]
       SET [Points] = (Select SUM([EstimateOptimistic]) from Task where Story.StoryID = Task.StoryID)
    UPDATE [TeamPulse].[dbo].[Story]
       SET [Points] = (Select SUM([EstimateProbable]) from Task where Story.StoryID = Task.StoryID)
    UPDATE [TeamPulse].[dbo].[Story]
       SET [Points] = (Select SUM([EstimatePessimistic]) from Task where Story.StoryID = Task.StoryID)

    5) Labels for story
    It could be great to add some Labels to the stories. Like this we can imagine to filter stories by labels. Example : [Bug] [New feature] [Evolution] [Core] [Test] [Optionnal]...

    6) Settings of team member
    Like, I'm john, and I can work between 25h and 35h a week on the project B. So that mean : the estimate Min and Max for the iterration. Right now it's cool that you can put what you want, but it could be good to put some rules to calculate those field.

    Pouf ! that's it ! :))
    Anyway, it's a great tool.
    I'm sorry to give you that much thinking work!

    Thank you
  2. David Harris
    David Harris avatar
    1 posts

    Posted 15 Sep 2010 Link to this post

    Hi Jean-Yves,

    Thank you for the excellent feedback! We have logged all of your suggestions individually into our internal system and will prioritize them as we move forward with feature development. Some of these ideas are things we have already discussed internally and even made some progress towards, so keep your eyes open in future versions of the product!

    I have awarded you some Telerik points for the high quality of your feedback.

    Kind regards,
    David Harris
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Jon
    Jon avatar
    1 posts
    Member since:
    Nov 2010

    Posted 08 Mar 2011 Link to this post

    Good points Jean-Yves -
    We to came to the same conclusion on updating Story points based on task sum as you describe. I went one step further to add this as an UPDATE trigger to the db so that as tasks are updated it automatically adjusts the story estimate.

Back to Top