| Course | BU 433 Agile Project Management |
|---|---|
| Unit | Unit 7 |
| Paper type | Retrospective with a committed change |
| Length | About 890 words, 6 pages |
| Format | APA 7 student paper |
| School | Herzing University |
| Program | BS in Project Management |
| Updated | September 2026 |
Free sample paper for BU 433 Unit 7
Stop Starting When Two Items Wait in Test: A Retrospective With a Committed Change After Sprint 4 of a Composite Storage Chain's Online Move-In Work
Student Name
Business, Herzing University
BU 433: Agile Project Management
Instructor Name
April 8, 2026
Stop Starting When Two Items Wait in Test: A Retrospective With a Committed Change After Sprint 4 of a Composite Storage Chain's Online Move-In Work
The Sprint Being Reviewed
On March 20, 2026, the team behind Prairie Vault Storage's online rentals, a storage company invented for this course, closed its fourth two-week sprint with a retrospective, recorded here. The sprint had aimed at one thing: a Wichita East renter completing lease and payment in staging without help, while staff still handed out gate codes in person. Two items made up the 11 points planned, lease signing at 8 and the manager's dashboard at 3.
The goal was met in the narrowed form agreed in advance: counsel sent revised notice wording on March 16, and the team completed lease signing against the March 4 draft, with the revision moved to Sprint 5. Lease signing was done. The dashboard was not; its code was written but it had not been tested by the sprint's end, so under the definition of done it returned to the backlog. The team completed 8 of 11 planned points.
The five team members and the product owner attended. The retrospective ran 90 minutes and followed the stages described by Derby and Larsen (2006): set the stage, gather data, generate insights, decide what to do and close. It opened with the reminder that everyone did the best job they could with what they knew at the time, a principle Kerth (2001) set down so that a review looks at the work and its conditions rather than at blame.
Gathering Observations Before Opinions
Data came first, before anyone explained or proposed anything. For ten minutes each person silently added events to a timeline drawn across the sprint's ten days, one note per event, with the date. The product owner then added figures from the board's history, which records when every task moved between columns. Only after the timeline was complete did discussion begin. Derby and Larsen (2006) argue that starting with shared facts prevents a retrospective from being decided by whoever speaks first, and on this team the loudest early opinion would have blamed counsel's revision for everything.
What the Team Saw
The timeline and board history produced seven observations, recorded here without interpretation.
| No. | Observation | Source |
|---|---|---|
| 1 | Counsel's revised notice wording arrived March 16, day six | Timeline |
| 2 | The tester spent March 16 to 18 retesting lease screens against the revision before the team agreed to use the March 4 draft | Timeline and board |
| 3 | Ten tasks passed through the Ready for Test column; six waited there more than a day | Board history |
| 4 | Average wait in Ready for Test was 2.1 working days | Board history |
| 5 | Both developers started new tasks while items waited in test | Board history |
| 6 | The dashboard's code was finished on March 17 and waited in test until the sprint ended | Board history |
| 7 | The new daily meeting format, walking the board, was used from March 11 | Timeline |
What the Observations Meant
In the insight stage the team asked why the dashboard, a small and easy item, was left unfinished while an 8-point item with a legal dependency was completed. The first explanation offered was counsel's revision. The board history did not support it as the whole answer: items were already waiting in test before March 16, and the average wait was over two days for the whole sprint, not only after the revision arrived.
The pattern the team settled on was that testing is a single-person step, the developers keep starting new work while finished code waits, and so work piles up at the tester's desk. Counsel's revision made the pile larger for three days, but it did not create it. The developers said they had assumed testing was the tester's job and that starting something new was the productive choice. The tester said she had not asked for help because the developers looked busy. Anderson (2010) describes this as the typical result of letting work in progress grow without a limit: effort is spread across many items, and few reach done.
The One Committed Change
The team listed five possible changes and chose one, deliberately, because its previous three retrospectives had each produced several intentions and none had been carried out.
The change: when two or more items are waiting in Ready for Test, no one starts a new task. Instead, a developer pairs with the tester, or tests an item written by the other developer against its acceptance criteria. The limit is written on the board above the column.
Owner: the senior developer, who agreed to check the column at every daily meeting and call the limit when it is reached. Ownership belongs to one person so that the rule does not depend on everyone remembering it.
How the Team Will Know It Worked
The signal is taken from the board history, which the team already has, rather than from impressions. If the change works, the average wait in Ready for Test should fall from 2.1 days to under one day in Sprint 5, and no item should return to the backlog unfinished because it was not tested. A secondary check is that completed points do not fall, since the developers are giving up some coding time to test. If the wait falls but completed points drop sharply, the team will discuss whether the limit is set too low. The product owner will bring the figures to the Sprint 5 retrospective, which will open by checking this commitment before anything else.
Two other possible changes, earlier contact with counsel and a second phone for testing, were noted for later. Earlier contact with counsel would have softened the three days of retesting, but it addresses a single event rather than the pattern, and a second phone would speed each test without changing who does the testing. Both remain on the team's list, and either can be chosen at a later retrospective if the pattern returns in another form. The company, the team and all figures in this record are composites for this course.
References
Anderson, D. J. (2010). Kanban: Successful evolutionary change for your technology business. Blue Hole Press.
Derby, E., & Larsen, D. (2006). Agile retrospectives: Making good teams great. Pragmatic Bookshelf.
Kerth, N. L. (2001). Project retrospectives: A handbook for team reviews. Dorset House.
The Herzing BU 433 Unit 7 instructions
For Unit 7, BU 433 asks students to document a sprint retrospective. Usual requirements include describing the sprint and its outcome, explaining how observations were gathered, recording what the team found, analyzing causes, committing to one or a few changes with owners, and stating how the team will know whether the change worked. Many instructors refer to Derby and Larsen's five stages. The record should be honest about problems without blaming individuals. A retrospective after a successful sprint still needs a committed change, often aimed at something small. Composite teams are acceptable when labeled. The record is commonly short, formatted in APA 7, with observations and the commitment set out clearly enough to check later.
Inside the BU 433 Unit 7 example
The record first describes the sprint, its goal, the narrowed outcome and the unfinished dashboard. It then explains the retrospective's format and the principle used to keep attention on conditions rather than blame. A section describes how the team built a silent timeline before discussing anything. Seven observations follow in a table, each with its source. The insight section tests the first explanation against the board data, finds it incomplete and describes the pile-up at testing in the team members' own words. The commitment section chooses one change from five, states it as a rule with a named owner, and explains why only one was chosen. The final section defines the measure of success and a secondary check.
Reading the BU 433 Unit 7 rubric
Retrospective rubrics generally score the description of the sprint, the data gathering process, the analysis of causes, the committed change and the success measure, along with writing quality. Data gathering earns credit when facts are collected before interpretation and sources are named. Analysis scores highest when the student tests explanations against evidence rather than accepting the first one. The commitment criterion rewards one specific change with a named owner over a list of good intentions. The success measure earns full points when it is observable and taken from data the team already collects. Instructors also assess tone, crediting records that describe problems plainly while focusing on the process rather than on individuals.
BU 433 Unit 7 help: mistakes that cost points
A common problem on this unit is a retrospective that ends with a list of five or six improvements, none owned, which rarely change anything. Another is jumping to causes before facts are gathered, so the loudest opinion decides the conclusion. Students often write vague commitments, such as communicate better, that no one can check. Some records blame individuals by name, or blame outside factors so heavily that the team's own process escapes scrutiny. Others skip the success measure, leaving no way to tell at the next retrospective whether the change worked. Finally, retrospectives of good sprints often say nothing needs changing, which instructors tend to question; even a strong sprint has one thing worth improving.
Get a BU 433 Unit 7 example written to your instructions
Send the Unit 7 instructions and your BU 433 rubric, plus the iteration or scenario the assignment supplies. We write a custom example that describes collection first, separates observations from conclusions, commits to one change with an owner and a starting point, defines the signal and records what was rejected. 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 3: Backlog with prioritization basis
- BU 433 Unit 4: Estimation exercise
- BU 433 Unit 5: Sprint plan
- BU 433 Unit 6: Ceremony analysis
- BU 433 Unit 8: Hybrid or scaling analysis
- BU 396 Unit 7: Monitoring and review plan
- BU 345 Unit 7: Status report to sponsor
- BU 434 Unit 7: Future state and gap analysis
- BU 436 Unit 7: Currency and financial risk
BU 433 Unit 7 questions, answered
Does the change have to be small?
Small enough that it can start in the next iteration without anybody's permission, which rules out most of the interesting complaints. A change needing a budget or a decision from outside the team is worth recording as an escalation, but the committed one should be something the team can begin alone, or the record ends in a request instead of a commitment.
What if the iteration went well?
Then the material is about what made it go well and whether that is repeatable, which is harder and usually scores better. A session with nothing to fix still has a question: which of the things that worked was deliberate and which was luck. Commit to protecting one of them, and define the signal that would show it slipping.
How honest can the record be about people?
Honest about behavior, silent about names, and worth stating in the record itself. Write what happened and what it cost the iteration, not who caused it, since a session where people expect to be identified stops producing usable material within one round. If the assignment draws on a real group, change enough that nobody could be recognized.
Where can I find a free BU 433 Unit 7 sample paper?
This page offers the complete BU 433 Unit 7 retrospective with a committed change free of charge, with the observation table, the analysis and margin notes. Should your sprint or team differ, we can draft a custom retrospective record for you without charge, typically within about two days.
How many changes should BU 433 Unit 7 commit to?
Usually one, with an owner and a measure. The sample chooses one rule from five candidates because the team's earlier retrospectives produced several intentions and carried out none, and it notes the other ideas for later.