Chart: Backlogs
mr.frrxtnee
pm490_v2_wk4_backlogs.docxPM/490 v2
Backlogs
PM/490 v2
Page 2 of 2
![]()
Backlogs
Complete the Product Backlog and Sprint Backlog sections. Refer to the Project Scope document and your completed WBS from Week 2 to complete these sections. Examples are in italics. Delete the examples prior to submission.
Part 1: Product Backlog
Use the WBS you completed in Week 2 to create the product backlog.
· In the WBS ID column, list the ID assigned to the product/deliverable.
· In the Product/Deliverable column, list at least 5 Level 2 deliverables that align with items in one or more levels of the WBS.
· In the Priority column, identify the priority level of each deliverable based on the business input. Label as High-1, Medium-2, or Low-3.
· In the Status column, identify the deliverable as not started, in progress, or complete.
· Not Started: The team has not started work on the deliverable.
· In Progress: The team is currently working on the deliverable.
· Complete: This deliverable has been completed.
Note: At this time of the project, it is estimated that 25% of the deliverables have not been started, 50% are in progress, and 25% have been completed.
· In the Estimated Hours column, estimate the time to complete the deliverable based on what is identified in the WBS at Level 2.
Product Backlog
|
WBS ID |
Product/Deliverable |
Priority (High-1, Medium-2, Low-3) |
Status (Not Started/In Progress/Complete) |
Estimated Hours |
|
1.1 |
Frame Set |
1 |
Not started |
40 |
|
1.2 |
Braking System |
1 |
Not started |
8 |
|
1 |
|
|
|
|
|
2 |
|
|
|
|
|
3 |
|
|
|
|
|
4 |
|
|
|
|
|
5 |
|
|
|
|
Part 2: Sprint Backlog
Use the stakeholder register and WBS from Week 2 to complete this section. Edit the number of rows as needed. Examples are in italics. Delete the examples prior to submission.
· In the Description of Feature/User Story column, describe, in approximately 2–10 words, the task associated with the deliverable for at least 2 tasks. There should be at least 7 rows completed.
Note: This is the sub-component in the WBS that is required to be delivered in the current sprint. This may have been called the product/deliverable when working with the waterfall methodology. This may also be known as epics, features, or stories, depending on the software you’re using.
· In the Responsible Party column, list the team member or role assigned to complete the deliverable. This is based on the stakeholder matrix in the Project Scope document.
· In the Status column, identify if the task is defined, in progress, tested, or accepted.
· Defined: The deliverable has been discussed, and the work required to deliver it has been clarified.
· In Progress: The work is underway for completing the deliverable.
· Tested: The work is completed, and testing is underway.
· Accepted: The deliverable was presented to the customer, who has accepted it and signed off on it as meeting requirements; no further work is required on the deliverable.
Sprint Backlog
|
ID # |
Description of Feature/User Story |
Responsible Party |
Status (Defined, In Progress, Tested, Accepted) |
|
example 1 |
Develop Bike Pedal design |
Kristen |
In Progress |
|
1a |
Finalize conceptual art |
Casey |
In Progress |
|
1b |
Select manufactures |
Brianne |
In Progress |
|
1c |
Research material options |
Steve |
In Progress |
|
1d |
Develop prototype |
James |
Defined |
|
1 |
|
|
|
|
1a |
|
|
|
|
1b |
|
|
|
|
1c |
|
|
|
|
1d |
|
|
|
|
2 |
|
|
|
|
2a |
|
|
|
|
2b |
|
|
|
|
2c |
|
|
|
Copyright 2025 by University of Phoenix. All rights reserved.
Copyright 2025 by University of Phoenix. All rights reserved.
