Blog comment Tim Wergeni Johansson

Is it clear what is done? Yes, you have clearly conveyed that you had a play-testing session where your gathered feedback. Is it clear how? To a lesser degree yes, the circumstances regarding how the play-testing was carried out is explained. Is it clear why? Yes, to gather feedback but perhaps not motivated very well, you could go into more detail on this. Is the post valuable? in my opinion not exactly, but that might just be because i value […]

Blog comment Simon Ågren

What: I get that you are trying to put focus on the user stories.
How: you make it clear that you broke down the user stories onto a page of ideas and used them to plan your sprints.
Why: you wrote that the user stories made it for your team to understand the coming tasks but It’s hard for me to see how as you don’t go into any further details to motivate how it has actually been useful.
The post is valuable […]

Comment #6

Comment made on Juste Eriksson’s blog post “The game, the good, the bad, the cool, the nice, the lessons learned, the post mortem”
https://justeerikssonblog.wordpress.com/2018/03/20/79/comment-page-1/#comment-15
Very good post. The quick description you give of the game is clear but not excessively detailed, it helps the reader picture what the game looks like without disrupting the flow of the text. You also manage to clearly describe what you’ve learned and the circumstances regarding why said thing stood out to you (Such as […]

Comment #6: Clement

Link to the post
Hej Clement!
You provided a very informative and structured blog post describing the game you created, design decisions behind it and obstacles you came across. I also really like that you provided an introduction describing the game concept itself and a small conclusion. This creates a great framework for the reader to follow.I especially enjoyed that you showed a table with the initial Aesthetics described in the concept, to show which of these goals you achieved […]

Grand Comment Blog

So this will be one long blog with all of my comments on other students blog posts.
Enjoy! orwhatever
Blog1 – Cai
https://caiart.wordpress.com/2018/02/08/development-blog-1perspective-and-boat/
Your blog gives very good insight into the design aspect of your game. The design decisions your team took and why they took them is mostly explained. Since the post focuses mostly on the decisions you made as a group it would however be interesting to read a bit about how you reached these decisions. The ideas behind your […]

Blog Comment 6

Link to designated blog:
https://kaijunqilin.wordpress.com/2018/03/21/postmortem/
 
My comment:
Your blog was enjoyable to read although a bit lacking in details. You talk about why you and your team are happy with the results and reference the last playtest and the positive feedback that you got, but I would like to know if there was anything you guys were not satisfied about and if there is something that the testers did not like because you only mentioned the good feedback you got, and that […]

Game Design Week 7 – Player Feedback

During our development process of Depth, two play testing sessions have been organized for all students partaking in the course, the first one was held after the alpha deadline, and the second one after the beta deadline. The purpose of these sessions was to provide a space for us novice game developers to see our games in action in the hands of a larger crowd. In advance, groups usually prepare questionnaires for testers to fill out to evaluate certain aspects of […]

Blog #2 comment

I’m gonna start by saying that it’s a very interesting choice of topic. Being responsible for sound in my project, and having a little bit of experience with it in the past I know exactly how important it is to put in the time and effort if you want the game to feel as good as possible. I also understand how tedious and boring it can be, though I never had to mix the sounds within code (not for long).
When […]

Blog #1 comment

First of all, a great post! You seem to care a lot for proper preparation and team feedback before any works gets done, which is definitely a big plus for your group. I really enjoyed the overview of your key features, and it’s a really interesting example that you have used as well. Breaking down artifacts into smaller components seems like a great way to reduce possibility of miscommunication/misunderstanding, and I will definitely try it out as well.
The writing is […]

Final Comment

Link to the post
Hello, Merve it’s a good post you have here!
I liked how you chose and covered three important aspects to game development: Your work/experience, Scrum and playtesting. It gives your perspective on what has happened and your experience with it clearly. It is also clear that you have learned a lot during this project which will benefit you in future projects. The only thing I am missing is your opinion on the end result, are you happy […]

Comment Archives: Week #6 – Michael Degirmen, Team Gnoll

On the bright side, you and your group managed to get a workable game out despite the feeling like the universe wanted otherwise. Also, the fact that you and all of the remaining team members didn’t let these setbacks get to them says a lot about you and them.
I know my knowledge of the inner workings of your group is zero and with what I’m about to say, I’m not trying to take away or demean anything about your grievances […]

Blog comment 18-03-22

Blog:
https://thedudeleo.wordpress.com/2018/03/20/blog-6-postmortem/
Comment:
Hello, I’m glad to read your blog, first of all, you clearly introduced the background of the shoot’em up game, this is good. For the readers which first time to read your blog, they can easily understand the project, and they will not feel confused about what we did in this project.
Then, you described some of the understanding of the concept of umibozu concept document. Indeed, before starting the group work, it will lay the foundation for later […]