Product Backlog Work Breakdown Structure
Use immediately

Product Backlog Work Breakdown Structure

PROJECT JEM

Source

Exterior

Interior

Certify

1.1 Task

1.2 Task

1.3 Task

2.1 Task

2.2 Task

2.3 Task

3.1 Task

3.2 Task

3.3 Task

4.1 Task

4.2 Task

4.3 Task

1.1.1 Subtask

1.1.2 Subtask

1.1.3 Subtask

1.1.4 Subtask

1.2.1 Subtask

1.2.2 Subtask

1.2.3 Subtask

1.3.1 Subtask

1.3.2 Subtask

2.1.1 Subtask

2.1.2 Subtask

2.1.3 Subtask

2.1.4 Subtask

2.2.1 Subtask

2.2.2 Subta...

2.2.3 Subta...

2.3.1 Subtask

2.3.2 Subta...

3.1.1 Subtask

3.1.2 Subtask

3.1.3 Subtask

3.1.4 Subtask

3.2.1 Subtask

3.2.2 Subta...

3.2.3 Subta...

3.3.1 Subtask

3.3.2 Subta...

4.1.1 Subtask

4.1.2 Subtask

4.1.3 Subtask

4.1.4 Subta...

4.2.1 Subtask

4.2.2 Subtask

4.2.3 Subtask

4.3.1 Subtask

4.3.2 Subtask

WorkBreakdown Structure (WBS)-Product Backlog

Product Backlog

STORY 1

STORY 2

STORY 3

STORY 4

STORY 5

STORY 6

STORY 7

STORY 8

STORY 9

High Priority

Medium Priority

12
0
1
publish time: 2021-07-01
Kiraaaa

The product backlog serves as the foundation for iteration planning. All work items should be included in the backlog: user stories, bugs, design changes, technical debt, customer requests, action items from the retrospective, etc. This diagram has four levels. First level is the project JEM. Second level is project JEM has been divided into 4 category- Source, Exterior, Interior & Certify. These sub categories are breakdown/branched into different tasks. And lastly the breakdown of tasks into subtasks. This diagram also tells us that from story 1 to 6 has high priority and story 7 to 9 has medium priority. EdrawMax allows its user to study similar diagrams from the already available templates.

See More Related Templates