Below is my evaluation of how my team has worked together on our 'Studio Project' this term. My team comprises of; Charlie Sykes, Shaun Slade, Jessica Magnus and myself.
How we've worked as a team;
I think that Charlie, Shaun, Jess and I have worked extremely well as a team on this project. We have met as a team almost every day we have been timetabled into uni for lectures by meeting up early in the morning if theres an afternoon lecture on a Monday, similarly with Tuesdays and often staying on after CS sessions to continue work and discussions.
One of the reasons I feel we have been so successful in co-operation is that we are all seriously committed to giving the project our all. Even though only one of us is based in Norwich, and 3 of us balance uni work with part-time jobs, we have kept up-to-date and worked hard when we can.
A key element to our teamwork has been the excellent level of contact between team members - primarily through our Facebook Group. This group has allowed us to essentially create a dev-diary which is private and purely for group use. As work is produced, ideas thought of, written work added to - it is all uploaded to our FB group instantly allowing all members of the group to access it, comment on it and in some cases edit and re-submit it. This organic process of creation and evaluation which has gone on through out the project has allowed us to collaboratively work as a team even over the weekends when we are apart.
When in university together, we often use the time to debate our latest ideas, re-assess group-members roles and tasks ahead. Often Shaun will be the member of the group questioning why we have made these decisions - challenging our thinking and forcing Jess and I to justify our decisions. Charlie is usually the member who quietly listens to both sides and is dragged in to mediate! This might sound like these discussions are confrontational, but now that Shaun, Charlie and I have worked on projects before together in the First Year, we are easily able to understand each other's reasoning behind comments. This level of personal and professional familiarity allows us to push each other, to openly question and critique each-other without fear of real offence. This is at its clearest when I am critiquing an image Shaun has posted on the group - his work is great, but I know it can be better - and I will make a comment about his anatomy or posing of a character. Shaun will complain that I am never happy with his work, but usually up on reflection he realises that I was indeed correct in my comments, and a better outcome is achieved overall.
Jess is new to the course, and to the group - but not new to me. We have been friends since freshers week last year and so I thought for her daunting first project on Games it would suit her best to be working with someone she knew well and who I know she has no worries asking for help from. A key element of good work is when people feel free to ask for help, question decisions and have fun and I honestly feel that we have achieved this without deliberation.
How we've worked as a team;
I think that Charlie, Shaun, Jess and I have worked extremely well as a team on this project. We have met as a team almost every day we have been timetabled into uni for lectures by meeting up early in the morning if theres an afternoon lecture on a Monday, similarly with Tuesdays and often staying on after CS sessions to continue work and discussions.
One of the reasons I feel we have been so successful in co-operation is that we are all seriously committed to giving the project our all. Even though only one of us is based in Norwich, and 3 of us balance uni work with part-time jobs, we have kept up-to-date and worked hard when we can.
A key element to our teamwork has been the excellent level of contact between team members - primarily through our Facebook Group. This group has allowed us to essentially create a dev-diary which is private and purely for group use. As work is produced, ideas thought of, written work added to - it is all uploaded to our FB group instantly allowing all members of the group to access it, comment on it and in some cases edit and re-submit it. This organic process of creation and evaluation which has gone on through out the project has allowed us to collaboratively work as a team even over the weekends when we are apart.
When in university together, we often use the time to debate our latest ideas, re-assess group-members roles and tasks ahead. Often Shaun will be the member of the group questioning why we have made these decisions - challenging our thinking and forcing Jess and I to justify our decisions. Charlie is usually the member who quietly listens to both sides and is dragged in to mediate! This might sound like these discussions are confrontational, but now that Shaun, Charlie and I have worked on projects before together in the First Year, we are easily able to understand each other's reasoning behind comments. This level of personal and professional familiarity allows us to push each other, to openly question and critique each-other without fear of real offence. This is at its clearest when I am critiquing an image Shaun has posted on the group - his work is great, but I know it can be better - and I will make a comment about his anatomy or posing of a character. Shaun will complain that I am never happy with his work, but usually up on reflection he realises that I was indeed correct in my comments, and a better outcome is achieved overall.
Jess is new to the course, and to the group - but not new to me. We have been friends since freshers week last year and so I thought for her daunting first project on Games it would suit her best to be working with someone she knew well and who I know she has no worries asking for help from. A key element of good work is when people feel free to ask for help, question decisions and have fun and I honestly feel that we have achieved this without deliberation.
No comments:
Post a Comment