よくある質問 (ライブ プラン)

このページの内容

お困りですか?

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

コミュニティに質問

The content in this page pertains to the usage of live plans in Advanced Roadmaps.

プラン

プランは会計年度単位と考慮されますか、それとも個々のプロジェクトとして考慮されますか?

A plan can be used at different levels. There is no general rule to using plans – how you use plans would typically depend on how you work. You might make different plans for different programs, create a separate plan for the next quarter, or make plans for a particular set of projects. The only rule is that plans are logically separated, and should not share any data, such as resource availability. This means whenever you need to balance resources between projects and teams, put the data into one plan.

プランの詳細を確認する

イニシアチブとリリースの機能面での目的は何ですか? どのように Jira プロジェクトに関連するのでしょうか?

イニシアチブはエピックやストーリーを大規模な作業単位にまとめます。イニシアチブは一般に複数のリリースにわたり、その間に中間的なデリバリが含まれます。ビジネス イニシアチブは一般に、実際のスコープと投資を含み、上位の管理層が承認したり、上位の管理層に報告したりするための粒度を示します。イニシアチブには Jira プロジェクトとの直接的な関係はありません。ほとんどの場合、1 つのイニシアチブにまとめられたエピックやストーリーは複数の Jira プロジェクトに存在します。1 つのイニシアチブのすべての課題が 1 つの専用の Jira プロジェクトに所属する場合もあります。

イニシアチブの詳細を確認する

Is there a separation between dynamic planning and the commitment of changes?

In Advanced Roadmaps, you can play with different scenarios before deciding to commit changes back to Jira. The total number of changes made in your scenario is indicated in an orange bubble at the top of your plan.

You can confirm changes by committing them to Jira, or discard them by reverting them.

Learn more about committing plan changes 

範囲

The issue 'x' doesn't appear in my plan

以下を確認してください。

  • the fixVersion field is not hidden for that issue type.
  • there are no filters set in the plan/setup wizard that are excluding it
  • the issue is has not been resolved otherwise It won't be visible in the import wizard.
  • if you are in plan view, go to More > status > open and completed issues and/or More > status > completion date.
  • the issue is not within a release that has been excluded.
  • the issue was not manually excluded in the wizard.

新しい課題をプランにインポートするにはどうすればよいですか?

Advanced Roadmaps doesn't exactly "import" issues, but lets you set projects/boards/filters as an issue source so that any new issue added to those sources from Jira are automatically added to your plan.

プランの作成の詳細を確認する

イニシアチブを追加するにはどうすればよいですか?

Initiatives are the high-level priorities that multiple teams or departments work against in an organization or company. Initiatives can span multiple epics, projects, and teams, and the work for initiatives can last months and even years. Using initiatives is essential in Advanced Roadmaps, so you'll need to configure these in your plan hierarchy.

Learn more about creating new initiatives

Jira のスプリントに課題を追加するにはどうすればよいですか?

You can assign issues to a specific sprint in Advanced Roadmaps, but it requires a small amount of configuration and only works for "board" issue sources.

チーム

I need to manage a mixture of teams that use Scrum and Kanban. Can I still use Advanced Roadmaps?

はい、Advanced Roadmaps では、スクラムとカンバンを使用するチームが混在した状態がサポートされます。両方の方法論に共通するのは、新しい作業を開始する前に課題での作業を完全に終了する必要がある点です。複数の課題に取り組む十分なキャパシティがある場合は、それも適宜反映されます。

Learn more about working with initiatives

Can multiple users be assigned to the same story through Advanced Roadmaps?

Yes, Advanced Roadmaps lets you assign multiple users to the same story. The maximum number of people that can be assigned to a single story is configurable in the settings.

Learn more about managing your teams

Can Advanced Roadmaps suggest the best teams to assign to initiatives based on the schedule?

If you don't assign a team manually, Advanced Roadmaps will make an automatic assignment, and suggest the teams who can deliver the work the fastest.

Learn more about working with initiatives

リリース

How do you model a release sprint, regression, or stabilization effort inside a release date being calculated?

There are different options to achieve this goal.

  1. Put a placeholder epic with an effort estimate to represent the stabilization effort. You could size it in such a way that it fills out the capacity for a full time for a sprint. You might have to work with dependencies or an earliest start date constraint to ensure the capacity is reserved only after the other work is done. 
  2. Another approach is modify the start date of the next release to leave a time buffer in-between for example, the subsequent release starting 2 weeks after the end of the previous release.

Any plans for sprint capacity planning? I'd like to know where my resource bottlenecks are during a two-week iteration. Jira doesn't do this natively, and as a result, I have to create a capacity plan in Excel.

Advanced Roadmaps should be able to help you with that today. It might be a bit counter-intuitive since you work in sprints, but in order to plan exact capacities on a day to day basis you would have to switch the team to Kanban mode (in the people section, team schedule column). You could  use releases to represent sprints instead. This will give you a day-to-day plan within your sprints to see how people are allocated. 

Learn about Reports

レポート

Does Advanced Roadmaps support exporting for reports?

We currently have CSV exports available for the scope and releases. To download a CSV, go to the particular report, and click the export button located on the right.

レポートの CSV エクスポートの詳細を確認

スケジュール

Please refer to Scheduling and timeline for more information about this topic.


最終更新日 2020 年 5 月 8 日

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

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