PM FPX 4080 Assessment 2 Sprint Plan example

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

This PM FPX 4080 Assessment 2 sample paper is a sprint plan for the online appointment booking feature, running goal first, capacity second and commitment third. It belongs to Capella PM FPX 4080, Agile Project Management, which students in the BS in Business, Project Management take as PM-FPX4080. The paper sets a sprint goal the sprint can be judged against and lets the team set its own capacity. It shows items pulled by the team rather than pushed onto it and prints the definition of done. It lays out the sprint backlog, shows scope moving before the date does, keeps roles where Scrum puts them and schedules the sprint events.

CoursePM FPX 4080 Agile Project Management
AssessmentAssessment 2
Paper typeSprint plan
LengthAbout 1,130 words, 6 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramBS in Business, Project Management
UpdatedSeptember 2026

Free sample paper for PM FPX 4080 Assessment 2

1

Planning a Sprint for Online Appointment Booking: A Goal the Sprint Can Be Judged Against, Capacity Set by the Team, Items Pulled Not Pushed, the Definition of Done Printed, Scope Moving Before the Date, and Roles Kept in Place

Student Name

Capella University

PM FPX 4080: Agile Project Management

Instructor Name

Month Day, Year

What this part is doingThe title names the sprint and the plan's features. Sprint planning papers are judged on goal and team ownership, so both lead.
2

The Team and the Sprint

Petline Software's booking team has a product owner, a Scrum Master, and five developers, including one tester. Sprints last two weeks. Sprint 1 runs from March 3 to March 14. The team's average velocity over its last four sprints on other work was 26 points.

A Goal the Iteration Can Be Judged Against

Sprint goal: a pet owner at a pilot clinic can see available times and book a routine appointment, and the booking appears in the clinic's schedule without double-booking. At the end of the sprint, the goal is either met or not, which makes it useful for judging the sprint. The Scrum Guide describes the sprint goal as the single objective for the sprint, giving the developers focus and flexibility in how they reach it (Schwaber & Sutherland, 2020).

Capacity Set by the Team

The developers set capacity, not the product owner or a manager. One developer has two days of planned leave, and the team has a half-day company meeting. Taking these into account, the developers agreed to plan for about 22 points rather than their average of 26. They also noted that PB5, the scheduling integration, involves code none of them has touched recently, so they preferred to leave some slack. Capacity set by the people doing the work is a forecast. Capacity set by someone else is a hope.

What this part is doingThe team determines its own capacity with reasons. Scorers reward plans that respect team ownership of capacity.
3

Items Pulled, Never Pushed

The product owner presented the top of the backlog: PB1, see available times, 5 points; PB2, book for a pet and reason, 5 points; PB3, clinic chooses appointment types, 3 points; PB5, booking appears in the schedule without double-booking, 8 points; PB4, confirmation messages, 3 points. The developers pulled PB1, PB2, PB3, and PB5, totaling 21 points, because together they meet the sprint goal. They did not pull PB4, which would bring the total to 24, above their capacity. The product owner accepted this. The product owner did not assign items to individuals; the developers decided among themselves who would start on each.

The Definition of Done Printed

The definition of done, which applies to every item, is printed in the plan so no one has to remember it. Code reviewed by at least one other developer. Automated tests written and passing for the item's acceptance criteria. No known defects of severity 1 or 2 open. Works in the two supported browsers and on mobile screens. Deployed to the staging environment used by pilot clinics. Product owner has reviewed the item against its acceptance criteria. An item that meets its acceptance criteria but not the definition of done is not done.

What this part is doingThe definition of done is listed in full. Scorers reward plans that make "done" explicit.
4

The Sprint Backlog

The developers broke the four items into tasks during planning, such as building the availability query, designing the booking screen, and writing the double-booking lock. These tasks are the developers' own plan and may change during the sprint.

Scope Moves Before the Date Does

If the team finds during the sprint that it cannot finish all four items, the sprint end date does not move. Instead, the team and product owner discuss what to drop while still meeting the goal. For example, PB3, clinic control of appointment types, could be simplified to one hard-coded appointment type for the pilot, preserving the goal while reducing work. Only if the goal itself becomes impossible would the product owner consider canceling the sprint. The sprint's length is fixed so that the team learns its real pace. Moving the date hides it.

Roles Kept Where the Method Puts Them

The product owner owns the backlog and its ordering and decides what is valuable; she does not tell developers how to build it. The developers own the sprint backlog and how the work is done. The Scrum Master facilitates events and removes impediments, such as getting access to the scheduling engine's test environment, which the team flagged as a risk; she does not assign work. A department manager asked to attend planning to "make sure the team commits to enough," and the Scrum Master explained that capacity is the developers' decision, inviting the manager to the sprint review instead.

What this part is doingRoles are described with an example of protecting them. Scorers reward plans that keep Scrum roles distinct.
5

Sprint Events Scheduled

Events are scheduled for the full sprint: sprint planning on March 3, limited to four hours for a two-week sprint; a 15-minute daily scrum at 9:30 a.m. for the developers; backlog refinement for one hour on March 10; the sprint review on March 14 with the product owner, pilot clinic managers, and the department manager; and the retrospective the same afternoon. Holding the review with pilot clinic managers means the team hears real users' reactions at the end of the first sprint.

