Blog #3 Scrum

The best thing with working with agile scrum has been the daily standups. Getting a quick overview of what everyone is doing really increases the communication between the different minors. It’s been a really good way of making sure you’re not completely off track. Working with the sprints however, has been more of a struggle – at least in this project. The weekly sprints makes for a lot of time being time for meetings. Since we have had lectures on many of the weekdays, there’s not a massive amount of time after to work on the project. And when you factor in the 4 meetings of playtest, sprint review, retrospective and sprint planning, it feels like it takes a great toll on the amount of time you can spend working. Yet, I think it’s a good way to introduce us students to the method. In our group, these meetings tend to drag on for quite some time, which might be why I consider it to be a hassle. But these last couple of weeks has been great to repeat the process and greatly increase the efficiency of these meetings.

We’ve also had troubles working agilely. When we first sat down to plan which artifacts were needed for the alpha, the list hasn’t changed much until now. The requirements from the course of what needed to be in the game was practically all our group had time doing. Therefore, making sure the game was “fun”, or matching our esthetic felt minor in comparison to making sure sure everyone would pass the course.

If you can’t find the game you’re making enjoyable, how would others? Although you’re not creating games for yourself, you need to see what others would find enjoyable in your game. And I think that is what has been missing for our group while using scrum. Working towards a minimum viable product (MVP) and testing it out to make sure it’s entertaining felt second in priority to getting a grade.

Despite everything I wrote, I’m really inspired by what working with Agile Scrum can accomplish. I naively think that a fun development process has a higher likelihood to end up with a better game. And through working towards a MVP, I think the team has an easier time seeing the whole picture, not getting as caught up in details, and getting joy seeing the game evolve in a different way from waterfall production. Especially since we all major in game design, seeing and pointing out flaws or strong points of the game throughout every step in the development will undoubtedly lead to a better experience once it’s complete.

TL;DR I think one week is a too short duration for a sprint, but it works well as practice, the goals of the course prevents some of the agile scrum strong points and working towards a MVP could be a very fun and good way to create games.

Thanks for reading, sorry if it turned out quite ranty!


6 thoughts on “Blog #3 Scrum

  1. Thanks for writing. I’m sorry to hear you have some issues with finding the fun, but I’m glad to see you writing it out. It shows that you’re reflecting on what you would like to do better next time, and it is ultimately the best way to learn. The reader gets to digest your challenges as well as your positives to using Scrum.

    Your honesty is appreciated here, as honesty will in the end offer better learning experiences for both you and the reader, instead of a false image that you did everything right the first time. Maybe your group can work out some of your Scrum issues for these final sprints?

    I don’t think you need to apologize in the end. I didn’t consider the text to be “ranty” until you suggested it, and then you started to color my view of your text. Reading it a second time it still works and isn’t a “rant”, so feel free to remove that part.

    Look forward to reading more. =)


  2. Thank you for this post. It was interesting to see what aspects of scrum has worked for your team, as well as what has been more challenging. I agree with you that a “fun” development process increases the chance of a good product.

    As mentioned in the comment above, your post did not give me a “ranty” impression, and for the most part I had no problem following your thought process. However, your descriptions of your struggles with the sprint could have been formulated differently. I understand what you want to express, but I believe the sentence “The weekly sprints makes for a lot of time being time for meetings.” is a bit confusing. If I am to give you an example, I think “A majority of the time intended for the sprints, is instead spent on several different meetings.” is a better way to phrase this thought.

    All in all it was a very enlightening post, and it is good to see that you can identify the problems of your working process in order to successfully improve your team’s efficiency.

    Keep up the good work 🙂


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s