Blog comments
|
Comment #1 Hey Michael, I found your blog post to be very helpful and informative. I appreciate the way that you went and explained each program and application that you used when making the sound effects. This information will be helpful should I ever be part of a team that has no experience with sound design. However, I also feel that you went and repeated yourself a bit with some of the information in the first couple of paragraphs. I liked how you talked about your process in coming up with ideas for sound effects, and how you would edit the existing ones in order to create the ones you had in your head. While I did like the way your text flowed, the overall tone of the post seemed a bit condescending. I’m assuming that you are writing with this much detail in order to explain to people that have no sound design experience (like me) a clear explanation on how to do it. Overall it’s a great post! https://michaeldegirmen.wordpress.com/2018/02/08/creating-the-first-sound-effects/#comment-3 Comment #2 I really enjoyed your article! The way you have it written so that it resembles a story is really interesting and fun. I liked the way that you went and found a way to to make even your meeting time and location seem like it was utmost importance. Other than a few grammatical errors, I found the flow of the text to be good and easy to follow. One other small problem that I noticed while reading your post was that I could not seem very clear to me how you and your group went about preparing for this. I like how you stressed the importance of needing the pre-alpha to go well and your not being entirely sure whether or not you guys would pass. That feeling of uncertainty seemed to be a common theme among the rest of the groups. Overall a great article! I hope you keep up with this writing style! M. Causey https://sasadzigurski.wordpress.com/2018/02/15/pre-alpha-story/ Comment #3 Hey Alex, Sorry for the incredibly late reply, but I enjoyed reading your post. My group also had some problems when it came to using the spreadsheet, but we choose to stick with it since it appeared to be required. It’s interesting that you had group members who were already familiar with using Scrum. Since this was our first time using Scrum it did not go as well as could have. Hopefully, it will go better during the arcade project now that all of the team members will have experience with Scrum. The way you set up how your group planned out the daily stand-up meetings was a good idea. I may try that with my new group, along with using a Trello board instead of using the google spreadsheet. Of course if it turns out that we will need to use the spreadsheet for hand-in purposes then we will just stick with that. Overall this was a great post. Comment #4 Hey Niklas, M. Causey https://niklasericssonblog.wordpress.com/2018/03/03/sprint-6-beta/ Comment #5 Hey Elias! I liked your post, it was well structured and easy to follow. The way you described how you and your team view the whole playtesting sessions was very informative. I missed the last playtesting session, but from I heard from my group they also did not have anything that they wanted to test that could be measured with quantitative data. I like that they were not the only group that went with an observation approach. It sounds like you guys got some good insight into what your game needed in order to be improved. It seems that your team took the feedback seriously and went and made a tutorial that would give the player as much time as they would need in order to learn how to use your game, which can only lead to them having a better gaming experience. I look forward to testing your game on Thursday! Mija https://managinggamemaking.wordpress.com/2018/03/08/design-build-test-learn/ Comment #6 Hey Juste, since I made the mistake of commenting on Elias’s blog last time, I’m commenting on yours this time. I found your post to be quite informative and easy to follow. The way you described your group dynamics was very open and honest (nice use of a fake name), but not in a way that you are bashing your problematic group member. It was nice to read after hearing about other people who are just going to write about how their team members were uncooperative. I have taken a lot away from your post, it is clear that you learned a lot from this project and the fact that you took the feedback that you got into account and worked with it to improve your game was great. I also liked the fact that you included your scrum master and asked them for help when you had issues with your group, I wish that I had done that more often. I’m going to try and use the solutions that you and your scrum master came up with in regards to communication among the different team members. Overall this is a great post, and I know that I give very unhelpful comments. I’m looking forward to seeing what you and your new team make in the next course! M. Causey https://justeerikssonblog.wordpress.com/2018/03/20/79/  |