Structuring the Documents, Week 2
|
What? So last week i described how everyone we’re going to use SCRUM. I also told you that some people did not read up on what it is and that kind of leads us to this week’s topics, Structuring the documents. In a project like this, and especially for a project manager, it is not only about the SCRUM chart. Its also about planning meeting, taking notes and with that documenting ideas. All of this is done in different documents to keep it more organised. How? So in the beginning i did not really know what the team wanted me to note, do or fix. I stayed a little in the background to see if there was a clear thing missing that i could help out with. Unfortunately ( rather the opposite ) for me my team did a lot of thing by themselves. I was trying to think of something i could do but could only remember what the teacher Monica told me ”As a project manager, try to act like the designers right hand. If the designer needs any help you should help him”. So i asked Joel, Our designer, if there was anything i could do. It turned out he wanted me to note as much thing i could during meetings. The result was me noting ideas, small things to add in the backlog. One thing i documented really detailed was the new systeming of the folders we were gonna use in Unity. This looked something like this:  Why? Why take notes, organising and keep track of things during a project? In a project, big or small, you should try to keep track of everything. This makes it a lot easier if you would need to change something to what it was before or if you want to remember something that was said during a meeting. Documenting things is also good for learning. If a company do another project of similar contrast and have a problem, reading how the previous project was made might help them both save time and money. That’s it for me this week. Next week i might talk about something els than documentation like SCRUM and taking notes since we are having trouble with the art guys! Bye!
 |