PM FPX 4080 Assessment 3 Retrospective Report example

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

This PM FPX 4080 Assessment 3 sample paper is a retrospective report after a sprint that missed its goal, moving from evidence to cause to commitment. It completes Capella PM FPX 4080, Agile Project Management, in the BS in Business, Project Management, catalog code PM-FPX4080. The paper sets out the sprint facts before any opinions and ties each observation to a real event. It examines causes before choosing remedies, commits to one or two changes with owners and states what the team should keep doing. It looks closely at a daily scrum that kept overrunning, keeps blame out of the record, explains how the meeting was run and carries the result into the next sprint.

CoursePM FPX 4080 Agile Project Management
AssessmentAssessment 3
Paper typeSprint retrospective report
LengthAbout 1,100 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramBS in Business, Project Management
UpdatedSeptember 2026

Free sample paper for PM FPX 4080 Assessment 3

1

A Sprint Retrospective After a Missed Goal: Iteration Facts Before Opinions, Observations Tied to Real Events, Cause Examined Before Remedy, One or Two Owned Changes, What to Keep Stated, and Blame Kept Out of the Record

Student Name

Capella University

PM FPX 4080: Agile Project Management

Instructor Name

Month Day, Year

What this part is doingThe title names the event and its features. Retrospective papers are judged on whether they lead to specific improvement, so owned changes are named.
2

Iteration Facts Before Opinions

The retrospective opened with facts, gathered by the Scrum Master before the meeting. Sprint 1 ran from March 3 to March 14. The sprint goal was that a pet owner at a pilot clinic could book a routine appointment and see it appear in the clinic's schedule without double-booking. The developers pulled four items totaling 21 points. Three items met the definition of done: the availability view (PB1), the pet-and-reason booking step (PB2), and clinic control over bookable visit types (PB3), 13 points in all. The eight-point schedule integration story (PB5) did not: the double-booking lock failed two automated tests. The sprint goal was not met. One defect escaped to the staging environment: available times showed in Coordinated Universal Time instead of the clinic's local time; a pilot clinic manager found it on day 8. Access to the scheduling engine's test environment arrived on day 3, not day 1. Daily scrums averaged 24 minutes against a 15-minute timebox.

Observations Tied to Real Events

Each person then added observations, and the facilitator asked that every observation name a specific event. "Communication was poor" was rewritten as "On day 5, the two developers pairing on PB5 learned from the tester that the scheduling engine locks time slots differently in production, which none of us knew during planning." "We were too optimistic" was rewritten as "We sized PB5 at 8 points without anyone having opened the scheduling engine's code." Other observations: "The pilot clinic manager's report of the time zone defect on day 8 came through the product owner, and it took a day to reach us." "Pairing on PB5 let two people understand the scheduling code by the end of the sprint." An observation without an event is an opinion. An observation with an event is something the team can fix.

What this part is doingEvery observation is tied to a dated, specific event. Scorers reward retrospectives grounded in what happened.
3

Cause Examined Before Remedy

The team examined causes before proposing remedies, asking why PB5 was not done. Because the double-booking lock failed its tests. Why? Because the lock was built on an assumption about how the scheduling engine reserves slots, and the assumption was wrong. Why was it wrong? Because no one on the team had worked with the scheduling engine, and the team could not test against it until day 3. Why did the team commit to it anyway? Because planning treated PB5 as a normal story rather than one with a large unknown. The root cause is committing to work that depends on an unexplored system without first exploring it. The time zone defect had a separate cause: acceptance criteria for PB1 did not mention time zones, and the test data all used one zone.

One or Two Changes, Owned

The team chose two changes, each with an owner. Change 1: before any story that depends on a system the team has not worked with enters a sprint, the team does a short time-boxed exploration, called a spike, in the previous sprint to learn how the system behaves. Owner: the product owner, who will add spikes to the backlog ahead of such stories, with the developers deciding their length. Change 2: the Scrum Master confirms access to every environment the planned items need before sprint planning, not on day one. Owner: the Scrum Master. The team discussed a third change, adding time zone checks to the definition of done, and chose instead to add it to PB1's acceptance criteria and to the test data, since it is specific to scheduling features. Two changes are enough to act on in one sprint; a longer list would dilute attention.

What this part is doingChanges are limited to two, each with an owner. Scorers reward retrospectives that commit to a small number of owned actions.
4

What to Keep, Stated Explicitly

The team named what worked, so it would not be lost. Pairing on the hardest item: by sprint end, two developers understood the scheduling code, which will make PB5 faster next sprint. Involving a pilot clinic manager in staging: she found the time zone defect before any real client saw it. Declining to pull PB4 during planning: had the team taken on 24 points, the miss would have been larger. These will continue.

The Daily Scrum Overrun

The team noted the daily scrum overrun but agreed it was a symptom: much of the extra time went to discussing PB5 problems that belonged in a separate conversation after the scrum. The Scrum Master will end the scrum at 15 minutes and schedule a follow-up for anyone who needs it.

