It can be used to estimate a team’s ability to complete work by a particular milestone and is invaluable for evaluating risk when making key decisions.Ĭapacity is added to the plan by team and domain leads who regularly assess their team’s availability, resource allocation, and the prioritization of other projects. Watch nowĬapacity reveals the units of work that a team undertakes in a given period of time. For more information about configuring and customizing your hierarchy levels, click here to learn more.įor tips and best practices on configuring the issue hierarchy above epics in Advanced Roadmaps, check out this short video. When positioned above the epic level, the initiative can be used as a container for epics. For example, you can create an initiative hierarchy level to represent company-wide goals. If you plan and track work across an organization, you’ll need to create hierarchy levels above epics.
In Advanced Roadmaps, subtasks can’t have teams assigned specifically to them, they inherit the team assigned to the parent issue. Subtask - A granular piece of work required to complete a story, task, or bug.These issue types can be assigned to specific teams. Bugs are problems that impede the progress or functionality of work. Story, task, or bug - Stories and tasks are issues that represent work that needs to be completed.The work contained in an epic can be assigned across multiple teams. In a plan, epics represent a significant milestone or deliverable. Epic - A large body of work that can be broken down into stories, tasks, and bugs.The hierarchy in Advanced Roadmaps is inherited from the default issue types in Jira Software: Depending on how your work is structured, hierarchy levels represent different levels of detail in a plan’s scope and show how they’re related. A hierarchy connects small, process-based tasks to cross-functional deliverables and escalates them to broad organizational objectives.
0 kommentar(er)
