Scrum
|
This week we have been tasked to talk about scrum and how it has affected our development. In other words, how has the scrum method worked compared to other methods of developing a product as a team? Well, the answer to that question is “In relation to what?”. I have never followed any method other than that of a basic schedule, and most group projects I’ve worked on has lasted only one week – the exception being a project lasting 4 weeks, however that only included me and one more person. Anyways, I have noticed a few advantages of our current work method. First and foremost, the daily stand-up meetings! This is great, as it keeps everyone in the group up to date with what everyone else is doing, and in does encourage you to work a bit harder so that you’ve more to show the next day. It is also an opportunity to discuss the project at large, and to make sure that the work you’re doing is easy for whoever you hand it over to once you’re done. For instance, if you’re creating sprites for a set of 2D buildings, the programmer might prefer if they all have the same shape at the base, as he/she can then use the same collision box for each building, instead of having to create a new collision box for each individual building. Reviewing and discussing the schedule on a weekly basis, as well as the iterative design process are two other benefits of working with scrum. However, this is what I’m used to when working with projects, but it’s worth mentioning. The last bit of praise for the scrum method is simply the project managers. It is great to have someone that can arrange and guide us through our daily meetings, and it’s very noticeable once they’re not present during a daily stand-up. Scrum does seem to have some rigid and arbitrary aspects to it. Perhaps this is either because it’s still a bit new. Once you know it better it might be easier to shape it into something that the group is more comfortable and happy with.
5SD064  |