Blame Kept Out of the Record

The record names systems, events, and decisions, not individuals' failures. It says "planning treated PB5 as a normal story," not that any developer misjudged it; it says "the defect report took a day to reach us," not that the product owner was slow. The Scrum Guide describes the retrospective as a way for the team to inspect how the sprint went with regard to individuals, interactions, processes, tools, and its definition of done, and to identify the most helpful changes (Schwaber & Sutherland, 2020). A record that blamed people would make them less willing to raise problems in the next sprint. If the record blames someone, the next retrospective will be quieter.

How the Meeting Was Run

The retrospective lasted 90 minutes, held on the afternoon of the sprint review. The Scrum Master facilitated, asked each person to write observations silently before any discussion so that quieter members were heard, and grouped them on a board. The product owner attended as a team member and was asked the same questions as everyone else. The meeting ended with the two changes written on the team's board, where they stay until the next retrospective checks them.

Carrying the Result Forward

PB5 returns to the top of the backlog, now with the knowledge gained through pairing. The product owner will present the missed goal at the next stakeholder update with the reasons and the changes, so that the pilot clinics hear about the delay from the team rather than discovering it.

Conclusion

Sprint 1 completed 13 of 21 points and missed its goal because the team committed to an item depending on an unexplored system. Facts and dated observations led to a root cause, and the team adopted two owned changes: spikes for unfamiliar systems and environment access before planning. Pairing, pilot clinic involvement, and realistic capacity are kept, and the record describes events without blaming anyone.

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 3 instructions ask for

The final assessment in PM FPX 4080 asks you to report on a sprint retrospective. You present the sprint data, such as committed and completed points and unplanned work, record observations about what helped and what got in the way, examine the causes of the main problems, agree on a small number of changes with owners, state what should continue and explain how the retrospective was run. The report should avoid blaming individuals and should lead to changes the team can actually make in the next sprint. The Scrum Guide and texts on agile retrospectives support the report.

How the PM-FPX4080 Assessment 3 example is put together

The report moves from evidence to cause to commitment, and refuses to skip the middle step. It opens with the iteration data, because a retrospective argued from memory drifts toward whoever speaks loudest. The observation section follows, sorted into what helped and what got in the way, with each entry anchored to an event in the iteration. The analysis section then asks why for the two or three observations that mattered most, which is where a carried-over item stops being bad luck and becomes an unrefined backlog entry. The action section commits to a small number of changes, each owned and each measurable in the next iteration. A section on what to keep protects the practices that worked, since retrospectives that only correct tend to erode good habits. The closing paragraph states how the previous retrospective's action turned out.

Reading the PM FPX 4080 Assessment 3 scoring guide

The scoring guide weighs the data, the observations, the cause analysis, the changes, the keeps and the tone. Data reach Distinguished when they come first, so the discussion rests on facts. Observations score higher when tied to specific events. Cause analysis earns credit when it happens before remedies are chosen. Changes are judged on whether there are only one or two, each with an owner and a way to tell next sprint whether it worked. What to keep should be stated. Tone should be free of blame, describing events and systems rather than the people involved. Distinguished reports produce a change the team will actually notice next sprint.

PM FPX 4080 Assessment 3 help: mistakes that cost marks

Retrospective reports often list a dozen action items, none of which get done. Another weakness is jumping from a problem straight to a fix without asking why it happened. Observations are general impressions. The data are missing, so the discussion reflects whoever spoke most. Blame appears in the record. Nothing is said about what went well, so useful habits are dropped along with the bad ones. Picking the one or two problems that cost the most, asking why at least twice for each, and assigning a single owner to each change keeps the report focused and closes the course with a real improvement loop.

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

Send the Assessment 3 instructions and the scoring guide from your PM FPX 4080 courseroom, plus the iteration data or scenario your section supplies. We write a custom example to those criteria, with causes examined and one owned change that can be checked next iteration, 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 3 questions, answered

What if the iteration in my scenario went well?

Then say so and look harder. Successful iterations still carry near misses, work that finished late in the window, an item nobody understood until the third day, or a practice that only held because one person absorbed extra work. A retrospective on a good iteration finds what to protect and what would break at larger scale.

Does the report need a named format such as start, stop, continue?

Only if your instructions ask for one. Any structure works when it separates observation from cause from action. Named formats help because they force the keep column that reports otherwise skip. What the criterion reads for is whether the findings are anchored in the iteration and whether something specific changes as a result.

How is this different from a lessons learned document?

Timing and consequence. Lessons learned usually arrive at the end of a project, when nobody on that team can act on them. A retrospective runs inside a live cycle and produces one change the same team applies immediately, then checks. Write it as something the team does next week, not as a record for the archive.

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

The full retrospective after the missed goal is here, with sprint facts before opinions, observations tied to real events, cause examined before remedy, one or two owned changes and blame kept out.

How many changes should a retrospective produce in PM FPX 4080 Assessment 3?

One or two. Teams rarely complete more within a sprint, and a short list with owners is far more likely to change how the next sprint runs.