| Course | BU 433 Agile Project Management |
|---|---|
| Unit | Unit 3 |
| Paper type | Backlog with prioritization basis |
| Length | About 750 words, 5 pages |
| Format | APA 7 student paper |
| School | Herzing University |
| Program | BS in Project Management |
| Updated | September 2026 |
Free sample paper for BU 433 Unit 3
A Sandbox Test Before Any Screen: A Backlog With Prioritization Basis for Renting Storage Units Online at a Composite Kansas Chain, Ordered by Cost of Delay and Dated as Provisional
Student Name
Business, Herzing University
BU 433: Agile Project Management
Instructor Name
February 11, 2026
A Sandbox Test Before Any Screen: A Backlog With Prioritization Basis for Renting Storage Units Online at a Composite Kansas Chain, Ordered by Cost of Delay and Dated as Provisional
The Backlog and What It Rests On
This is the product backlog for online move-in at Prairie Vault Storage, the composite self-storage chain with 11 facilities in Kansas and Missouri used throughout this course, as of February 11, 2026. It holds 14 items in a single order. The product owner, the director of operations, owns that order; the team supplies sizes and warns about technical dependencies. In Scrum the backlog is never finished, and ordering it is the product owner's job (Schwaber & Sutherland, 2020), and this document records both the order and the reasoning behind it so the reasoning can be challenged.
The order rests on cost of delay divided by size, a rule Reinertsen (2009) argues maximizes the value delivered over time when work competes for the same people. Leffingwell (2011) turned it into a practical score, weighted shortest job first, in which cost of delay is the sum of three judgments: value to the renter or company, time criticality and risk reduction. Each is scored from 1 to 10 by the product owner, and the team's size estimate, in story points, divides the total. The score is a starting point, not the final order; three adjustments for dependencies are stated after the table.
Scores
Items are listed here in score order. The value, time and risk columns are the product owner's judgments; sizes for the lower items are rough and marked as such.
| Item | Value | Time | Risk | Cost of delay | Size | Score |
|---|---|---|---|---|---|---|
| B. Gate vendor sandbox test | 1 | 8 | 10 | 19 | 2 | 9.5 |
| A. Unit availability and price on facility pages | 8 | 5 | 2 | 15 | 3 | 5.0 |
| I. Follow-up email for abandoned rentals | 5 | 3 | 1 | 9 | 2 | 4.5 |
| G. Manager's morning dashboard | 5 | 6 | 2 | 13 | 3 | 4.3 |
| F. Gate code by text | 9 | 7 | 3 | 19 | 5 | 3.8 |
| C. Card payment and unit hold | 8 | 6 | 4 | 18 | 5 | 3.6 |
| D. Lease signing with approved version | 9 | 7 | 5 | 21 | 8 | 2.6 |
| H. Save progress for 24 hours | 4 | 2 | 1 | 7 | 3 | 2.3 |
| E. Identity check by license photo | 6 | 5 | 6 | 17 | 8 | 2.1 |
| K. Unit size comparison guide | 3 | 2 | 1 | 6 | 3 (rough) | 2.0 |
| M. Autopay enrollment at move-in | 5 | 1 | 1 | 7 | 5 (rough) | 1.4 |
| N. Protection plan offered at checkout | 6 | 2 | 2 | 10 | 8 (rough) | 1.3 |
| J. Unit photos | 3 | 1 | 1 | 5 | 5 (rough) | 1.0 |
| L. Spanish-language version | 4 | 2 | 1 | 7 | 13 (rough) | 0.5 |
Three Adjustments and the Final Order
Pure score order would build a follow-up email and a manager's dashboard for a move-in process that does not yet exist. Three adjustments fix that, each stated so it can be questioned.
First, the sandbox test stays at the top on its score and on its own merits. The gate vendor's interface is the largest unknown in the project; if its sandbox behaves differently from the vendor's documentation, the team needs to know in February, not in April. It delivers nothing a renter sees, which is exactly why a value-only ordering would have buried it.
Second, the smallest releasable flow is moved up as a block. A renter at the pilot facility needs to see a unit (A), pay (C), sign (D) and get in (F). Those four move ahead of the dashboard and follow-up email even though two of them score lower, because none of the four has any value until all four exist. Lease signing is also bound to a date: counsel's approval is due in March, and the item is placed so it can be built against a draft in late February and switched on when approval arrives.
Third, the identity check drops below the dashboard. The pilot facility can launch with the manager reviewing every online rental before a code is issued, which Story 2a's flag already supports. That manual step costs about ten minutes per rental and buys time to build the photo check properly.
| Order | Item | Refinement |
|---|---|---|
| 1 | B. Gate vendor sandbox test | Ready: criteria written, sized |
| 2 | A. Availability and price | Ready |
| 3 | C. Card payment and hold | Ready |
| 4 | D. Lease signing | Ready; release waits for counsel |
| 5 | F. Gate code by text | Ready; release waits for vendor |
| 6 | G. Manager's dashboard | Sized; criteria drafted |
| 7 | I. Abandoned rental email | Sized; criteria drafted |
| 8 | E. Identity check | Sized; vendor not chosen |
| 9 | H. Save progress | Sized |
| 10 | K. Size comparison guide | One line |
| 11 | M. Autopay enrollment | One line |
| 12 | N. Protection plan | One line |
| 13 | J. Unit photos | One line |
| 14 | L. Spanish version | One line |
Why the Bottom Is Left Rough
The top five items carry full stories, acceptance criteria and team sizes, because they will be built in the next two or three sprints. Items six to nine have sizes and draft criteria. The last five are one-line entries with rough sizes, and that is deliberate. Whether renters want unit photos or a Spanish version will be clearer after the pilot facility has run for a month; detailed stories written now would describe guesses and would need rewriting. Refinement effort goes where it will be used soon.
The lower items also show where the product owner's judgments are least certain. The protection plan scores a value of 6 because it earns revenue on every rental that adds it, but the company has not decided whether to offer it online at all. If the owners decide yes, time criticality rises before the summer, and the item may move into the top ten.
How Long This Order Holds
This backlog is dated and provisional. It will be reordered at every sprint review, and three events would reorder it sooner: the sandbox test failing, counsel's approval slipping past March, or the pilot facility showing a large share of renters abandoning at one step. The score table is kept with the backlog so that anyone who disagrees with the order can see which judgment to argue with. The company, its items and every score here are composites for this course.
References
Leffingwell, D. (2011). Agile software requirements: Lean requirements practices for teams, programs, and the enterprise. Addison-Wesley.
Reinertsen, D. G. (2009). The principles of product development flow: Second generation lean product development. Celeritas.
Schwaber, K., & Sutherland, J. (2020). The Scrum guide: The definitive guide to Scrum: The rules of the game. https://scrumguides.org/scrum-guide.html
BU 433 Unit 3 instructions, in plain terms
The third unit of BU 433 asks students to build a product backlog and justify its order. Common requirements are a single ordered list of items, a stated prioritization method such as MoSCoW, value versus effort or weighted shortest job first, an explanation of dependencies and risk, and a note on who owns the order. Many instructors expect the top items to be more detailed than the lower ones and ask students to explain why. Scores or ratings are welcome when their inputs are visible. The backlog should be recognizably provisional, since it will change after each sprint. A typical submission is a few APA 7 pages built around one or two tables, and it should make any single position easy to challenge.
How this BU 433 Unit 3 example is built
The sample begins by dating the backlog, naming the product owner as the person accountable for the order and explaining the cost-of-delay method. A score table lists all 14 items with value, time criticality, risk reduction, size and score. The next section describes three adjustments to the score order, each with a reason: the sandbox test stays first because it retires the largest unknown, the minimum flow moves up because its parts have no value alone, and the identity check drops because manual review covers the pilot. A final order table shows each item's level of refinement. The paper then explains why lower items are left rough and closes with three events that would reorder the list early.
BU 433 Unit 3 rubric: what full points look like
Backlog rubrics usually reward a clear single order, a stated and consistently applied prioritization method, attention to dependencies and risk, appropriate levels of detail and professional presentation. The ordering criterion expects one sequence rather than groups of equal priority. The method criterion earns full points when inputs are visible and the student explains any departure from them. Dependencies and risk score highest when the paper shows how technical or external constraints changed the order. The detail criterion rewards refining near-term items while leaving distant ones coarse, with a reason. Instructors also credit papers that identify who owns the order and when it will change, since a backlog presented as final misunderstands its purpose.
BU 433 Unit 3 help before you submit
A frequent mistake in backlog papers is presenting items grouped as high, medium and low, which is a list of categories rather than an order. Another is using a scoring method but then silently ignoring it. Students often prioritize by value alone and bury risk-reducing work, such as testing an unfamiliar integration, until it is too late to react. Some backlogs detail every item equally, wasting effort on features that may never be built. Others present the order as fixed. Many papers forget dependencies, placing an item that cannot be released until another exists. Finally, a backlog without a stated owner leaves unclear who resolves disagreements, which instructors tend to question.
Get a BU 433 Unit 3 example written to your instructions
Send the Unit 3 instructions and the BU 433 rubric from your classroom, plus the stories or scenario the assignment builds on. We write a custom example that orders into one sequence, weighs value against uncertainty, concentrates detail at the top, argues the basis in prose and dates the list as provisional. First custom sample free, back in 24 to 48 hours.
More BU 433 papers and project management samples
- BU 433 Unit 1: Agile principles and fit analysis
- BU 433 Unit 2: User stories with acceptance criteria
- BU 433 Unit 4: Estimation exercise
- BU 433 Unit 5: Sprint plan
- BU 433 Unit 6: Ceremony analysis
- BU 433 Unit 7: Retrospective with a committed change
- BU 433 Unit 8: Hybrid or scaling analysis
- BU 345 Unit 3: Scope and work breakdown document
- BU 396 Unit 3: Qualitative analysis and scoring
- BU 436 Unit 3: Decision rights and escalation
- BU 442 Unit 3: Work breakdown and durations
BU 433 Unit 3 questions, answered
How is a backlog different from a work breakdown?
In what it is for. A breakdown decomposes an agreed scope into everything that must be done, and completeness is the point; a backlog orders what is currently worth doing, expects items to be added and dropped, and is never complete. One is measured against a total, the other against what comes next. Writing the backlog as a decomposed tree is how this assignment usually goes wrong.
Should the backlog carry estimates?
Only where the instructions ask, and it is worth checking, since sizing is often the next unit. Where sizes are wanted, keep them coarse and attach them only to the refined items at the top, because sizing something described in one line produces a number with nothing behind it. The ordering argument is what this unit is graded on.
Who decides the order?
In the model the course teaches, one person holds that decision and takes input from everybody else, which is what stops an order settled by negotiation among stakeholders. In the assignment you are writing as that person, so state the perspective you are ordering from and whose interests you are weighing, and say where you would expect an argument.
Where can I find a free BU 433 Unit 3 sample paper?
The BU 433 Unit 3 backlog with prioritization basis is published above free of charge, with the score table, the final ordered list and margin notes. If your product or method differs, send your prompt and a custom backlog is drafted for you at no cost, typically in two days.
Which prioritization method works for BU 433 Unit 3?
Any method whose inputs are visible and applied consistently. The sample uses weighted shortest job first, cost of delay divided by size, then states three adjustments for dependencies so every departure from the score can be questioned.