| Course | BU 433 Agile Project Management |
|---|---|
| Unit | Unit 5 |
| Paper type | Sprint plan |
| Length | About 950 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 5
Sign and Pay End to End, Gate Code by Hand: A Sprint Plan for Two Weeks of Online Move-In Work at a Composite Storage Chain, Sized to the Pace the Team Has Shown
Student Name
Business, Herzing University
BU 433: Agile Project Management
Instructor Name
March 11, 2026
Sign and Pay End to End, Gate Code by Hand: A Sprint Plan for Two Weeks of Online Move-In Work at a Composite Storage Chain, Sized to the Pace the Team Has Shown
The Sprint and Its Goal
This plan covers Sprint 4 of the online move-in work at Prairie Vault Storage, the composite 11-facility storage chain in this course, running from March 9 to March 20, 2026. The team planned it on the morning of March 9 in a session of about three hours, with the operations director present in the product owner role to answer questions about priorities and acceptance.
Sprint goal: a renter at the Wichita East facility can choose a unit, sign the lease and pay online from start to finish in the staging environment, with the facility manager issuing the gate code by hand.
The goal is a single outcome, not a list of items. The Scrum Guide treats the sprint goal as the one objective the team commits to and allows the work selected to change during the sprint as long as the goal holds (Schwaber & Sutherland, 2020). Writing it this way gives the team a test for every decision in the next two weeks: does this help a renter sign and pay end to end? The goal also accepts a limitation openly. The gate vendor's interface is not due until mid-April, so the code is issued by hand, as the backlog already planned for the pilot.
How Much the Team Can Take On
The team's completed work in its first three sprints was 11, 15 and 10 points, an average of 12. Sprint 3 finished lower than planned because the gate vendor sandbox test took three days rather than one, which is recorded as the reason rather than smoothed away. For Sprint 4, one developer will be at a payments conference on March 12 and 13, removing about two of the team's roughly 36 working days. The designer, who works part time, has no user interface work in this sprint beyond reviewing the lease screens. The team therefore planned to about 11 points, near its average less a little for the absence, rather than to its best sprint. Cohn (2005) advises planning an iteration from the team's demonstrated velocity and known availability rather than from the amount the business would like to see done.
What Was Pulled In
Two items were pulled from the top of the backlog because both serve the goal. A third was considered and left out.
| Item | Size | Why it serves the goal |
|---|---|---|
| D. Lease signing with approved version | 8 | The renter cannot finish without signing |
| G. Manager's morning dashboard | 3 | The manager must see the rental to issue the code by hand |
| Total pulled | 11 | |
| Not pulled: F. Gate code by text | 5 | Depends on the vendor interface due mid-April |
Card payment and hold, Item C, was completed in Sprint 3, so lease signing is the last missing step for a renter. The dashboard makes the manual gate step workable; without it, a manager would learn of an online rental only when the renter phoned from the gate. The text-message gate code was left out even though the team might have had room for part of it, because building against documentation before the interface exists risks rework, and partial work would not serve the goal.
The Work Inside the Items
In planning, the team broke each item into tasks of a day or less. Lease signing became seven tasks: load the lease template for each state; build the notice sections that must be opened before signing; capture the signature; store the signed record with version, time and device; generate and email the PDF; write automated tests for each acceptance criterion; and have the tester run the criteria on two phones. The dashboard became three: query overnight online rentals, build the list view sorted by move-in time and show the review flag.
Tasks are not assigned to people in this plan. The team decides each morning who picks up what, and the developer going to the conference has agreed to take the template and test tasks early in the sprint. Rubin (2012) notes that assigning every task at planning undermines the team's ability to swarm on whatever blocks the goal, and the lease work, with its dependency on counsel, is the kind of work where that flexibility matters.
Definition of Done
Six conditions must all hold before an item counts as finished. The code has been reviewed by the other developer. Automated tests for every acceptance criterion pass. The tester has checked every criterion in staging on the two most recent versions of iOS and Android. Screen reader labels exist for every input. The product owner has accepted the item after seeing it work. The change is deployed to staging and switched off in production behind a setting that can be turned on per facility. Work that meets some of these conditions is not partly done; it is not done, and it returns to the backlog at the sprint's end if unfinished.
If the Goal Stops Being Reachable
The main threat is counsel's lease draft. The team is building against a draft received on March 4; if counsel sends substantial changes after March 13, the notice sections may need rework. The response has been agreed in advance. At the daily meeting on the day any change arrives, the team and product owner will decide whether the changes fit inside the sprint. If they do not, the goal is kept but narrowed to "with the March 4 draft," and the revised text becomes the first item of Sprint 5. If the lease approach itself changes, for example counsel advising that online signing is not permitted for one of the two states, the product owner may cancel the sprint, which the Scrum Guide allows when a goal becomes obsolete. Either way, the decision is made openly on the day, not discovered at the review. The company, its team and every number here are composites for this course.
References
Cohn, M. (2005). Agile estimating and planning. Prentice Hall.
Rubin, K. S. (2012). Essential Scrum: A practical guide to the most popular agile process. Addison-Wesley.
Schwaber, K., & Sutherland, J. (2020). The Scrum guide: The definitive guide to Scrum: The rules of the game. https://scrumguides.org/scrum-guide.html
Reading the BU 433 Unit 5 instructions
BU 433 Unit 5 asks students to plan a single sprint or iteration. Requirements commonly include a sprint goal, the backlog items selected and why, a capacity figure based on past velocity and availability, a breakdown of items into tasks, a definition of done and a plan for what happens if the goal becomes unreachable. Instructors usually expect the goal to be one outcome rather than a list of features. Many prompts discuss the Scrum Guide directly. Whether tasks should be assigned to individuals is a common question; most instructors accept either choice if it is explained. A sprint plan of three or four pages with tables in APA 7 is typical, and the amount of work planned should be justified by evidence.
Inside the BU 433 Unit 5 example
The sample states the sprint dates and the goal in one sentence, then explains why a single outcome serves better than a list. A capacity section reports the team's three completed sprints, explains the low third sprint and adjusts for a planned absence. A table shows the two items pulled, their sizes and how each serves the goal, and the item left out with its reason. The task section breaks lease signing into seven tasks and the dashboard into three, and explains why tasks are not assigned. The definition of done is printed as six conditions. The final section sets out the agreed response if counsel's revision arrives mid-sprint, including narrowing the goal or canceling the sprint.
Reading the BU 433 Unit 5 rubric
Sprint plan rubrics usually score the sprint goal, the selection of work, capacity planning, task breakdown, the definition of done and risk handling, plus clarity and APA. The goal criterion rewards a single measurable outcome. Selection earns full credit when every pulled item serves the goal and exclusions are explained. Capacity scores highest when based on actual velocity and adjusted for known absences, not on what the business wants. Task breakdown is judged on whether tasks are small and cover testing as well as coding. The definition of done criterion expects conditions a reviewer can check. Risk handling earns top marks when the plan names a specific threat to the goal and a response agreed before the sprint starts.
BU 433 Unit 5 help: mistakes that cost points
Common mistakes in sprint plans include goals that are just lists of items, which give the team no way to decide what matters when trade-offs appear. Another is planning to the team's best sprint or to a round number rather than its demonstrated pace. Students often forget absences and holidays. Some pull items that do not serve the goal because they are next on the list. Task breakdowns frequently leave out testing, deployment and review. A definition of done written as the work is complete checks nothing. Finally, plans that assume nothing will go wrong lose points; naming the likeliest threat and the agreed response shows the student understands how sprints actually unfold.
Get a BU 433 Unit 5 example written to your instructions
Send the Unit 5 instructions and the rubric in your BU 433 classroom, with the backlog and the iteration length the assignment supplies. We write a custom example built on a one sentence goal, items justified against it, capacity taken from demonstrated throughput, the standard for finished printed, and a renegotiation position. 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 6: Ceremony analysis
- BU 433 Unit 7: Retrospective with a committed change
- BU 433 Unit 8: Hybrid or scaling analysis
- BU 345 Unit 5: Budget baseline sheet
- BU 396 Unit 5: Response strategy selection
- BU 434 Unit 5: Requirements document
- BU 436 Unit 5: Sustainability plan with costs
BU 433 Unit 5 questions, answered
Should the plan show who does what?
Only at the level the instructions ask for. Assigning every item to a named person at the start is one of the ways this deliverable turns into a schedule, and it removes the flexibility the iteration exists to preserve. Where ownership is required, note who picks something up as it begins rather than allocating the whole set in advance.
How long should the iteration be?
Use whatever length the case or the instructions fix, and keep it constant if you are planning more than one. Where the choice is yours, say what drove it: how quickly feedback can be obtained, how long a stakeholder can wait to see something, how much the team can hold in view at once. The reasoning is the graded part.
What if the plan cannot fit a whole feature?
Then it should not try, and saying so is the point. Pull the slice of it that serves the goal and is worth having on its own, then note in the plan that the remainder stays on the list. A plan stretching to include everything a stakeholder mentioned has stopped being matched against capacity.
Where can I find a free BU 433 Unit 5 sample paper?
The whole BU 433 Unit 5 sprint plan is free to view above, with the capacity reasoning, the pulled items, the definition of done and margin notes. If your team or backlog differs, email the prompt and a free custom sprint plan is prepared, usually inside two days.
How do I set capacity in BU 433 Unit 5?
Start from the points your team actually completed in recent sprints and adjust for known absences. The sample averages 12 points across three sprints, removes about two working days for a conference and plans 11 points.