ステージとスキル
This page refers to Portfolio classic plans. If you are currently running Portfolio 2.0, please check this link to access the latest page version.
ステージ
Stages represent different activities required to deliver a work item. Typically, stages are used for activities that need to be done sequentially per work item.
A typical example for stages in a Scrum team that is using hours/day estimation could be:
- Story writing (responsible: Product Owner)
- Implementation (done by the cross-functional Scrum team)
Intuitively, this means that a story needs to be written, before the implementation of it can be done.
Another likely setup could be:
- Design
- 実装
- テスト
In this configuration, the testing effort is planned separately after the implementation of an individual story is completed.
Skills
Skills can be defined per stage and allow to categorize different types of work within a stage.
Example: within a design stage, one activity could be UI design, another one could be technical/architecture design. In an implementation stage, skills could be used to distinguish different technology expertise like web/frontend development, data management, etc.
Tip: Use skills for those cases where they potentially cause bottlenecks in planning, i.e., if you have specializations among your team members and need to make sure that the capacity plan is realistic in terms of who is planned for which work items.
Sample scenarios
In the following sections you'll see different scenarios examples:
Stages and skills with story points
Scrum methodology doesn't recognize the idea of Stages and Skills. However, if you work with story points and would like to use stages and skills for fine grained capacity planning, this is fully supported by Portfolio for JIRA. The only assumption that needs to be made is that every team member contributes equally to the team's velocity. See Settings estimates with story points for more information.