Despite having no homework, tests, or commitments outside of class, I've found it difficult to make time to write this semester. The type of thinking I do most days leaves me drained, and whatever energy I have left is typically zapped by my evening commute home.
At any rate, today was such a good day that I can't help but write a bit. I'm working on a project at the Virginia Ball Center, which has been a very rewarding project. I've had the chance to work with some quirky, brilliant people. As a group, we've been doing game design and internal play testing for the better part of two months. Game design uses a part of my brain that I find very taxing, but today was a bit different.
As our project moves away from game design and into software design and development, I get the chance to actually write software. I'm not resentful for things taking as long as they have; at any point, I could have said,"I don't feel like prototyping any more, I'll just write some code." But I feel that I have a good idea as to the creative direction that the game is going in. It wouldn't be fair to drop someone else into this role, I have too much momentum to do anything other than hashing out game mechanics,IMHO.
With most of the game designing done, I was able to focus some attention today on a programming task. I jumped into things via pair programming. I navigated, while a team member steered. We employed the builder pattern for the section of code we were working on, which I had not had the chance to work with yet. Today was also one of the first chances I've had to make use of some of the concepts within Clean Code, by Robert Martin. The Computer Science students within the team are reading through this book together, and we've all found it very informative.
Once our code was refactored and we determined that no code smells permeated the air, it was lunch time. After some discussions around the dining room table and our respective meals, the Computer Science students involved with the project came together and put in some really solid collaborative work regarding use cases—something none of us were proficient with yet.
Overall, the project is beginning to really come into focus. The game is taking the shape of a game, and it's hard not to be excited! Throw some gorgeous leap-year day weather into the mix and it's easy to see why today was so great! I'm looking forward to the lessons I'll learn and the tools I'll pick up in the next two months.
Showing posts with label immersive learning. Show all posts
Showing posts with label immersive learning. Show all posts
Wednesday, February 29, 2012
Wednesday, July 27, 2011
Archaeology Simulation Assessment
The end of this past week saw the Digital Archaeology Project reach it's scheduled ending date. The team worked for 5 weeks on developing a digital, educational experience that was appropriate for a 4th grade level of student. This post will focus on the positives and negatives of the project.
Background On the Project
The team on this project consisted of eight students, four CS students and four Anthropology/History students, as well as three faculty advisors. The focus of the project was to create an experience that accurately depicted the archaeology process. The player would discover an artifact through digging, categorize the artifact, explore the house for more artifacts, research their findings in the library, all the while opening up interpretations. Their findings and research allowed them to make claims about the people who inhabited the land.
Our goals were pretty lofty considering that we had zero starting out. Knowing this, our advisors realized that we wouldn't be able to give the game the polish it would need. Therefore, our team of eight students would be in charge of the game design and initial development of the software. We wouldn't put the polishing touches on it, but we would have the game working completely by the end of our project. Then we would hand our product off to another on-campus organization to polish it up and prettify it.
Results
At the end of our 5 week period, we have a game. It's very, very raw, but it is a game. The data is there, the game flow is there. It's just ugly. It's all programmer and placeholder art, which is notoriously hideous, but it did it's job.
We didn't have to change our goals to meet our production rate, which is good. However, our goals were very, very aggressive - perhaps too aggressive. We weren't in a place where we could playtest a prototype with actual 4th graders, so we're carrying quite a bit of risk still. I say 'still' because the game can still be changed, once what's there is beautified. There are plans to playtest it and tweak what needs to be tweaked.
In the vein of SCRUM, I'll lay out areas that were successful and those that needed more work.
Positives
Conclusions
After everything is said and done, the project was a success. We set out to create something educational while still being accurate and we did that. Things weren't perfect, but I feel that we (the four CS students and two of the advisors who have worked together before) are perfecting our process.
I'm glad to have taken part in the project and I would encourage others to look for similar Immersive Learning opportunities. While these projects are great learning opportunities, one problem with Immersive Learning is that not every major supports it as well as they could. I know that art students in particular have trouble finding room in their schedules to accommodate it. If I were on a tighter schedule I may not have had time for this project.
I'll use this experience, and the Morgan's Raid experience, to make the most of this Spring, where I'll be working on a project at the Virginia Ball Center. I'm really excited about this opportunity, and I'm sure I'll blog about it in the coming months. I'm not entirely done with the Archaeology Project, as I'll likely be doing some additional development on it in the next few weeks, but I'm proud of what we were able to accomplish.
Background On the Project
The team on this project consisted of eight students, four CS students and four Anthropology/History students, as well as three faculty advisors. The focus of the project was to create an experience that accurately depicted the archaeology process. The player would discover an artifact through digging, categorize the artifact, explore the house for more artifacts, research their findings in the library, all the while opening up interpretations. Their findings and research allowed them to make claims about the people who inhabited the land.
Our goals were pretty lofty considering that we had zero starting out. Knowing this, our advisors realized that we wouldn't be able to give the game the polish it would need. Therefore, our team of eight students would be in charge of the game design and initial development of the software. We wouldn't put the polishing touches on it, but we would have the game working completely by the end of our project. Then we would hand our product off to another on-campus organization to polish it up and prettify it.
Results
At the end of our 5 week period, we have a game. It's very, very raw, but it is a game. The data is there, the game flow is there. It's just ugly. It's all programmer and placeholder art, which is notoriously hideous, but it did it's job.
We didn't have to change our goals to meet our production rate, which is good. However, our goals were very, very aggressive - perhaps too aggressive. We weren't in a place where we could playtest a prototype with actual 4th graders, so we're carrying quite a bit of risk still. I say 'still' because the game can still be changed, once what's there is beautified. There are plans to playtest it and tweak what needs to be tweaked.
In the vein of SCRUM, I'll lay out areas that were successful and those that needed more work.
Positives
- Diverse team
- we had a very diverse team, but we were able to find a group identity and work well together.
- SCRUM
- we used what I would call SCRUM lite, but the parts of it that we did use worked well. The group took to it quickly.
- New technology
- the tech team (the CS students) picked up C# and Unity3D quickly. It was fun to work with new software.
- Built off of past success
- Speaking from a tech team perspective, the Morgan's Raid experience was helpful in this project.
- Empowered team
- the faculty advisors did a good job of directing us initially, but by the end, the students were making the decisions, even the big ones
Negatives
- Pressure of lofty of goals
- while we were successful, had our goals been smaller we could've polished the game mechanics more
- Feelings of being unfulfilled
- handing off a project to someone else to finish isn't enjoyable. You get protective of a project and to see it go before it's done is a little saddening, even if it's necessary.
- Empowered team
- having the students making the big decisions led to moments where the decision took longer than it might've, had an advisor just dictated what to do.
- Short deadlines
- having such a short timeframe for a big project led to some software debt. At the time, it made more sense to keep implementing new features instead of refactoring. Also, our Product Owners didn't dictate that they wanted code refactored, so I'm not sure who should've spoken up.
Conclusions
After everything is said and done, the project was a success. We set out to create something educational while still being accurate and we did that. Things weren't perfect, but I feel that we (the four CS students and two of the advisors who have worked together before) are perfecting our process.
I'm glad to have taken part in the project and I would encourage others to look for similar Immersive Learning opportunities. While these projects are great learning opportunities, one problem with Immersive Learning is that not every major supports it as well as they could. I know that art students in particular have trouble finding room in their schedules to accommodate it. If I were on a tighter schedule I may not have had time for this project.
I'll use this experience, and the Morgan's Raid experience, to make the most of this Spring, where I'll be working on a project at the Virginia Ball Center. I'm really excited about this opportunity, and I'm sure I'll blog about it in the coming months. I'm not entirely done with the Archaeology Project, as I'll likely be doing some additional development on it in the next few weeks, but I'm proud of what we were able to accomplish.
Subscribe to:
Comments (Atom)