Mastering big projects with Scrum

-



Whenever you're working on a big project with a group, you need some kind of plan to follow along. Wether you are working on an extensive homework, a garden project or as in our case a game, starting off without any plan will lead to nothing.

This is where Scrum comes into place. Scrum is an agile way of managing work and is widely used in software development and the games industry. The idea behind Scrum is that everybody knows what they're doing, what others are doing and what has to be improved. Scrum also puts a big emphasis on constant feedback.
Using Scrum comes with a Scrum Document, in which you take down Sprint Goals, a Product Backlog, Sprint Planning and Sprint Reviews.

My work in the "Sprint Planning" section of the scrum document
The Sprint Goals define what needs to be achieved each week. This section does not only include milestones like Alpha, Beta and Release of a project, but also user stories for each sprint (usually "sprint" defines a week of work). User stories describe what the user experiences, when he uses the product after the sprint is done.
In the Product Backlog, all the elements of the product are taken down before working on the project in as much detail as possible. Additionally, you write down who is responsible for that specific element, when it should be done and what the risks for being unsuccessful in completing your tasks are. This ensures that each member of the team knows, what has to be done at a certain point of time as well as what is left to be done. Often things in the Product Backlog get scrapped, or additional features get planned, that will be taken down during the development process as well.
At the Beginning of each sprint, the team members meet up to plan what will be done during the week. These tasks get taken down in the Sprint Planning section in the Scrum Document alongside with the responsible person, the estimated work hours and a responsible person for quality assurance.
When the sprint ends, team members meet up again to discuss what they have been working on, how long it took and if they achieve to fulfill the requirements of the current sprint goal or if they arre behind schedule. This assures, that everyone is on track, people do not take too less or too little time to work on their tasks and elements meet the expectations of other team members. It is also an opportunity to give valuable feedback, ask questios or discuss occurring problems.

All in all Scrum is an incredibly useful tool and boosted the productivity of our team by an exponential amount. Especially the feedback loops and the possibility of keeping track of the work you have been done and that lies ahead of you gives a great overview and helps you out a lot when working on your project!



Comments

  1. Unknown27 February 2018 at 04:48

    You do a very good job at explaining what scrum is and why it is used. You go into some very useful details about the scrum document and explain how it is divided and what each section is used for and why it is useful to the team members, and I like how you describe the different stages of a sprint. But seeing as how you go so much into explaining scrum, I would have liked to see some references to some trustworthy source to provide more validity to what you are try to tell your readers, and I think you should have mentioned how your team does things because this felt like it was a general explanation of what scrum is and not how your team used it. You only briefly mention that scrum was useful to your team and I would have liked to know why it was useful and how.

    ReplyDelete

Post a Comment

Popular posts from this blog

The importance of playtesting

-
Image
Testing game play in the Unity editor Recently I realized how important it is to play test your game. I always thought of play testing as a thing a developer has to do every once in a while, but did not take play testing and all of its facets too serious. However, a play testing session that we had at university on Monday proved me wrong. I didn't expect  a lot from the play testing. We prepared a few questions about our game, that we could ask the testers about. Some of the questions were about the play feeling of the game, others were about specific mechanics, music or the art style. Nevertheless, I was actually really confident with our game and did not really expect too much useful feedback, but more response on issues that we already know of. However, when the play testing started, we already faced our first issues. As we never build our Unity project as an actual .exe file, there were a few things we have not tested out. When our testers started playing in full scre...
Read more

Programming a centered bee swarm

-
Image
Finished version of the centered bee swarm following the player The bee swarm in “Game of Beelonging” is one of the main parts of the game concept. Whilst playing the game, there is a bee swarm constantly chasing the player, helping you out when enemies come to close and assigning a new player on death of the main bee. The swarm is supposed to always be vertically centered in a compact swarm, even if one of the bees die, which makes programming the swarm quite difficult. As I was aware that setting up the bee swarm was the most difficult part of creating “Game of Beelonging” I started off with it right away. I began creating ten empty game objects called “slots” representing  all the positions, each of the non playable bees could go to and added a script to each of the slots containing a pointer to their current bee, a pointer to the next slot and a boolean that tells if the slot is occupied or if it is not. The idea was that each bee will constantly ch...
Read more

More Bees, Less Bugs

-
Image
Even though we are creating a game about bees, wasps and beetles, I only want bugs to appear on screen and not in my code. Unfortunately, fixing bugs is a major part of your work as a programmer and can get extremely frustrating when you can not seem to find out what is wrong. Especially after the last playtesting session there were a lot of things that needed to be fixed. For some reason, our main character or his companions occasionally decided to leave the screen, the pause menu did not work, dead things still managed to kill you, bees were hiding behind each other, random pieces of air killed you during the boss fight, the Game Over Screen popped up when you were not actually dead and the Win Screen refused to show up at all. Me seeing my stupid code not working As there was a huge amount of things to fix up, I tried to figure out the best way to debugging in Unity and figured out that there is a lot of approaches that might work depending on the situation. 1. The Conso...
Read more