PM FPX 4080 Assessment 1 Product Backlog example

Reviewed by Rupert Danvers, MBA Agile Project Management Capella University Free custom sample in 24 to 48h

This PM FPX 4080 Assessment 1 sample paper is a product backlog for an online appointment booking feature at a veterinary practice, written and ordered the way an agile team would use it. It was written for Capella PM FPX 4080, Agile Project Management, a course in the BS in Business, Project Management, with the catalog code PM-FPX4080. The paper states the product and its goal, then writes each item from the user's side and argues the ordering from value. It concentrates detail at the top of the backlog, sizes items relatively in story points and puts acceptance criteria on the top items. It explains how the backlog was built, sets a refinement cadence and leaves out dates and assignees.

CoursePM FPX 4080 Agile Project Management
AssessmentAssessment 1
Paper typeProduct backlog
LengthAbout 1,120 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramBS in Business, Project Management
UpdatedSeptember 2026

Free sample paper for PM FPX 4080 Assessment 1

1

A Product Backlog for Online Appointment Booking: Items Written From the User's Side, Ordering Argued From Value, Detail Concentrated at the Top, Relative Sizing, Acceptance Criteria on the Top Items, and No Dates or Assignees

Student Name

Capella University

PM FPX 4080: Agile Project Management

Instructor Name

Month Day, Year

What this part is doingThe title names the backlog and its features. Backlog papers are judged on user focus and ordering, so both lead.
2

The Product and Its Goal

Petline Software, a composite company, sells practice management software to about 600 small animal clinics. Clinics have asked for a way for pet owners to book appointments online, which two competitors already offer. The product goal for the next three months is: pet owners can book a routine appointment online with their clinic, and clinics can control which appointment types and times are offered. The Scrum Guide describes the product backlog as an ordered list of what is needed to improve the product, managed by the product owner (Schwaber & Sutherland, 2020).

Items Written From the User's Side

Items are written as user stories, describing what a user needs and why, rather than as technical tasks. PB1: As a pet owner, I want to see available appointment times for my clinic so that I can choose one that fits my schedule. PB2: As a pet owner, I want to book an appointment for a specific pet and reason so that the clinic knows what to prepare. PB3: As a clinic manager, I want to choose which appointment types can be booked online so that complex visits are still booked by staff. PB4: As a pet owner, I want a confirmation text and email after booking so that I know it worked. PB5: As a front desk staff member, I want online bookings to appear in the schedule immediately so that I do not double-book. PB6: As a pet owner, I want a reminder the day before so that I do not miss the appointment. PB7: As a pet owner, I want to cancel or reschedule online so that I do not have to call. PB8: As a clinic manager, I want to set how far ahead and how close to the time bookings are allowed so that the schedule stays manageable. PB9: As a pet owner, I want to log in with the same account I use for the pet portal so that I do not need another password. PB10: As a clinic manager, I want a report of online bookings by week so that I can see whether the feature is used. PB11: As a pet owner, I want to request a specific veterinarian so that my pet sees someone familiar. PB12: As a pet owner, I want to pay a deposit when booking so that clinics with high no-show rates can use the feature. A story written from the user's side keeps the team asking what the user needs, not what the code needs.

What this part is doingEach item names a user, a need, and a reason. Scorers reward backlogs written from the user's perspective.
3

Ordering Argued From Value

The order is argued from value. PB1, PB2, PB3, and PB5 come first because together they make the smallest usable feature: an owner can book, and the clinic controls what is offered and sees bookings immediately. Without PB3 and PB5, no clinic would switch the feature on, because staff would lose control or face double bookings. PB4 follows because owners need to know the booking worked. PB9 comes next, because a separate login would reduce use. PB8 and PB7 follow, since clinics asked for booking limits and owners expect to cancel online. PB6, reminders, is lower because clinics already send reminders through another part of the software. PB10, PB11, and PB12 are last: useful, but not needed for the first release. PB12, deposits, is lowest because it requires payment processing work that is not yet planned.

Detail Concentrated at the Top

The top items have detail; lower items do not. PB1, PB2, PB3, and PB5 have acceptance criteria and have been discussed with three pilot clinics. PB4 and PB9 have notes but no acceptance criteria yet. Items from PB6 down are one-line stories that will be refined when they approach the top. Spending time detailing PB12 now would be wasted if priorities change.

Relative Sizing, Not Converted Hours

The team sized items in story points using relative comparison, with PB4, confirmation messages, as the reference at 3 points. PB1: 5. PB2: 5. PB3: 3. PB5: 8, because it touches the scheduling engine. PB4: 3. PB9: 5. PB8: 3. PB7: 5. Items below are not yet sized. Points are not converted to hours, because their purpose is to compare items and to plan with the team's velocity, not to estimate time for each item.

What this part is doingItems are sized relative to a reference item. Scorers reward relative estimation without hour conversion.
4

Acceptance Criteria on the Top Items

PB1: Given a clinic with online booking enabled, when a pet owner opens the booking page, then available times for the next 14 days appear for enabled appointment types only, and times already booked do not appear. PB2: Given a logged-in owner with two pets, when the owner selects a time, then the owner must choose a pet and an appointment reason before confirming. PB3: Given a clinic manager, when the manager unchecks an appointment type in settings, then that type no longer appears to owners within one minute. PB5: Given a booking is confirmed, then it appears in the clinic's schedule within 10 seconds, and the same time cannot be booked by staff or another owner.

