5 ms·

What is the problem you're trying to solve?

• lotyrin 8y ago
  An opinionated workflow of collecting from a development team and its customers potential future efforts, estimates of the cost and value of those efforts, prioritizing based on those estimates (maximize expected value, minimize expected cost), scheduling & forecasting efforts based on a sound statistical model (e.g. estimation error).
  • joeblau 8y ago
    You can accomplish most of that with Phabricator[1], except for the forecasting efforts. As for the forecasting; I worked at Amazon which had a dedicated JIRA engineer and that was the best I've ever seen JIRA being run and used. In my time there, I never saw any manager predict anything consistently accurate over the course of a long project with it without actually talking to engineering. JIRA promises armchair management, but I've yet to see those tools actually work. That being said, you may be a better JIRA user than anyone I know. JIRA has always be promoted as a tool from the top down, never from the bottom up. [1] - https://www.phacility.com/phabricator/ https://www.phacility.com/phabricator/
    • lotyrin 8y ago
      JIRA's problem is it's too configurable and popular with folks who are into prescriptive authority, so it absolutely can be worst tool you've ever used, and frequently will be.
      • joeblau 8y ago
        100% agree.