One Sprint Goal, 15 points selected against a capacity-adjusted forecast of 16, and a plan for the first two days make MT247's Unit 7 sprint planning artifact. Searches like "mt 247 unit 7 assignment example", "mt247 unit 7 sample" and "mt247 unit 7 example" land here.
What a finished MT247 Unit 7 sprint planning artifact looks like
Four pages organized by the three topics the 2020 Guide sets for Sprint Planning. Why this Sprint is valuable comes first: the Sprint Goal, that a resident reporting a leak after hours reaches the on-call technician and sees when help will arrive. What can be done follows, with a capacity table: five Developers across ten days, less five days for a holiday, three for vacation and four for production support, leaving 38 of 50, or 76 percent. Applied to the last three velocities, averaging 21, that gives a forecast near 16 points and a range of 13 to 18. Three items totaling 15 are selected: emergency routing at 8, the technician arrival window at 5, and an older-phone photo defect at 2. How the work gets done closes the artifact, with the first two days broken into tasks.
How a MT247 Unit 7 example is structured
The artifact follows Sprint Planning's own order, because the goal has to exist before selection can be judged against it. The Sprint Goal is written as an outcome a resident would notice, which lets the Developers renegotiate scope during the Sprint without abandoning the commitment. Capacity is calculated before any item is chosen, so the forecast reflects this Sprint's actual people rather than an average Sprint. Selection then serves the goal: the arrival window sits seventh in the Product Backlog, below smaller items, but completes the goal, and the Product Owner's agreement is recorded. Two exclusions are explained, permission-to-enter windows because adding them would plan to the very top of the range, and phone-based request closing because the technicians' phones arrive next month. Only the first two days are decomposed into tasks, by the Developers' own choice. The Definition of Done is referenced once.
A goal a resident would notice
Reaching the on-call technician after hours and seeing when help arrives, stated as an outcome so scope can flex without the Sprint losing its purpose.
Thirty-eight of fifty days
Five days for the holiday, three for one Developer's vacation and four for the support rotation, leaving 76 percent of a full Sprint's time.
A forecast near sixteen
Three recent velocities averaging 21, scaled to this Sprint's capacity, give about 16 points and a range running from 13 to 18.
Fifteen points against the goal
Emergency routing, the arrival window and a photo defect on older phones, with the Product Owner's agreement recorded for pulling the arrival window forward.
Two items left out, with reasons
Permission-to-enter windows would push the plan to the top of the range; phone-based closing waits for technicians' devices due next month.
Tasks for the opening days only
The first two days are broken into tasks of a day or less; the rest of the plan is left for the Developers to shape at each Daily Scrum.
Where marks go in MT247 Unit 7
Sprint plans that fill a Sprint to the average velocity without subtracting holidays, leave and support duties are the commonest weakness, and scenarios often supply those absences precisely to see whether they are counted. A list of items with no Sprint Goal, or a goal that merely restates the list, misses the commitment the 2020 Guide places at the center of the event. Selecting a lower item because it completes the goal can be defensible, but only when the Product Owner's agreement is recorded. Plans decomposing every item into tasks for the full two weeks imply a certainty nobody has. Forecasts presented as promises to management repeat the misuse earlier units warned against. Missing references to the Definition of Done, and items selected that depend on something not yet available, draw the lighter comments.
Get a MT247 Unit 7 example written to your instructions
Known absences matter as much as velocity here. Include the team details or case, any velocity figures, holidays, leave and support duties, and the Unit 7 prompt with its rubric. The first artifact is free and back in 24-48h, capacity calculated before selection and a Sprint Goal written as something a user would notice.
MT247 Unit 7 questions, answered
How is capacity different from velocity?
Velocity is what the team has completed in recent Sprints, measured in its own units. Capacity is how much time the team actually has this Sprint after absences and other duties. The example scales average velocity by this Sprint's capacity, 76 percent of normal, to produce a forecast. Velocity alone would plan a full Sprint's work into a Sprint missing a quarter of its time.
Can the team select an item that sits lower in the backlog?
It can when the item serves the Sprint Goal and the Product Owner agrees, since Sprint Planning is a collaboration and the goal gives the selection its coherence. The example pulls the arrival window forward for that reason and records the Product Owner's agreement. Skipping items without explanation, or without the Product Owner present, would be the weaker version.
Does every item need tasks at Sprint Planning?
The 2020 Guide says the Developers plan the work for each selected item, often by decomposing it into pieces of one day or less, and that how they do so is their choice. The Sprint Backlog then changes as more is learned. The example details the first two days and leaves the rest to emerge at the Daily Scrum, a choice the artifact explains.