Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89778

Define story point supply per resource

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Timed out
    • Plans - Timeline
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.

      Having a scrum team and calculating with story points I want to be able to define a story point supply for every resource.
      Currently JPO only supports the velocity definition for the whole team.

      Workaround:

      You can adjust weekly hours as a proxy to reflect story points per team member.
      The proportion of weekly hours per team member equates to the proportion of story points assigned to members from the pool of team points.

      E.g: Team X has 30 pts
      Case 1:
      Member A - 40 weekly hrs = 10 pts
      Member B - 40 weekly hrs = 10 pts
      Member C - 40 weekly hrs = 10 pts

      Case 2:
      Member A - 60 weekly hrs = 15 pts
      Member B - 40 weekly hrs = 10 pts
      Member C - 20 weekly hrs = 5 pts

            [JRACLOUD-89778] Define story point supply per resource

            Deleted Account (Inactive) added a comment -

            This is especially valuable for teams to have rotating or inconsistent resourcing. Estimations based at the team level are not a good way of forecasting in that use-case.

            Deleted Account (Inactive) added a comment - This is especially valuable for teams to have rotating or inconsistent resourcing. Estimations based at the team level are not a good way of forecasting in that use-case.

              Unassigned Unassigned
              msturm@atlassian.com Martin Sturm (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: