ステージとスキルについて学ぶ

このページの内容

お困りですか?

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

コミュニティに質問

このページでは、Advanced Roadmaps のライブ プランの使い方について説明します。デザインが変更されたプラン インターフェイスを使用している場合は、こちらのページをご覧ください。

Stages are activities that are done sequentially per work item. In a typical release, there are several work stages that could happen in a sequence.

For example, let's say your team works according to the following stages:

  • Stage 1 is Design, where designers brainstorm and come up with the product design, based on the product and user requirements that have been scoped
  • ステージ 2 は Implementation です。このステージでは、開発者はステージ 1 で決定した設計に基づいて、ソフトウェアを作成または更新します。
  • Stage 3 is Testing, where quality engineers then test the software, based on agreed scope, requirements, and design.

別の例として、チームが作業を時間と日数で見積り、次のステージを使用するとします。

  • Stage 1, where the product owner writes the story
  • Stage 2, where the cross-functional Scrum team handles the implementation


Skills, on the other hand, are abilities that team members must have in order to complete work items. Skills can be defined per stage and allow to categorize different types of work within a stage.

スキルは、メンバーの能力が計画作成のボトルネックになる可能性がある場合に便利です。チームに適切な専門領域があることを考慮する必要があります。

For example, let's say in the design stage, you need the following skills:

  • UI design, which pertains to UX design skills
  • Frontend architecture, which pertains to frontend development skills

To create a stage:

  1. プランで、プラン名の横にある [その他] () > [設定] >[ステージとスキル] をクリックします。
  2. [ステージを追加] をクリックします。
  3. Enter a name for the new stage.
    If necessary, change the color for the stage by clicking on the color ball and selecting a new color.

  4. Click Add stage.

To create a skill:

  1. プランで、プラン名の横にある [その他] () > [設定] >[ステージとスキル] をクリックします。
  2. [スキルを追加] をクリックします。
  3. Enter a name of the skill, and click Create skill.
  4. Set the percentage for the estimate allocation of the skill.
    The estimate allocation will define the percentage of that skill that someone needs to complete that issue.

    For example, if an issue has a total estimate of 10 points, and the implementation stage has two (2) skills visual design and coding, and each skill is 50% of the stage, this would happen: 5 points of the total estimate would require a person with visual design skills, and the remaining 5 points would require a person with coding skills.

  5. 一連のスキルを作成したら、それらをステージに追加できます。

(info) To delete a skill, hover over the skill > click more () > Delete.

Some examples of using stages and skills in teams

例 1 - 完全な機能横断型のスクラム チーム

In this example, you have a fully cross-functional Scrum team — everyone in the team can do all types of work required to implement a user story.

You have the following stages:

  • ステージ 1 - 製品の所有者がストーリーを記載します。
  • ステージ 2 ではチームがユーザー ストーリーを実装します。UI 設計、コーディング、テストなどのすべてのアクティビティが同じイテレーションで行われます。

Configuring stages will be very simple in this case. You just need to add two (2) stages, without any skills.

Anyone in the team can take over any implementation task, so everyone will have the implementation skill: 



The resulting schedule will then look like this when some stories are added. The story writing stage will be scheduled at least one sprint before the implementation stage. However, this doesn't apply to stories that don't required any story writing effort.



例 2 - ストーリーの記載は行わない、完全な機能横断型のスクラム チーム

If you prefer not to estimate and reflect any story writing effort in your capacity plan, and instead plan for story writing separately, you can choose to leave out the story writing stage altogether.

In this case, the following will happen:

  • Story writing effort is not planned in Advanced Roadmaps.
  • Implementation effort is planned in Advanced Roadmaps, and implementation is becomes stage 1.
  • Since it's the product owner that handles story writing, you no longer need to include the product owner in the capacity plan, as shown below:

Advanced Roadmaps では、ストーリーがスケジュールされるとすぐにチームで必要なすべてのインプット (ユーザー ストーリー、要件など) を利用できるようになるという想定に基づいて、スケジュールに取り組みます。

Although you can plan activities separately, we recommend that you include all types of effort, stages, and skills in your plan. One of the common challenges many teams see in their organization is being realistic and explicit about design work and user story writing. Having a single source of truth for all teams to see can help align effort — and Advanced Roadmaps can help your team achieve this better if all aspects are included in your plan.

例 3 - 専門領域を持つスクラム チーム

チームにおいて、全員がテストなどのタスクを担当でき、特定のメンバーのみが設計、コーディング、および開発テストに携わるスキルを持っているとします。

To handle this in your plan, you can add the specializations as skills for the corresponding stage, which is implementation in this example. 



After which, you can then assign the skills for each of the team members:

例 4 - 連続したスケジュール (例: カンバン) で作業するチーム

Let's say your team doesn't work in fixed iterations — and that they work on a day-to-day schedule, pulling in work from a backlog when tasks are completed. In this case, their work would be structured into design, implementation and testing – and these happen sequentially per work item. However, rather than waiting for the next iteration to start with the next stage of work, implementation can actually start on the right after design has been completed.

この例では、Advanced Roadmaps で次のようにセットアップできます。

  • チーム スケジュールをカンバン モードに切り替える
  • Define 3 stages, which are design, implementation, and test in this example
  • 必要に応じて、ステージに専門分野を追加します (この例では frontendbackend、および data management)

The schedule will look different for Kanban teams, with the stages scheduled sequentially per item. If there are free capacities, multiple stories can then be scheduled in parallel. The focus here would be completing stories end-to-end, from design through testing, in the shortest possible time.

Last modified on Mar 30, 2020

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

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