Built for MT247 Unit 9, this retrospective runs ninety minutes in five timed stages, sorts issues by Circles and Soup, and ends with two owned actions checked next time. Searches like "mt 247 unit 9 assignment example", "mt247 unit 9 sample" and "mt247 unit 9 example" land here.
What a finished MT247 Unit 9 retrospective design looks like
Four pages: a one-page agenda, a page of materials and two pages of rationale. The agenda follows Derby and Larsen's five stages with minutes attached: set the stage 5, gather data 25, generate insights 25, decide what to do 25, close 10, for 90 in all against the Guide's three-hour maximum for a one-month Sprint. Each stage names its activity and output. Data comes from a Sprint 15 timeline, the blocked-days chart from the impediment log and the list of fourteen earlier actions with their status. Insights come from Circles and Soup, which sorts every issue into what the team controls, what it influences and what it must accept, followed by five whys on the top controllable item. The close is a return-on-time-invested vote. Rationale covers the facilitator, the action limit and the follow-up rule.
How a MT247 Unit 9 example is structured
The design starts from evidence of failure, the two-in-fourteen record, and every choice answers a reason that record suggests. Too many actions diluted ownership, so the decision stage caps them at two. Actions phrased as intentions, communicate better, could never be checked, so each must name an owner, a change visible to people who were not in the session, and a date. Actions lived in a document nobody reopened, so the Guide's allowance to add improvements to the next Sprint Backlog is used deliberately. The Circles and Soup sort keeps the session from spending its energy on the vice president and the security queue, which the team cannot change, while still routing them out through the Scrum Master. The outside facilitator addresses candor: people speak differently when the person running the room also rates them. The next retrospective opens by checking both actions.
Two out of fourteen
The record that shapes the design: six earlier retrospectives, fourteen actions, two completed, and no session held at all since Sprint 6.
Five stages, ninety minutes
Derby and Larsen's sequence with minutes on each stage, well inside the Guide's maximum and matched to a two-week Sprint.
Data before opinions
A Sprint timeline, the blocked-days chart and the old action list with statuses, on the wall before anyone offers an interpretation.
Circles and Soup
Every issue sorted into control, influence or accept, so the team spends its energy where it can act and hands the rest to the Scrum Master.
Actions capped and placed in the backlog
An owner, an observable change and a date for each, both entered into the next Sprint Backlog so they compete for time like any other work.
A facilitator who rates nobody
A Scrum Master borrowed from the finance systems team runs the session, because the team's own Scrum Master also writes its members' reviews.
Where marks go in MT247 Unit 9
Retrospective designs that name a popular format, start, stop and continue, with no reasoning about this team, earn little, since prompts here generally ask for a meeting that produces change. The most frequent gap is the absence of any mechanism for follow-through: actions without owners, without observable outcomes or without a check at the next session. Designs ignoring who is in the room miss the candor problem that often explains why earlier retrospectives failed. Timeboxes contradicting the Guide, or agendas with no times at all, draw comments. Spending the session on issues the team cannot influence, with no route out for them, tends to produce frustration rather than improvement. Formats changed every Sprint for novelty, unconnected to what the data shows, read as decoration. Missing data inputs leave insight to memory, which favors the loudest recollection.
Get a MT247 Unit 9 example written to your instructions
If earlier retrospectives produced actions nobody finished, say so, because that history shapes the design more than any format. Describe the team or paste the case, then attach the Unit 9 prompt and rubric. The first design is free inside 24-48h, timed stage by stage, with a follow-through rule someone could check.
MT247 Unit 9 questions, answered
Which retrospective format is best?
None in general; the format should fit what the team needs to examine. Start, stop and continue suits a quick check, a timeline suits a Sprint with a dramatic event, and Circles and Soup suits a team spending energy on things outside its control. The example chose Circles and Soup because the impediment log showed most lost time sitting outside the team.
Can improvements from a retrospective go into the Sprint Backlog?
Yes. The 2020 Scrum Guide says the most impactful improvements are addressed as soon as possible and may even be added to the Sprint Backlog for the next Sprint. The example uses that allowance deliberately, because actions kept in a separate document were forgotten. In the backlog they are visible at every Daily Scrum and compete for time openly.
Why limit the session to two actions?
Because the team's history showed many actions producing almost no change, and ownership thins as the list grows. Two actions that happen beat fourteen that do not. The limit is a design choice, not a rule from the Guide; some teams manage three. The example explains its limit using the two-in-fourteen record, which makes the choice defensible rather than arbitrary.