martial

My feedback

  1. 20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    martial shared this idea  · 
  2. 42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    martial supported this idea  · 
    An error occurred while saving the comment
    martial commented  · 

    Hi,

    It could may be extended to TFS state?

    Rds
    Martial

  3. 44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    martial commented  · 

    Hi,

    Sorry for answering so late, I missed the questions you set.
    My first comment is that for me, the automatic sorting is a great nice to have but the most important is the stack itself; automatic sorting should not block stack rank.

    I do a short description you an overview of our current way of using Speclog, I think it will help to understand my answer below:
    - We have one workspace per project
    - We create one workspace per iteration
    - We do a rough pre-selection of user stories and include them to this iteration workspace; total estimate is greater than iteration capacity (20-30% in excess).
    - We then define the priorities in this iteration workspace.

    This 2 steps make things easier for us to define priorities. I need stack rank because:
    - We provide the user stories to the customer in html format, and it must be sorted by priorities; currently this is impossible.
    - We need it in TFS; currently we do update manually

    Therefore most of the issues you raised in your questions (y-axis, slice, …) were not in my mind when I raised the idea.
    I had just in mind to prioritize user stories of my iteration workspace, independtly of axis, slice, …
    That s why I m very interested by your idea of workspace position -> stack rank.

    My answers to the questions:
    Stack rank -> workspace position: My preference would be by colum, most important top left, 2nd one below, … ; a new column is created every 5-6 users stories. This is the best to display as many as possible user stories in one screen. But I know other Speclog users work differently (one column for instance).

    Workspace position -> stack rank :
    - You re right, very interesting, much faster than updating each user story one by one.
    - Current stack rank of the top left story on the workspace is used as reference, next user stories has stack rank incremented by 1
    - How should we rank stories on the same x-level? I don t know the best way to proceed.

    Working with slices: this is currently not my case, I don t know the best way to proceed.

    Rds
    Martial

    martial shared this idea  · 

Feedback and Knowledge Base