Portfolio for Jira の発見

While Jira is extremely powerful in tracking the status of development work, it is not the ideal tool when you're planning work for multiple teams, across multiple projects. Jira easily becomes too granular, which can make more challenging to see how multiple projects and initiatives are tracking towards the bigger picture.

Portfolio for Jira helps fill in this gap by simply pulling in relevant issue details, and these details will be used to create a realistic schedule for all the work you're planning. Once your plan is set up, you and your teams can then have a single source of truth into the current and future health of your initiatives. With your plan, you can also create reliable forecasts of the work of your teams in Jira — and all that while keeping track of current work in an ever-changing agile environment.

Jira からの課題の詳細が表示されたサンプル プラン。

The purpose of the sample plan above is to track the long-running initiative of mobile expansion. There are three teams working together, to complete this initiative as a whole — the iOS team, Android team, and Design team. The Mobile expansion product manager is using Portfolio for Jira to plan and schedule work for these 3 teams, using relevant issue details that come from their individual boards in Jira.

What is Portfolio for Jira?

Portfolio for Jira can provide the ideal environment for realistic strategic planning, regardless of how many teams or people you have working towards your goals. Together with Jira, Portfolio for Jira can provide a single source of truth for the current and future health of your initiatives.

The plans in Portfolio for Jira make use of what-if scenarios, the data in your Jira instance, and an intuitive interface to help your team do the following:

  • イニシアチブを効率的に表示、計画、および管理する
  • 信頼できる予測と現実的なスケジュールを作成する
  • 変化を続ける環境でリリースのトラブルシューティングと管理を行う


Jira データの既存のデータからプランを作成し、エピックをイニシアチブに変換してチームまたはプロジェクトを横断して表示できるようにしましょう。


Advanced users can auto-schedule issues to create a realistic schedule. To create this schedule, multiple variables are considered, including backlog priority, estimates, and dependencies — to generate a plan in a matter of seconds.




優先付けとトレードオフの決定を迅速に行い、計画への影響を即座に表示して、"what-if" の質問に答えられるようにします。





Last modified on Mar 25, 2020


Powered by Confluence and Scroll Viewport.