Team Global Trailers

• One thing I would have done different given the choice, I would probably spent more time on domain analysis. I wasn't very familiar with Oregon Trail, and didn't really put much time to understand it thinking it wouldn't matter much. As it turns out, I felt I lost important opportunities to make our team's version of game more interesting and robust. I wish we had designed some of the classes in different ways. Especially, how the events are generated with location classes is something I would implement differently. So we could have multiple interesting events generated at the same time. There are random events and location specific events. Even though they are just events, the way they are generated and interacts with other classes are very different in their domain. I believe that we could have better structured events and their interactions if the events were analyzed deeper.
• If you pick your friends to be in your group just because you want to be nice to them, you will go through some rough patches with them throughout the semester
• One thing you should consider when assemble your team, please take consideration of programming skill level. This class does not judge the programming too critically. It's all about deliverable. How good or bad your programs doesn't matter much as long as your team can meet the requirements. That's why it's very important to even out your team's talents as much as possible, so that all members would share the same amount of the burdens. Like I said before, the program doesn't need to be the most efficient or smartest in this class. That's not the point. As long as your team can get the job done, you would be fine. If all members has equal skill levels, then your team members would work as hard as you given your team is well managed.
• Also, try to have a CM major in your group, it DEFINITELY helps our for GUI coding or UI evaluation, they have more knowledge about it. And it helps seeing things in a CM perspective than just the CS.
• Start early in your milestone but be sure to take breaks and relax
• Divide up the work, so everyone gets a part and there won't be any overlap
• Communication is very important so make sure you have the email or phone number of everyone in your team
• If a team member is not doing what he or she is supposed to do, try to talk to him/her first to clear any kind of missunderstanding

Link to this Page

• Cases last edited on 30 July 2011 at 2:33 am by r59h132.res.gatech.edu