Uploaded image for project: 'JIRA Agile'
  1. JIRA Agile
  2. GHS-1187

Evidence Based Scheduling (EBS) Feature

    Details

    • Type: Suggestion
    • Status: Open (View Workflow)
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      I think it would be real nice if Greenhopper provides evidence-based scheduling to JIRA

      See the rationale in practice here: http://www.joelonsoftware.com/items/2007/10/26.html
      FogBugz has this feature, which is really neat: http://www.fogcreek.com/FogBugz/learnmore.html#hist_PredictShipDates

        Issue Links

          Activity

          Hide
          cowwoc Gili added a comment - - edited

          As much as I love JIRA, FogBugz's Evidence-Based Scheduling is light years ahead when it comes to scheduling. I already purchased a JIRA and Confluence license. I am actively looking to purchase an add-on to help me with scheduling, but not without this feature.

          Show
          cowwoc Gili added a comment - - edited As much as I love JIRA, FogBugz's Evidence-Based Scheduling is light years ahead when it comes to scheduling. I already purchased a JIRA and Confluence license. I am actively looking to purchase an add-on to help me with scheduling, but not without this feature.
          Hide
          taoy Josef Karthauser added a comment -

          I also desire this functionality. We recently moved to Jira/greenhopper from fogbugz, for a number of reasons but mainly the functionality that greenhopper provides for agile development. However, without evidence based scheduling I have absolutely no idea how to make reliable predictions on delivery dates with jira.

          Show
          taoy Josef Karthauser added a comment - I also desire this functionality. We recently moved to Jira/greenhopper from fogbugz, for a number of reasons but mainly the functionality that greenhopper provides for agile development. However, without evidence based scheduling I have absolutely no idea how to make reliable predictions on delivery dates with jira.
          Hide
          petemounce Peter Mounce added a comment - - edited

          For the love of all that is holy, I would kill for EBS in JIRA or via some plugin. Our team (about 20-strong) would benefit hugely. I've used it in FogBugz, and it was eeriely amazing at how easy it was to then push back to the business on scope-creep or incomplete/inaccurate requirements. It was literally a killer feature.

          Show
          petemounce Peter Mounce added a comment - - edited For the love of all that is holy, I would kill for EBS in JIRA or via some plugin. Our team (about 20-strong) would benefit hugely. I've used it in FogBugz, and it was eeriely amazing at how easy it was to then push back to the business on scope-creep or incomplete/inaccurate requirements. It was literally a killer feature.
          Hide
          askbjoernhansen Ask Bjørn Hansen added a comment -

          This would be a big deal to us as well.

          Show
          askbjoernhansen Ask Bjørn Hansen added a comment - This would be a big deal to us as well.
          Hide
          andrewmwebster Andrew Webster added a comment -

          +10 This would be a hugely useful feature. We have a situation where team vary across projects all the time, so being able to handle velocity and estimation with any mix of people would be a huge benefit for us.

          Show
          andrewmwebster Andrew Webster added a comment - +10 This would be a hugely useful feature. We have a situation where team vary across projects all the time, so being able to handle velocity and estimation with any mix of people would be a huge benefit for us.
          Hide
          gregreynolds Greg Reynolds added a comment -

          This is still a significant problem with JIRA. I absolutely need a way to manage and plan product releases, to view the release burndown. On a related note there needs to be a better way to view the roll up of User Stories under Epics, and Epics under Epics. Having to drill down into a ticket to see associated stories is not enough. I need story points to rollup, and an ability to view the parent-child relationships in a tree like view.

          Show
          gregreynolds Greg Reynolds added a comment - This is still a significant problem with JIRA. I absolutely need a way to manage and plan product releases, to view the release burndown. On a related note there needs to be a better way to view the roll up of User Stories under Epics, and Epics under Epics. Having to drill down into a ticket to see associated stories is not enough. I need story points to rollup, and an ability to view the parent-child relationships in a tree like view.
          Hide
          tyler00durden Gerald Lim added a comment -

          My company would love to see this as well. It would help tremendously.

          Show
          tyler00durden Gerald Lim added a comment - My company would love to see this as well. It would help tremendously.
          Hide
          atlassian@agilevelocity.com Tracy Whitehill added a comment -

          I think anything that requires team members to acurrately track their time will end up being flawed. It is very tough to get accurate. Many advanced Scrum Coaches are even dropping the hours estimating all together. Joel's first step is the most valid. Break it down. I am mostly a fan of doing this with smaller stories. Then task in Sprint planning, but if I have small pointed stories then I dont really need all the hours tracking stuff. It gets in the way. EBS with story points and small stories then yes, but not at an hours level would be my recommendation.

          Show
          atlassian@agilevelocity.com Tracy Whitehill added a comment - I think anything that requires team members to acurrately track their time will end up being flawed. It is very tough to get accurate. Many advanced Scrum Coaches are even dropping the hours estimating all together. Joel's first step is the most valid. Break it down. I am mostly a fan of doing this with smaller stories. Then task in Sprint planning, but if I have small pointed stories then I dont really need all the hours tracking stuff. It gets in the way. EBS with story points and small stories then yes, but not at an hours level would be my recommendation.
          Hide
          acgentry Adam Gentry added a comment -

          I am very interested in this feature, which is not closed, yet a "duplicate" issue of GHS-1656 exists and is closed. Can you tell me if this GHS-1656 comes close to the features of fogbugz as listed bellow:

          Evidence-Based Scheduling works by doing a Monte Carlo simulation, taking into account evidence such as:

          Each developer’s track record—as they become better estimators, they’ll generate a narrower range of possible completion dates
          Estimates for all uncompleted tasks
          The developer’s schedule (including holidays, vacations, etc.)
          Project dependencies (e.g. "we can't start task A until task B is done" or "we can't start task C until the new servers arrive.")
          Other projects/tasks that sap away developers' time

          Show
          acgentry Adam Gentry added a comment - I am very interested in this feature, which is not closed, yet a "duplicate" issue of GHS-1656 exists and is closed. Can you tell me if this GHS-1656 comes close to the features of fogbugz as listed bellow: Evidence-Based Scheduling works by doing a Monte Carlo simulation, taking into account evidence such as: Each developer’s track record—as they become better estimators, they’ll generate a narrower range of possible completion dates Estimates for all uncompleted tasks The developer’s schedule (including holidays, vacations, etc.) Project dependencies (e.g. "we can't start task A until task B is done" or "we can't start task C until the new servers arrive.") Other projects/tasks that sap away developers' time
          Hide
          cowwoc Gili added a comment -

          Adam, yes. Evidence-based scheduling should cover your requirements.

          Show
          cowwoc Gili added a comment - Adam, yes. Evidence-based scheduling should cover your requirements.
          Hide
          marekvse Marek Vsechovsky added a comment -

          I'm bit confused here. Is this feature part of the new Jira or not then? I did a few quick searches and there seems to be a plugin. Does that only work with JIRA 6? Will there possibly be any videos done on that? I'd love to see how that works and if it is worth spending the time to installing or upgrading if necessary.

          Show
          marekvse Marek Vsechovsky added a comment - I'm bit confused here. Is this feature part of the new Jira or not then? I did a few quick searches and there seems to be a plugin. Does that only work with JIRA 6? Will there possibly be any videos done on that? I'd love to see how that works and if it is worth spending the time to installing or upgrading if necessary.
          Hide
          glen1 Glen Coates added a comment -

          +1 would love to see this in GreenHopper.

          Show
          glen1 Glen Coates added a comment - +1 would love to see this in GreenHopper.
          Hide
          njm Nicholas Muldoon added a comment -

          One story that would help alleviate this pain in the short term is GHS-7988.

          Show
          njm Nicholas Muldoon added a comment - One story that would help alleviate this pain in the short term is GHS-7988 .
          Hide
          yazan1 yazan jaber added a comment -

          +1 This is a great feature.

          Show
          yazan1 yazan jaber added a comment - +1 This is a great feature.

            People

            • Assignee:
              Unassigned
              Reporter:
              shachris23 Shivesh Wangrungvichaisri
            • Votes:
              44 Vote for this issue
              Watchers:
              40 Start watching this issue

              Dates

              • Created:
                Updated: