ユースケース

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

Portfolio for JIRA highly enhances the benefits you get from your JIRA application, no matter the role you have in your team.

Check out some of the popular use cases of Portfolio for JIRA in the market, depending on the role being taken on. 

役割ごとのユースケース

プロダクト マネージャーの場合

As a product manager, you need a way to quickly turn the feature ideas and customer feedback into a compelling product roadmap to keep stakeholders informed and for your own guidance. You also need visibility into the team's progress so you can keep your plan up-to-date as things change. If this sounds like you, keep reading to learn about three ways Portfolio for JIRA can help you plan better.


アイディアの整理

Start by defining initiatives in Portfolio for JIRA; think of initiatives as chunks of work spanning multiple epics and teams, so you can see what needs to be done in the next planning cycle. Once you’ve defined initiatives, they need to be broken down into smaller work- pieces to populate the backlog:

  1. イニシアチブの定義

    イニシアチブと他の階層レベルの構成」の手順に従ってイニシアチブを定義します。

  2. イニシアチブを新しいエピックやストーリーにブレイク ダウンする

    Break your initiatives down into epics and stories that are ready for implementation; they can be turned into actual JIRA issues.

    Follow the steps provided in Creating and deleting issues.

  3. Import existing work items

    Import all of the relevant epics and stories that already exist in your JIRA application, and assign them to the right initiatives.

    Follow the steps provided in Importing, exporting and duplicating classic plans.

ロードマップの作成

A roadmap is based on scope, time, and people. You can play with these variables in Portfolio for JIRA to see different roadmap scenarios. Once you have a backlog of ideas in the form of work items, you need to get everything on a roadmap to share with your stakeholders. These are the three things you need to build a roadmap:

  1. 範囲の設定

    アイディアを整理し、バックログの用ができたら、作業を見積もる必要があります。 

  2. ターゲット リリース日

    Configure your release dates by following the steps provided in Creating project-specific releases.
  3. チームの選択

    Define your teams and their velocities in hours or points. The velocity can be linked directly to a board in your JIRA application.
    Learn more about resources in Adding and removing teams.

開発マネージャーの場合

As a Development Manager, you’re responsible for making realistic commitments on your team's behalf. During the planning, you need a clear roadmap that you and the product manager have agreed on so you can run the numbers and ensure your team can get it all done. You need a way to easily plan your team's’ resources and see the capacity of the team at any point in time so you have data to show what’s possible and what isn’t. You also want to keep stakeholders informed of progress and status without too much hassle. If this sounds like you, keep reading to learn about three ways Portfolio for JIRA helps you plan better.


キャパシティ プランニングをマスターする

チーム内に複数の専門領域を持つメンバーがいる場合、キャパシティ プランニングを行ってプランの現実性を確保し、作業の完了に特定のスキルが必要な場合のボトルネックを回避できます。

Learn more about your team capabilities in Learn stages and skills.

ロードマップにチームのキャパシティを表示する

Portfolio for JIRA allows you to understand what your team is working on at a much more granular level, so when it comes to planning scope with project and product managers, you have the data to support your views on what’s possible and what isn’t.

  • Capacity view
    The graphical schedule shows both planned capacity and resource utilization. Capacity is displayed as story points for Scrum teams, while capacity is plotted using calendar weeks for Kanban teams. You can view capacity by release, team and even team members.
  • Stories view
    The stories view shows individual stories and their stages of work. When using scrum, the schedule creates a swimlane per team and shows the team’s sprints, as well as the stories scheduled for each of the sprints. When using kanban, the view plots the stories on a day granularity timeline. You can also view the schedule as stories by team person.

    Learn to use the views by following the steps provided in Scheduling behavior.
プロジェクトの進捗を追跡する

In Portfolio for JIRA, you can see the progress for individual story items, epics, and initiatives. For anything that is unestimated, you can show those items in relation to items that are estimated. This will allow you to see the percentage of work done on estimated items while also seeing that some unestimated items are still outstanding and require work.

  1. 追跡オプションを設定する

    Portfolio for JIRA supports different ways to track progress depending on your team's requirements. 
    Learn to configure the progress tracking by following the steps provided in Tracking progress and status.
  2. バックログでステータスと進捗を確認する

    バックログの進捗およびステータス列で計画項目の進捗状況を確認できます。  

    • Issue Status - Only exists if the backlog item links to one or multiple JIRA issues. It shows the actual workflow status of these issues. In the case of multiple issue links, an icon is shown for the status of each linked issue. 
    • Progress - Sum of work logs on the linked JIRA issues, as well as their child elements. 
    Learn to use the views by following the steps provided in Status and progress tracking.

プロジェクト マネージャーの場合

As a project manager, you plan and coordinate work against milestones to make sure you're meeting deadlines, and to show how projects are tracking against business goals. Dependencies are a big thing for you – they account for 90% of your planning-related headaches – so you need to map out these dependencies, and not just track them. Having a graphical or visual presentation of information is really helpful at times.


マイルストーンに従って計画する
  1. 範囲の設定

    Once you've organized your ideas, you can re-prioritize the work items.
  2. リリースを定義

    Configure your release dates by following the steps provided in Configuring release dates.
Manage dependencies so the timeline is realistic

In Portfolio for JIRA, it’s possible to control the sequence in which items are scheduled on the roadmap by setting explicit dependencies.

  1. Create and manage your dependencies
    Configure your release dates by following the steps provided in Managing Portfolio dependencies.
  2. Configure your hierarchy levels.
    Display the dependencies in the graphical schedule by following the steps given in Configure initiatives and other hierarchy levels.
目標に向けたプログラムの状況を追跡する

In Portfolio for JIRA, you can set themes and track progress against them to make sure the organization is executing on strategy and everyone is aligned to the same priorities.

  1. Create your focus areas
    Themes are high-level strategic focus areas, value streams, or investment categories; you can use themes to set priorities and define where your teams should devote most of their time.
    Create and configure your themes by following the steps in Using the themes report.
  2. Keep track of the progress 
    The graphical schedule shows the results of resource calculations and forecasting based on your plan data. It also provides visibility into forecasted release dates. 
    Track your progress by following the steps provided in Tracking progress and status.

最終更新日 2018 年 9 月 28 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.