How the Backlog Was Built

The product owner built the backlog from three sources: requests logged by clinics in the support system over the past year, interviews with managers at three pilot clinics, and a review of competitors' booking features. Pilot clinic managers were clear that they would not turn on online booking unless they could limit which appointments owners could book, which is why PB3 sits near the top. Owners' needs were drawn from a short survey sent through the pet portal, which 410 owners answered.

Refinement Cadence

The team spends about one hour a week refining the backlog with the product owner, adding detail and acceptance criteria to items as they approach the top and splitting items too large to finish in a sprint. PB12, deposits, will likely be split into smaller stories when it rises, since payment processing touches several systems.

No Dates and No Assignees

The backlog shows no dates or assignees. When items are done depends on the team's pace, and who does them is decided by the developers during the sprint. Adding dates would turn the backlog into a schedule the team did not commit to.

Conclusion

The backlog lists twelve user stories, ordered so that the first four make a usable feature clinics will turn on. Detail and acceptance criteria are concentrated on the top items, sizing is relative to a reference story, and dates and assignees are left out.

5

References

Schwaber, K., & Sutherland, J. (2020). The Scrum guide: The definitive guide to Scrum: The rules of the game. Scrum.org.

What the PM FPX 4080 Assessment 1 instructions ask for

The first assessment in PM FPX 4080 asks you to create a product backlog. You describe the product, its users and its goal, write backlog items, usually as user stories in the form "as a user, I want, so that," order them by value, risk, dependency and effort, estimate them with relative sizes, add acceptance criteria to the highest items and explain how the backlog will be refined. Items lower in the backlog can stay rough, since they will be refined when they rise. Dates and named assignees do not belong in a backlog. The Scrum Guide and agile texts on backlog management support the work.

How the PM-FPX4080 Assessment 1 example is put together

The example is ordered by value and refined by depth. It opens with the product and the users, briefly, because items written for an unnamed user turn into feature requests. A short section states the ordering basis: business value, risk reduction, dependency and effort, and says how those were traded against each other. The backlog itself follows in rank order, and the top group carries full detail with acceptance criteria while the lower group deliberately does not. A sizing section explains the relative scale, names the reference item and states plainly that points are not hours. A refinement section describes when items move up and get broken down, which is the part that keeps the artifact alive. The document closes by naming what was left off the list and why, since an ordered backlog is a set of decisions about what is not being built yet.

Where the marks sit in the PM FPX 4080 Assessment 1 scoring guide

Capella's scoring guide rates the product goal, the items, the ordering, the sizing, the acceptance criteria and the refinement plan. The goal reaches Distinguished when it names the users and the outcome, like pet owners booking without phoning. Items score higher when written from the user's point of view with a reason. Ordering earns credit when the basis is stated and applied, not just shown as a list. Sizing is judged on whether it uses relative points consistently rather than disguised hours. Acceptance criteria should be testable on the top items. Detail should thin out lower down. The refinement plan should say when and by whom. Proficient backlogs list features; Distinguished ones show why the first item is first.

PM FPX 4080 Assessment 1 help: mistakes that cost marks

Backlogs often read as feature lists written from the system's side, like "add calendar widget," which lose sight of the user. Another weakness is ordering without a stated basis, so the list looks arbitrary. Every item is written in the same detail, wasting effort on items that may never be built. Story points are converted straight into hours, which defeats relative sizing. Acceptance criteria are missing on the items the team will start next. Dates and names creep in, turning the backlog into a schedule. Stating the ordering rule in two sentences, then writing the top five items in full and the rest briefly, gives the backlog the shape the scorer expects and feeds the sprint plan in Assessment 2.

Get a PM FPX 4080 Assessment 1 example written to your instructions

Send the Assessment 1 instructions together with the scoring guide from your PM FPX 4080 courseroom, plus the product or case scenario your section uses. We write a custom example to those criteria, ordered by value, sized relatively and free of predictive habits, and return it in 24 to 48 hours. First one free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.

More PM FPX 4080 papers and BS in Business, Project Management samples

PM FPX 4080 Assessment 1 questions, answered

Do the items have to be written as user stories?

Check your instructions, since some sections require the standard form and others accept any user-facing statement. What matters to the criterion is that each item names the person who benefits and the benefit itself. A line reading build the reporting module fails whichever format you use, because nobody can tell what it is worth or when it is finished.

How do story points work if they are not hours?

They compare items with each other. One item is chosen as a reference, given a value, and everything else is sized against it for effort, complexity and uncertainty together. The team learns how many points it completes in an iteration, and that observed rate does the forecasting. Converting points to hours in the document reintroduces the estimate the method was built to avoid.

How large should the backlog be?

Large enough to show ordering and refinement, which in most sections means enough items that the top of the list looks different from the bottom. Check any count your instructions set. Depth matters more than volume: a shorter list where the top items carry acceptance criteria and the lower ones are honest epics demonstrates the practice better than fifty uniform lines.

Where can I find a free PM FPX 4080 Assessment 1 sample paper?

A complete backlog for online appointment booking is on this page, with items written from the user's side, ordering argued from value, relative sizing and acceptance criteria on the top items. The sprint plan builds on it.

Why leave dates out of a backlog in PM FPX 4080 Assessment 1?

A backlog is an ordered list of what to build, not a schedule. Dates and names belong to sprint planning, where the team decides what it can take on.