Review of the Scrum pattern

It has been five weeks since we start to follow the Scrum working pattern, I got fully used to it and realized a reliable project management will increase the efficiency and cooperation of the group to a large extend.

“The Scrum is a lightweight framework designed to help small, close-knit teams of people develop complex products. A scrum team typically consists of around seven people who work together in short, sustainable bursts of activity called sprints, with plenty of time for review and reflection built in.” (Lecture notes, Adam 2017, Game design department) A Scrum team consisted of three roles which are Product Owner, Scrum Master and Team members. In our case, our project manager is both the Product Owner and the Scrum Master and the rest of the people are team members.

First of all, thanks our project manager for organizing meetings and presenting the Scrum every week. I know it was an annoying process to keep every member to fill the estimate time and actual working hour, but I still left some blanks in Scrum document every week especially on the first and second week. Despite previously setbacks, it works great right now. As a team member, I not only need to finish the work, but also have to document the process punctually on the backlog which will save a lot of time for the Scrum master.

What Scrum improved me in the project? It set a criteria and a load of work (20 hours) I need to achieve every week and kill the possibility of been lazy. It’s common as the project goes on the speed of individual members slows down. For those hard working people, it’s more like a reminder to tell you what standard you need to reach. In addition, since you cover and break down all the things you need to do at the sprint plan meeting, it helps you to come up with details you maybe encounter in later process. You could go through problems with the group and receive instance feedback in advance which increase efficiency drastically.

Unlike the game jam you rush everything as fast as possible, a long project requires a all-round, ordered management. As a first year student, it’s the first time I know how a group actual works. You can’t decide how the game looks like by yourself like the individual project in programming lectures. However, it’s good having someone also tells you what to do next. I like my team and I hope everything goes well in future.

7

1 Comment

  1. Your blog post gives the reader a good over view of how to work whit scrum and what it is. But you could have introduced yourself more in the beginning of the post because the reader maybe doesn’t know who you or what scrum is.
    You write that you have used Scrum for a few weeks but not much more about what is done during this time you have used scrum. Maybe write more about what has been done this weeks.
    You do write about what scrum is and how it is used but you don’t write much about how the sprint planning worked or the standup meetings. Because the reader may not know what scrum is.
    You don’t write about why Scrum is used during this week’s so maybe write more about why its is used in this course and why your team is using it.
    But you do write about how scrum have affected your team work and the effect it had on you. And how it has affected your development throughout the weeks. This is good for the reader because if someone that are using or are going to use scrum would read this blog they may get good ideas on how to use it and why to use it.

    Oskar Karlsson

    Liked by 1 person

Leave a comment