MGMT 8805M Week 6 Sprint Critique Example

Course	MGMT 8805M Agile and Disruptive Innovation Management
Week	Week 6
Paper type	Sprint critique
Length	About 780 words, 5 pages
Format	APA 7 student paper
School	Walden University
Program	PhD in Management
Updated	October 2026

Free sample paper for MGMT 8805M Week 6

Points Completed, Decisions Unchanged: A Sprint Critique Auditing a Handheld Ultrasound Team's Two-Week Iteration Against What It Set Out to Learn, Separating Output From Validated Learning and Asking Whether Regulated Device Work Suited Iteration at All

Student Name

Walden University

MGMT 8805M: Agile and Disruptive Innovation Management

Instructor Name

Month Day, Year

What this page is doingThe title names the critique's standard, learning rather than output, and the question its closing pages ask.

The Team and Its Question

Brightwater's new handheld unit has a team of seven: four software engineers, a hardware engineer, a clinical specialist and a product lead. In its sixth sprint, in June 2022, the team set out, in the product lead's words at planning, "to learn whether anesthesiologists will use guided needle visualization during nerve blocks, or keep using the cart they already have."

What this page is doingThe critique opens with the question as the team itself stated it at planning, so the iteration is judged against its own aim.

The Iteration Record

[after]

The team completed 34 of 38 planned story points, plus 8 added mid-sprint, and the sprint review rated the iteration "on track."

Table 1

Sprint 6 Record: Planned Work, Completed Work, Assumptions and Results

Line	Item	Planned	Completed	Assumption tested	What came back
1	Needle-tip highlighting algorithm	Yes	Yes	Visible needle tip is what users lack	Not tested with users
2	Tablet interface for one-handed use	Yes	Yes	Anesthesiologists hold the probe and tablet at once	Two users preferred a stand
3	Pilot with 5 anesthesiologists at one hospital	Yes	No; moved to sprint 7	Users will choose handheld over cart	No data
4	Battery life improvement	No	Yes, added mid-sprint	None stated	Bench test only
5	Regulatory documentation for highlighting feature	Yes	Partial	None stated	Draft only

Output Against Learning

Ries (2011) argued that, under uncertainty, progress should be measured by validated learning, evidence from real users about whether the team's assumptions hold, rather than by output such as features completed. Judged that way, sprint 6 learned very little. Its central question, whether anesthesiologists would choose the handheld over the cart, depended on line 3, the pilot, which was moved to the next sprint. Line 1 produced a working algorithm but no evidence that users needed it. Line 2 produced the only real learning: two users said they preferred a stand to holding the tablet, which contradicted the assumption behind the one-handed interface the team had just built.

What Changed and What Did Not

Comparing plans before and after the sprint, one decision changed: the team added a tablet stand to the sprint 7 backlog. The central decision, whether to continue building for anesthesia at all, did not change, because no evidence bearing on it was collected. The 42 points completed were output; the stand was the learning.

What this page is doingThe critique counts decisions changed, because a sprint that alters no decision has not answered its question, whatever it shipped.

Responding to Change

The team did respond to change, but to the wrong kind. The Agile Manifesto values responding to change over following a plan (Beck et al., 2001). Mid-sprint, the team added battery work after an engineer found an improvement, and dropped the pilot because the hospital's scheduling slipped. Both changes followed internal convenience, not new information from users. The battery work was easy to complete and visible at review; the pilot was hard and uncertain. Points rewarded the first.

What the Review Rewarded

The sprint review is where the team's incentives become visible. Its agenda gave twenty minutes to demonstrating the needle highlighting and the battery gain, and five minutes to the pilot, described as "rescheduled." No one at the review asked what the team now knew about anesthesiologists that it had not known two weeks earlier. A review built around demonstrations will favor work that can be demonstrated, and a team that wants a good review will choose that work when plans slip. Changing the review's first question, from what was built to what was learned, would change what the team chooses to do mid-sprint.

Did This Work Suit Iteration?

Boehm (2002) argued that agile methods suit projects with rapidly changing requirements and small teams, and that plan-driven methods suit projects where failure is costly and requirements are stable, such as safety-critical systems. The handheld project mixes both. The question of what anesthesiologists want is uncertain and suits iteration. The regulatory documentation, line 5, is safety-critical and was squeezed into a two-week cycle where it could only be drafted. The critique's view is that the team should iterate on the clinical question in short cycles, with user evidence as the measure, and run regulatory work on its own plan-driven track.

What the Next Sprint Should Change

Sprint 7 should make the pilot its first item and measure its success by what five anesthesiologists do with the device, not by points. If the pilot cannot run, the sprint should be shortened rather than filled with other work.

Limits

The critique relies on the sprint record and review notes; it did not observe the team. Interviews with the product lead about why the pilot slipped would test whether the cause was external or a choice.

References

Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R. C., Mellor, S., Schwaber, K., Sutherland, J., & Thomas, D. (2001). Manifesto for agile software development. https://agilemanifesto.org/

Boehm, B. (2002). Get ready for agile methods, with care. Computer, 35(1), 64-69. https://doi.org/10.1109/2.976920

Ries, E. (2011). The lean startup: How today's entrepreneurs use continuous innovation to create radically successful businesses. Crown Business.

Reading the MGMT 8805M Week 6 instructions

Week 6 asks you to critique one iteration of an agile team. State the team, the product and the question the iteration was meant to answer, in the team's own words at planning. Present the iteration record as an exhibit: planned work, completed work, assumptions tested and what came back from users or data. Compare output with learning, counting decisions changed rather than points completed. Examine how the team responded to change during the iteration, and whose information drove it. Consider whether the work suited iteration at all, using research on when agile methods fit. Close with what the next iteration should change and the limits of your evidence. Expect four to six pages that read partly as an audit.

How this MGMT 8805M Week 6 example is built

The sample states the team's planning question about anesthesiologists. The record exhibit lists five items: needle highlighting, a one-handed interface, a postponed pilot, unplanned battery work and partial regulatory documents. A section applies Ries's validated learning and finds that only user comments about a tablet stand produced learning. A section counts one decision changed. The Agile Manifesto's preference for responding to change is applied to the mid-sprint additions, which followed convenience, not users. A section shows the review agenda favored demonstrations. Boehm's argument that agile suits uncertain work and plan-driven methods suit safety-critical work leads to separate tracks. The next sprint puts the pilot first, and limits follow.

MGMT 8805M Week 6 rubric: what earns full marks

Graders reward an exhibit detailed enough that the analysis can refer to it line by line. The planning question should be stated as the team stated it. Strong critiques measure the iteration against learning and decisions changed, using research accurately, and are specific about which items produced learning. Analysis of responses to change should ask whose information drove them. The question of whether the work suited iteration should be argued with research and should distinguish parts of the work. Concrete recommendations for the next iteration complete strong work. Critiques that praise or condemn agile in general, or count only points and velocity, remain in the middle band, as do critiques without an exhibit.

MGMT 8805M Week 6 help from the desk

Ask the team, or find in the case, the exact question the iteration was meant to answer; it is often written in planning notes. Build the record exhibit before writing analysis. For each item, ask what assumption it tested and what users or data said. Count how many decisions changed at the end; that number is often surprising. Look at what was added or dropped mid-iteration and why. Then consider whether parts of the work need a different approach, especially regulated or safety-critical parts. Keep recommendations specific to the next iteration. Tutors are available to help with the exhibit and the research behind it, and the handheld team critique above shows a completed version.

Get a MGMT 8805M Week 6 example written to your instructions

Forward the Week 6 prompt, the rubric, and the sprint record your section provides, or describe the team you plan to critique, and a critique is back within 24-48h, no charge for the first. State whether the exhibit counts toward the page limit. Your team's backlog belongs in your paper; the sample shows how one gets read.

More MGMT 8805M papers and PhD in Management samples

MGMT 8805M Week 6 questions, answered

Where can I find a free MGMT 8805M Week 6 sample paper?

The handheld team sprint critique above, with its iteration record, is the full sixth-week sample.

What did the team in the MGMT 8805M Week 6 sample fail to learn?

Whether anesthesiologists would choose the handheld over the cart, because the pilot moved to the next sprint.

What is validated learning?

Ries's term for evidence from real users about whether a team's assumptions hold, used as the measure of progress.

How many decisions did the sprint change?

One: the team added a tablet stand to the next backlog after two users said they preferred one.

Did the work suit iteration?

Partly. The clinical question suited short cycles, while regulatory documentation needed its own plan-driven track.