MT340 Unit 3 Team Effectiveness Diagnosis Paper Example

Four Reasons Before Any Name: An MT340 Unit 3 Team Diagnosis of a Combat Team That Keeps Missing Sprint Goals

[Student Name]

Purdue University Global

MT340: Conflict Management and Team Dynamics

Unit 3 Team Diagnosis Paper

[Instructor Name]

[Date]

The studio, team and figures are composite; the framework and research cited are real.

The Team and the Symptom

The combat team was formed in spring to make melee combat feel responsive before a publisher milestone. It has four members: a gameplay engineer, an animator, a designer and a QA tester. Over three two-week sprints, it planned 31, 28 and 30 tasks and completed 19, 18 and 17. Animation tasks were carried over most often: of 37 tasks carried over across the three sprints, 21 were animation tasks.

In stand-ups and retrospectives, the explanation offered most often has been that the animator has too much on her plate. That may be true. But it describes a symptom, carried-over animation work, as if it were a cause.

Why Hackman

Hackman (2002) argued that team effectiveness depends less on the members' individual qualities than on conditions the organization creates around them. Wageman et al. (2005) turned that work into a diagnostic survey built on five conditions. A team needs to be bounded and stable, to have a direction worth pursuing, to be set up with workable tasks and norms, to receive the information, rewards and resources it needs from the wider organization and to have access to skilled coaching. The framework is chosen here because its conditions sit outside individual members, which forces the diagnosis to look at structure before people.

The Five Conditions

The first condition is a real team. It is partial here. The engineer, designer and tester work only on combat. The animator splits her time with trailer work for the publisher, and her manager, the art director, sets her priorities. When a trailer deadline approaches, combat animation stops. The team's boundary therefore runs through the middle of one member's week, and the team does not control that part of her time.

The second condition is a compelling direction. It is absent in a usable form. The milestone criterion is "combat feels responsive." Nobody on the team can say what measurement would show that the criterion is met. The engineer thinks it means input latency under a hundred milliseconds; the designer thinks it means players stop complaining in playtests; the tester thinks it means no reported animation-cancel bugs. Each member works toward a different finish line.

The third condition is an enabling structure. It is partial. The team has good norms of communication, but the task design makes iteration slow. Each change to combat feel requires a full build, which takes 42 minutes. A designer who wants to try three variations of a sword swing must wait more than two hours. Animation changes are hit hardest, because they often need several rounds to look right.

The fourth condition is a supportive context. It is absent in one critical respect. Nobody on the team holds authority to decide when combat feels right. The creative director reviews a build every Thursday and frequently overrides the team's choices, sometimes reversing work completed that week. Tasks marked done on Wednesday reopen on Friday.

The fifth condition is expert coaching. It is present. The lead designer, who sits outside the team, coaches the combat designer weekly, and the team's retrospectives are well run.

The animator is not the reason the team misses its goals; she is the place where four structural problems happen to meet.

Why Animation Carries Over Most

Each of the four gaps lands hardest on animation. The animator's split time removes her from the team when trailers are due. The vague criterion means animation is judged by feel, which is the most subjective part of combat. The 42-minute build makes animation iteration the slowest. And the creative director's Thursday reviews reverse animation choices more often than code, because animation is what he sees on screen. The symptom concentrates in one role, but its causes sit in the team's design.

The Milestone Criterion

Of the four gaps, the vague criterion matters most, because it multiplies the others. If "responsive" were defined, say as input-to-animation latency under 100 milliseconds, no animation cancels in a standard test suite and at least 12 of 16 playtesters rating combat four or five out of five, the team could test its own work. The creative director's Thursday reviews could check against the definition instead of against his impression, and tasks would stay closed when they met it.

Limits of the Claim

This paper leaves open whether individual members could do better, and it accepts that the creative director is right to care about feel. Its claim is that the team's conditions would produce missed goals with almost any four people in it. Hackman (2002) warned that leaders often attribute team problems to members because members are visible and conditions are not, and the studio's own explanation fits that warning.

How the Gaps Turn Into Conflict

The four gaps also explain the friction on the team. When the creative director reverses Wednesday's work on Friday, the engineer and animator each tend to blame the other's part of the combat loop, because nothing defines whose part fell short. Jehn and Mannix (2001) found that process conflict late in a project was associated with poorer performance, and this team's process conflict, about whose time and whose decision, is rising as the milestone approaches. Two retrospectives in a row have ended with the animator and engineer disagreeing about whether animation or code caused a combat bug. Without a definition of done, there is no way to settle the question, so it repeats.

Recommendations for the Next Unit

The diagnosis points to four changes, developed in later units: an agreed share of the animator's week protected from trailer work; a measurable definition of responsive combat; a faster iteration path for animation, such as hot-reloading animation data without a full build; and a decision right for the team on feel, within the definition, with the creative director's review checking against the agreed criteria.

Limits

The diagnosis rests on three sprints of task data, meeting notes and conversations with the four members. It does not include the creative director's view, which a fuller diagnosis should seek. Ratings of present, partial and absent involve judgment. The build time could be shortened by engineering work outside the team, which this paper has not costed.

Conclusion

The combat team's missed sprint goals come from four structural conditions: a boundary that runs through the animator's week, a milestone criterion no one can measure, a slow iteration loop and the absence of a decision right on feel. The animator's carried-over tasks are where those conditions meet, not their cause. Fixing the conditions should fix the symptom without replacing anyone.

References

Hackman, J. R. (2002). Leading teams: Setting the stage for great performances. Harvard Business School Press.

Jehn, K. A., & Mannix, E. A. (2001). The dynamic nature of conflict: A longitudinal study of intragroup conflict and group performance. Academy of Management Journal, 44(2), 238-251. https://doi.org/10.5465/3069453

Wageman, R., Hackman, J. R., & Lehman, E. (2005). Team diagnostic survey: Development of an instrument. The Journal of Applied Behavioral Science, 41(4), 373-398. https://doi.org/10.1177/0021886305281984