| Course | MGT 641 Agile Project Management |
|---|---|
| Topic | Topic 2 |
| Paper type | Scrum event audit |
| Length | About 1,360 words, 7 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for MGT 641 Topic 2
Every Event Held, Most Purposes Missing: An Audit of Five Sprints of the Scrum Events on a Credit Union's Lending App Team
[Author Name]
Colangelo College of Business, Grand Canyon University
MGT-641: Agile Project Management
Topic 2 Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Every Event Held, Most Purposes Missing: An Audit of Five Sprints of the Scrum Events on a Credit Union's Lending App Team
Method
Sagebrook Community Credit Union's lending app team has worked in two-week sprints for three months. Its sponsor asked whether Scrum is working. A schedule check would answer yes, since every event has been held on time. This audit asks a different question: for each event, did the team get what the event exists to produce? I attended all events across five consecutive sprints, kept notes on timing, attendance and outcomes, and compared the product backlog before and after each Sprint Review. The purpose of each event is taken from the 2020 Scrum Guide and paraphrased, so the team is measured against the framework's own claims rather than an outside preference (Schwaber & Sutherland, 2020).
Summary of Findings
Table 1
Scrum Events Against Their Purposes Over Five Sprints, Illustrative
| Event | Purpose in the Scrum Guide | What five sprints showed | Information lost |
|---|---|---|---|
| Sprint | A fixed period in which the team can adapt toward a goal | Content fixed by vendor scope list | Any chance to change course mid-sprint |
| Sprint Planning | Agree why the sprint matters, what can be done and how | Stories picked from fixed scope; goal reads finish assigned stories | A goal the team can trade scope against |
| Daily Scrum | Inspect progress toward the goal and replan the next day | 35 minutes of task reports to a project manager | Daily replanning by the developers |
| Sprint Review | Inspect the outcome with stakeholders and adjust the backlog | Demonstrations to the vendor account manager | Reactions from members and lending staff |
| Sprint Retrospective | Plan ways to raise quality and effectiveness | 14 improvement items raised, none closed | Any improvement at all |
Table 1 sets out the five events. The team holds all of them, and only one, Sprint Planning, partly produces its intended result.
Sprint Planning
Planning is held on the first morning of each sprint and lasts the allotted four hours. The developers select stories from the list attached to the vendor contract, in the order the contract sets. The Sprint Goal is written each time, but all five read as a version of complete the stories selected. A goal of that kind gives the team nothing to trade against: if a story proves harder than expected, there is no shared outcome that would let them drop part of it and still succeed. The guide describes the goal as the single objective that gives the sprint coherence and allows flexibility in the work (Schwaber & Sutherland, 2020). Here the purpose is partly met, since the team does agree on what it can do, but the why is missing.
Daily Scrum
The Daily Scrum runs about 35 minutes against a 15-minute limit. Each developer tells the project manager what they finished yesterday and what they will do today, and the project manager updates a spreadsheet. Nobody refers to the Sprint Goal, and in 50 observed meetings the plan for the day changed twice. The length is a symptom, not the problem. The event exists for the developers to inspect their progress and adjust their own plan, and Moe et al. (2010) found in a Scrum case study that daily meetings reporting to a manager weakened the shared mental model and the backup behavior the team needed. A 15-minute report to the project manager would defeat the purpose just as surely as a 35-minute one.
Sprint Review
Each review is a demonstration for the vendor's account manager and the project manager. No member has attended, no lending officer has attended, and the credit union's product owner, a business analyst, attended two of five and could not commit to changes without the chief lending officer. The backlog was identical before and after all five reviews. This event matters most, because it is how what the team builds meets the people who will use it. Without those people, five demonstrations produced polite approval and no new information. The missing feedback also explains why nothing else in the audit improves: the team has no evidence to plan around.
Sprint Retrospective
Retrospectives are lively and well run. The team has raised 14 improvement items, and none has been closed. Nine concern waiting on the compliance group for disclosure wording, three concern test environment outages and two concern the length of the Daily Scrum. Most of the items need someone outside the team to act, and no one with that authority attends. Hoda et al. (2013) describe self-organizing teams that rely on informal roles to reach outside parties and remove obstacles; this team has no one in that role, and the Scrum Master's requests to compliance go through the same queue as everyone else's.
Meetings the Team Has Added
Two meetings sit outside the five events, and the audit asks of each the same question: what does it produce? Backlog refinement, which the guide treats as an ongoing activity rather than an event, is held for two hours midway through each sprint and is the one session where the product owner and developers discuss upcoming work in detail; it earns its place. The weekly status call with the vendor's account manager does not. It repeats the task reporting of the Daily Scrum for a different audience and produced no decision in five sprints, so the audit treats it as a duplicate and recommends replacing it with the sprint review summary.
The Sprint Itself
The sprint is treated last because it contains the others. A sprint is meant to be a period in which the team can adapt toward its goal. Here the vendor contract fixes the content of each sprint in advance, so even a perfect review and a perfect Daily Scrum would have nothing to adjust. This is the deepest gap, and it lies outside the team's control.
The Maturity Defense
The project manager argues that the events are young and will improve with practice. The argument deserves a fair test. Across five sprints, no measure moved: the Daily Scrum did not shorten, review attendance did not widen, and no retrospective item closed. Time alone will not change a contract or invite a lending officer. The defense is granted in one place only. Retrospectives often need several cycles before a team learns to frame items it can act on, and that one event may improve without outside help.
What the Gaps Cost
The cost of each gap can be stated as information the credit union paid for and did not receive. Five reviews without members meant that ten weeks of screens went untested by the people who will apply for loans. The home equity project, built the old way, showed what that costs later: most of its changes arrived after members finally used the product, when each one required a change order. With seven developers in the room, the Daily Scrum consumed about 200 developer hours over five sprints, more than a month of one developer's time, and produced two changes to the plan. Fourteen unclosed retrospective items represent problems the team has already diagnosed and keeps paying for, chiefly an average wait of six working days for compliance wording on each screen that shows a disclosure. None of these costs appears on a status report, because the calendar shows every event complete.
Two qualifications are needed. The five sprints observed came early in the project, and the vendor scope list did allow small changes to the order of stories within a sprint, which the team used twice. Neither changes the conclusion that the events are held as a schedule rather than as feedback loops.
Recommendations
First, no further review should be scheduled until the chief lending officer or a delegate with authority, and two branch lending staff, can attend; members should join monthly. Second, the Daily Scrum should belong to the developers, with the project manager attending as a listener and the Sprint Goal on the wall. Third, each retrospective item needing outside action should be assigned to a named credit union manager and reviewed at the next retrospective. Fourth, the sponsor should open the vendor contract so that sprint content can be reordered by the product owner. Without the fourth change, the first three will improve the events without making the sprints adaptive.
References
Hoda, R., Noble, J., & Marshall, S. (2013). Self-organizing roles on agile software development teams. IEEE Transactions on Software Engineering, 39(3), 422-444. https://doi.org/10.1109/TSE.2012.30
Moe, N. B., Dingsøyr, T., & Dybå, T. (2010). A teamwork model for understanding an agile team: A case study of a Scrum project. Information and Software Technology, 52(5), 480-491. https://doi.org/10.1016/j.infsof.2009.11.004
Schwaber, K., & Sutherland, J. (2020). The Scrum guide: The definitive guide to Scrum: The rules of the game. https://scrumguides.org/scrum-guide.html
What the MGT 641 Topic 2 instructions ask for
The Topic 2 assignment in MGT-641 asks students to look at the Scrum events in practice and judge them by what they are for. Describing the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective from the guide is only the starting point. A paper meets the brief when it observes a real or realistic team over several sprints, records what each event produced and compares that with the purpose the Scrum Guide gives it. Graduate students should explain the cost of each gap in terms of lost information or effort, draw on research into Scrum teams, consider a fair defense of the team and recommend changes in an order that reflects which gaps cause the others.
Inside the MGT 641 Topic 2 example
Five rows make up the finished audit, one per event, each holding the purpose the 2020 Scrum Guide assigns, what the team did across five two-week sprints and what the gap costs. The Daily Scrum runs about 35 minutes and consists of developers reporting yesterday's tasks to a project manager, so it inspects no progress toward a Sprint Goal and replans nothing. Sprint Planning selects stories from a scope the vendor contract already fixed, which leaves the Sprint Goal reading as finish the assigned stories. Reviews are demonstrations to the vendor's account manager; no member and no lending officer has attended one, so nothing learned enters the backlog. Retrospectives have produced 14 improvement items and closed none. Its verdict: the calendar is intact, while the feedback the events exist to create has not appeared once.
Where the marks sit in the MGT 641 Topic 2 rubric
Instructors grading the audit reward evidence gathered over time rather than a checklist of events held. An Excellent paper states its method, sprints attended, notes kept and backlog compared, so every finding can be traced. Credit goes to separating symptoms from causes, such as seeing that the Daily Scrum fails because developers report upward, not because it runs long. The rubric values identifying the review as the gap that starves the other events of feedback, and recognizing that a sprint fixed by contract cannot adapt. Strong papers weigh the maturity defense against the record and grant it only where the data allows. The best recommendations come in dependency order and assign outside actions to named managers.
MGT 641 Topic 2 help: mistakes that cost marks
A ceremony audit confirming that each event happened on the calendar has checked the form this topic asks the writer to look past. Papers describing the five events from the guide, with no observation of a real team, supply the purpose and none of the gap, which is where the analysis lives. Treating a long Daily Scrum as a timekeeping problem misses that its content, reporting upward, defeats its purpose at any length. Reviews without decision makers are frequently overlooked, although they explain why nothing else in the case improves. Some papers blame the Scrum Master for every gap and ignore that the vendor contract fixed each sprint's content before planning began. Recommendations to add a coach or more training leave the absent stakeholders absent, and a credible audit states what each missing purpose costs in lost information.
Get an MGT-641 Topic 2 example written to your instructions
Send the MGT-641 Topic 2 instructions and your section's rubric, with any team, framework or observation notes the assignment supplies. We write a custom example to those criteria, with each event's purpose stated, observed practice recorded, the cost of every gap named and the maturity defense weighed, in 24 to 48 hours. The first one is free.
More MGT 641 papers and MBA samples
- MGT 641 Topic 1: Agile Manifesto Assumptions Paper
- MGT 641 Topic 3: Backlog Ordering Rationale
- MGT 641 Topic 4: Story Point Estimation Memo
- MGT 641 Topic 5: Proxy Product Owner Dq Post
- MGT 641 Topic 6: Scaling Framework Critique
- MGT 641 Topic 7: Agile Adoption Behavior Audit
- MGT 641 Topic 8: Hybrid Delivery Defense
- MGT 655 Topic 2: Forecast Error Analysis
- MGT 640 Topic 2: Competing Business Case Appraisal
- MGT 660 Topic 2: Weighted External Analysis
- MGT 605 Topic 2: Effectiveness Theory Survey
MGT 641 Topic 2 questions, answered
What are the Scrum events?
The 2020 Scrum Guide names five: the Sprint, which contains the others, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Each is a formal chance to inspect something and adapt. The guide sets time limits, including fifteen minutes for the Daily Scrum. Many teams call them ceremonies and some lists leave out the Sprint itself, which is why the example names the edition it follows.
Why audit purpose instead of attendance?
Because attendance can be perfect while the event achieves nothing. A Daily Scrum everyone attends can still be a status report, and a review can be well attended by people with no authority over the backlog. Purpose asks what the event changed: a replanned day, a reordered backlog, an improvement adopted. The example records those outcomes sprint by sprint, which attendance figures never show.
Where can I find a free MGT 641 Topic 2 sample paper?
All of the credit union Scrum audit is here: the method, the five-event table, each event's findings, the cost of the gaps, the maturity defense and four recommendations. Describe the team you watched, and we can prepare a free audit based on your observations.
Which Scrum event does the MGT 641 Topic 2 audit fix first?
The Sprint Review, because no member, lending officer or empowered product owner attended any of the five, so the backlog never changed and the other events had no new information to plan around.
Does the MGT 641 Topic 2 audit cover the Sprint itself?
Yes, separately and last. The vendor contract fixes each sprint's content in advance, so even well-run planning, daily meetings and reviews would have nothing to adjust, and the audit names that as the gap outside the team's control.