You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the Jira tickets were loaded for the estimates, tickets may already have been estimated. For such tickets an indicator for the Scrum Master is helpful so that they are not unnecessarily re-estimated.
This can be avoided by adjusting the JQL when reading the tickets for the first time. However, during the estimation process and many user stories the overview can still get lost, so this indicator should be used both when reading the tickets for the first time and when updating user stories.
For the last aspect we should consider whether the list of user stories is updated or only the previously estimated ticket is updated.
If the list of tickets is updated, a JQL could be used which excludes estimated tickets. The list of tickets to be estimated would then become shorter.
The text was updated successfully, but these errors were encountered:
If the Jira tickets were loaded for the estimates, tickets may already have been estimated. For such tickets an indicator for the Scrum Master is helpful so that they are not unnecessarily re-estimated.
This can be avoided by adjusting the JQL when reading the tickets for the first time. However, during the estimation process and many user stories the overview can still get lost, so this indicator should be used both when reading the tickets for the first time and when updating user stories.
For the last aspect we should consider whether the list of user stories is updated or only the previously estimated ticket is updated.
If the list of tickets is updated, a JQL could be used which excludes estimated tickets. The list of tickets to be estimated would then become shorter.
The text was updated successfully, but these errors were encountered: