|
Hey Tim,
great blogpost! I think you start of well with a nice introduction and concept summary outlining the game your group has been working on and what your blogpost will be about.
It is interesting to read about how the mentality of going into the development process is affected by the premises – did going into development with this mentality prove a hindrance in some way? For instance, did the reluctance to redesign certain aspects prove problematic, and is there something to be learned for future projects?
The way you have separated the blogpost into different parts in which you outline, for instance, what you have learned in relation to “design” and later “programming” is a nice way of distinguishing between, and analyzing, what you have learned – it also makes it very easy to follow when reading!
You also do well in explaining what you have learned following the decisions you and your team made by writing what lessons you have learned at the end of each section.
You also give a good run-through of what you have learned using SCRUM, but maybe you could have specified more clearly why it was a bumpy ride. I know that you have already made a blogpost about SCRUM specifically, but it might have been nice to have a few sentences to explain what some of the issues were.
Explaining what you have learned from working with your group in relation to non-violent communication etc. and relisting the lessons is a great way to end. Finally, I just want to add that it was very interesting to read your blogpost! Good luck with the arcade course!
-Jeppe Willatzen
About Jeppe Willatzen
2017 Programming
|
