Hello there.
This week I am going to talk about how scrum has affected the project of creating the game “Depth”. As the project manager of the team, this has been immensely helpful. Reasons for this is that it helps with communication, since everyone knows what everyone is doing, has done and will do for the rest of the week/sprint. This way, I can have an easier time to analyze how I can help with problems that the team have and can get. I say “can get”, since by analyzing the items they are working on, I can also prevent problems, before they occur.
It is also very good to use, since it tells us to have daily stand up meetings. This makes the group talk to each other and explain their problems. The procedure in my team is to have the daily stand up meeting and after that have an additional meeting right after, where we try to solve and discuss the problems in further detail. Though, most of the time we do not have to have many discussions at those times, since we have a clear constant communication.
Other benefits with scrum, that have helped my team is the backlog. The backlog has given the team a clear view on what has been done and what has to be done. It boosts morale, since it clearly shows the progress made. It also helps the team prioritize what has to be in the game and what should be scrapped in case there would not be enough time. Though this is not something my team have had to think about, it is nice to know what is to be prioritized in case of unforseen events.
The problems that using scrum has caused, is that some members of my team are disliking using it. This, because they feel like it is stopping them from doing what they want to do, at the moment. Instead they follow what was agreed upon with the rest of the team at the beginning. Though, they do understand the benefits of using scrum and do agree that it is very useful.
To summarize, overall scrum has been very useful and help the team with communication, as well as problem solving and prevention.
Nicklas Rosén 
Hi Nicklas! Reading your blog about Scrum, (and considering a game version I had opportunity to test yesterday and which impressed me a lot,) I can see that you implemented Scrum sensitively, based on needs of individual group members, rather than pushing Scrum in a rigid manner. For example, your approach to make Daily Scrum Stand-up meeting, followed by additional meeting to go more in depth, seems to be effective way how to manage complex issues of the game development. On the one hand, you realized benefits that Scrum brought to your team, such us keeping a product backlog helping you to manage the task in your group, or keeping transparent communication between group members “…since everyone knows what everyone is doing, has done and will do for the rest of the week/sprint”. On the another hand, you mentioned a problem with acceptance of Scrum as a project methodology by team members, as you wrote “..some members of my team are disliking using it”. It’s not surprising, as most of students have little or no experience with Scrum, they tend to use simple and more natural methods how to reach a goal, and may consider Scrum as too synthetic and so “unartistic”. Although Scrum should be easy to implement, it doesn’t mean it’s without facing resistance of adopters to change, and here Scrum Master could help a team to deal with it. Finally, I like you pointed out that “… we have a clear constant communication”, which I can feel is reflected in your current product – a game prototype with high coherency between visual art and game dynamics. Good luck! //Karel
LikeLike