How the Sprint Serves the Product Goal

The product goal for three months is online booking that clinics control. This sprint delivers the smallest part of that goal that a pilot clinic can try. Later sprints add confirmations, login, booking limits, and cancellation. If the pilot clinics find a problem with the first version, the product owner can reorder the backlog before Sprint 2, which is the reason for delivering something usable early.

What Stakeholders Will See at the Review

At the sprint review, the team will demonstrate a pet owner booking an appointment at a pilot clinic's staging site and the booking appearing in the clinic schedule. Pilot clinic managers will be asked to try booking themselves and to say whether they would turn the feature on. Their feedback goes into the backlog before Sprint 2 planning, and the product owner will reorder items if needed.

If the Team Finishes Early

If the developers finish the four items early, they may pull PB4, confirmation messages, from the top of the backlog after checking with the product owner. They will not pull work that does not serve the product goal, and they will use any remaining time to improve test coverage on the scheduling integration, which the team identified as fragile.

Risks for This Sprint

Access to the scheduling engine's test environment and the unfamiliar code in PB5 are the main risks. The Scrum Master will confirm access on day one, and two developers will pair on PB5 so that knowledge of the scheduling code is shared within the team.

Conclusion

Sprint 1 has a goal that can be judged, capacity of about 22 points set by the developers, 21 points pulled to meet the goal, a printed definition of done, a plan to adjust scope rather than the date, and roles kept where Scrum places them.

6

References

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

Reading the PM-FPX4080 Assessment 2 instructions

Assessment 2 in PM FPX 4080 has you plan a sprint from the backlog in Assessment 1. You state the sprint goal, set capacity from the team's availability and past velocity, select items the team can complete, break them into tasks, state the definition of done, explain how the plan will respond if work runs over, describe the roles of product owner, Scrum Master and developers, and schedule the sprint events. When time is fixed, scope is what flexes, and the plan should say which items would be dropped first. The Scrum Guide and agile planning texts support the plan.

How the PM-FPX4080 Assessment 2 example is put together

The example runs goal first, capacity second, commitment third, and that order is the argument. It opens by stating the iteration goal, because a set of items with no unifying purpose cannot be traded against anything when the iteration gets tight. Capacity comes next and is derived from the team's own recent completion rate and its availability, stated openly, so the commitment has a ceiling that came from evidence. The committed items follow in the backlog's order, each with its size and a sentence on why it serves the goal, and the running total stays under the ceiling. Task breakdown sits below the items and stays the team's work rather than the writer's assignment. A ceremony section covers the daily check, the review and the retrospective. The plan closes with the risks to the goal and what the team would drop first.

PM FPX 4080 Assessment 2 scoring guide: what Distinguished looks like

Marks in this assessment go to the goal, the capacity, the selection, the definition of done, the handling of overruns, the roles and the events. The goal reaches Distinguished when it unifies the items so trade-offs can be made. Capacity scores higher when set by the team from availability. Selection earns credit when items are pulled by the team. The definition of done is judged on whether it is printed and specific. Overruns should be handled by moving scope, not the date. Roles should match the Scrum Guide, with the product owner owning the order and the developers owning the plan. Distinguished plans show a team that owns its commitment.

PM FPX 4080 Assessment 2 help: mistakes that cost marks

Sprint plans often fill the sprint to a manager's target rather than the team's capacity. Another weakness is a goal that restates the list of items. The definition of done is assumed. Tasks are assigned to named people at planning, which undercuts self-organization. Overruns are handled by extending the sprint. Roles blur, with the product owner directing daily work and the Scrum Master acting as a task manager. Deriving capacity from each person's available days, then pulling items until it is used, and writing the goal as one outcome, keeps the plan honest and sets up the retrospective in Assessment 3.

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

Send the Assessment 2 instructions and the scoring guide from your PM FPX 4080 courseroom, plus the backlog or scenario your section works from. We build a custom example to those criteria, with a stated goal, team-derived capacity and no dates hiding inside the items, 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 2 questions, answered

What does the sprint plan do about a fixed deadline?

It holds the date and moves the scope, which is the trade the method makes. If the goal cannot be met inside the iteration, items come out rather than the end point moving. Say so in the plan and name what leaves first. A plan that extends the iteration to fit the work has stopped being adaptive.

Should tasks be assigned to named people in the plan?

No, and doing it is one of the visible tells. Items are broken into tasks during planning, and members take them up as the iteration runs, which is what keeps the team collectively accountable for the goal. Naming an owner for every task in advance recreates the hierarchy the method removed and usually costs the practice criterion.

How do I set capacity for a team that has no history?

State the assumption and show the reasoning. A first iteration commits conservatively, notes that the rate is unknown, and says the number will be corrected once real completion data exists. That is honest and it scores. Inventing a rate and presenting it as established is what loses credit, since the whole point of the method is measuring rather than predicting.

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

This page shows the complete booking sprint plan, with a sprint goal, capacity set by the team, items pulled not pushed, the definition of done printed and scope moving before the date.

What is a definition of done in PM FPX 4080 Assessment 2?

A shared checklist every item must meet before it counts as finished, such as code reviewed, tested and deployed to a test site. It prevents half-finished work being reported as done.