{"id":1847,"date":"2011-09-06T11:00:46","date_gmt":"2011-09-06T15:00:46","guid":{"rendered":"http:\/\/www.playthepast.org\/?p=1847"},"modified":"2011-08-28T09:13:13","modified_gmt":"2011-08-28T13:13:13","slug":"design-and-development-of-morgan%e2%80%99s-raid","status":"publish","type":"post","link":"https:\/\/www.playthepast.org\/?p=1847","title":{"rendered":"Design and Development of Morgan\u2019s Raid"},"content":{"rendered":"

[This is a guest post by Paul Gestwicki. \u00a0Paul is an Associate Professor of Computer Science at Ball\u00a0State University, where he serves as Undergraduate Program Director\u00a0and teaches courses on game development and human-computer\u00a0interaction. His earlier game-related scholarship involved using game\u00a0engine development to teach advanced topics of Computer Science. This\u00a0has evolved into his current work on interdisciplinary game design and<\/em>\u00a0development, focusing on the relationship between games, fun, and\u00a0learning.]<\/em><\/p>\n

In 1863, Confederate Brigadier General John Hunt Morgan<\/a> led his men on an unauthorized raid of Indiana<\/a> and Ohio. One hundred and forty-eight years later, two professors at Ball State University<\/a> got together to determine how to engage fourth-graders in this story. The Civil War is a key topic of fourth grade social studies in Indiana, and Morgan\u2019s Raid is arguably the most significant part of the state\u2019s Civil War history. The lack of age-appropriate materials and the dramatic flavor of the story gave us the opportunity to create a history education game for use in the classroom. The result of our efforts is the Morgan\u2019s Raid game<\/a>, which we released earlier this Summer.<\/p>\n

\"\"<\/a><\/p>\n

The development process spanned three 15-week semesters. In the first semester, we led an interdisciplinary team of eleven undergraduates on an exploration of the design space. This team learned about the history of the raid, the challenges of teaching social studies, the science of learning, and theories and techniques of game design. This resulted in a set of physical prototypes and a design specification. The following semester, the 25 students in my game programming course (a junior-level elective in the Computer Science department<\/a>) developed the game engine and built the first playable digital prototype. In the final semester, eight developers worked with our artist and historian to produce the final version of the game.<\/p>\n

A key decision that was made early in the design process was that the player would take on the role of John Hunt Morgan. This was a contentious decision as we knew that the player would identify with the protagonist, and yet the target of Morgan\u2019s aggression was Indiana\u2014the player\u2019s own state. When we playtested a digital prototype with fourth-graders who had not yet studied Morgan\u2019s Raid, we observed that they adopted the role of Morgan without questioning their imposed goals and motivation. After playing the game, we asked if Morgan was \u201ca good guy or a bad guy.\u201d Most quickly responded that he was a good guy, and when asked to explain, they answered that he must be the good guy because they controlled him. Simply by posing this question, however, some students began to question their assumptions. One student pointed out that, in the closing cinematic, Morgan ends up in prison. In admirable fourth-grade logic, this means he must be a bad guy, because good guys do not go to prison. With another group of testers, when we asked where Morgan was raiding, the students acknowledged that it was Indiana. Once again, through moderated discussion, the students began to consider that perhaps Morgan was not a \u201cgood guy.\u201d Identification with the protagonist was an expected default response, and it exemplifies the strength of structured reflection to fostering learning. Note that our design goal was neither to demonize nor glorify Morgan, but to represent historical events and to foster the development of multiple perspectives.<\/p>\n

The game design underwent significant evolution between the end of the first semester\u2014when the design document was written\u2014and the release in early Summer 2011. The design document required the player to decide, at each town, whether to raid, avoid the town, or deceive the population into giving him supplies. These are historically-accurate options, and selection was to be made through a three-button dialog box. During the second semester, as more variations and features were considered, more dialog boxes were added. Two weeks before the end of the semester, we had our first feature-complete digital prototype. Internal playtesting forced the team to make a startling realization: the game was not fun. We had approved beneficial, incremental alterations to the design but had failed to foresee that the sum of these was a monotonous chain of click-through dialog boxes. The aftermath of this realization demonstrates the success of the project as a learning experience: the team was forced to acknowledge their mistakes, reflect on the causes, and develop solutions that would fit into the project schedule. I am pleased that the team went immediately to the most powerful tools of game design: whiteboard, markers, construction paper, scissors, and Skittles. By the end of the semester, the team had built a shared vision of a resource-allocation game much like the one we finally shipped.<\/p>\n

This illustrates what I consider to be the greatest learning opportunity inherent in game design and development: the internalization of design thinking. Design thinking<\/a> provides a disposition to approach open-ended design problems in a way that complements the philosophy of agile software development<\/a>. I am partial to George Kembel\u2019s formulation of design thinking<\/a>, which presents a five-step cycle<\/a> of empathy, identification, ideation, building, and testing. Playtesting with end-users was crucial to the team as it allowed them to develop empathy, not just intellectually but also tacitly and emotionally: the team had been physically in the spaces where the game would be played, and they had sat and engaged with \u201creal live ten-year-olds.\u201d Following Scrum<\/a> with two-week sprints, we were building something that could be tested every two weeks, and we were taking the time to reflect on our successes and our failures. These students were immersed in reflective practice, and already I have been able to see them apply these principles to new problems and domains.<\/p>\n

Mentoring the team through the design and development of Morgan\u2019s Raid has been the most personally and professionally rewarding experience of my career so far. I am proud of how the interdisciplinary team learned to trust and respect each other. I believe this project is an exemplar of the potential for the future of higher education. We were fortunate to have significant internal support for the project, but we were also very lucky that students\u2019 schedules worked out as they did. It is my hope that higher education reform will consider projects such as this and others featured on this blog as ideal candidates for the new normal for student learning experiences.<\/p>\n

Play Morgan\u2019s Raid for free online at https:\/\/sites.google.com\/site\/morgansraidgame\/<\/a>. Special thanks to my collaborator, Ron Morris<\/a>, for his dedication to the project. You can read more about the design and development of Morgan\u2019s Raid on my blog<\/a>; search for \u201cMorgan\u2019s Raid.\u201d<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

[This is a guest post by Paul Gestwicki. \u00a0Paul is an Associate Professor of Computer Science at Ball\u00a0State University, where he serves as Undergraduate Program Director\u00a0and teaches courses on game development and human-computer\u00a0interaction. His earlier game-related scholarship involved using game\u00a0engine development to teach advanced topics of Computer Science. This\u00a0has evolvedContinue Reading<\/a><\/span><\/p>\n","protected":false},"author":16,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[15],"tags":[],"coauthors":[],"class_list":["entry","author-pastplayer","post-1847","post","type-post","status-publish","format-standard","category-articles"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.playthepast.org\/index.php?rest_route=\/wp\/v2\/posts\/1847","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.playthepast.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.playthepast.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.playthepast.org\/index.php?rest_route=\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.playthepast.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1847"}],"version-history":[{"count":7,"href":"https:\/\/www.playthepast.org\/index.php?rest_route=\/wp\/v2\/posts\/1847\/revisions"}],"predecessor-version":[{"id":1855,"href":"https:\/\/www.playthepast.org\/index.php?rest_route=\/wp\/v2\/posts\/1847\/revisions\/1855"}],"wp:attachment":[{"href":"https:\/\/www.playthepast.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1847"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.playthepast.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1847"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.playthepast.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1847"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.playthepast.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcoauthors&post=1847"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}