Managing a Game Project, week 1
|
SCRUM The first week i started out to explain to the group what SCRUM is in more detail. I also explained how we were going to use it togheter with the game concept document we choosed. With this i also got help from Joel.P who has been though some SCRUM in design class with Adam Mayes. What? I explained for the group what SCRUM is. I started with the basics like were SCRUM came from and how it got invented. This didnt really matter to much to the group itself but it could make the group understand why WE are using it. The group responded well to this and seemed happy with they way we were going to work, ”Finaly some structure in the work we do” said one member. I learned here that non in the group had been working with this method before so i realised that it might be hard to follow a too scructured SCRUM planning. How? How does SCRUM work and how did we choose to work with it? We got a premade Google Docs document from Marcus in wich he wanted us to fill in the following things: User stories/Sprint goals, Product Backlog, Sprint Planning and Sprint Review. Since we need som pictures in the blog i will now show you how the diffrent tabs looks and how we choose to struckured them.     Of course i had to explain all this to the team. How does it work? After this you go to the Sprint Planning tab. Here you choose what Artifacts you need for the following Sprint. See row 16 in Sprint planning for example. Its just a copy of the Artifact in row 7 from the Product Backlog. This makes it simple to see what you should do this week and also removes stress since you would not have to look at the Product backlog for a week. For the sprint Review you just put in what you finished, how long time you spent on an Artifact and if it got done or not. This is one thing i did the first week to help the group get going. We did this togheter and with the help of Love our wonderfull SCRUM master! Chaoilao! Yeah i made that word.  |