#cardsforplay2015

[atomic--sloth]

27.03.15 | Cards For Play: Special Delivery

Look what just delivered to my door! Line Racer version 1.0!

The plastic cards are amazing. I can’t wait to show the rest of my teammates!

[themightyblogster-blog]

Reflective Statement

(continued, or rather separate from the earlier reflection)

We had some really stressful times and i think it all hit us during our presentation. 

Our presentation didn’t go as we planned, but it was a fruitful experience. I’ve understood a bit more about decision making. We learn from our mistakes and our presentation only serves to help us grow and become better. Our cards are complete  but it seems we didn’t advertise that very well as Ben didn’t see it that way. Not many people got the idea of our cards but im sure if they play a game, they’d have fun. 

I was a little disappointed how Ben didn’t spend more time on our presentation to discuss. It was our fault the presentation didn’t go well, but I was hoping to redeem a few points with any questions he had or other things.

I got to see how creative other people can be with their presentations and that also hit me hard. We could’ve made a better effort but what’s done is done, and i’ve definitely learnt from this.

I was a tad confused how some people didn’t follow the regulations, if their presentation is marked wit the same standards as ours, then that’s a marking flaw. If we had the chance to make videos and other things, we could’ve made our presentation a lot better. Im sure others feel the same or similarly.

Sam, myself and Yonathon have worked hard with this project in our own ways, and honestly it is quite relieving to have it all done and dusted. Now i’m just looking forward to the next project :3

Creative cards.

Group: Shakeel, Sam, Yonathon

[patriciadanielletan]

Studio I: CARDS FOR PLAY - Reflective Statement (150 words)

For our first studio project, Karen, Thomas and I worked collaboratively to develop a card game, "7 Days". I’m really pleased with its successful outcome, and I've learned valuable skills along the way that will be essential to refining my future design practice and working processes - although time management is one I still have to work on. Key to our project's success was the foundation of solid design pillars, continued development through iteration and also learning to interpret feedback from playtesting to meet our design goals. An efficient strategy was allocating roles that played to our individual strengths: Karen designed our game's aesthetic look & feel, Thomas devised its mechanics and I meshed these elements together into a cohesive package of prototype+presentation. I found this an insightful experience highlighting the essence of being a creative technologist - being the "glue" that binds people and practices into a high-performing collective.

[niishbct]

Reflective Statement

Honestly, I'm not really happy with our play project’s outcome. Our project has undergone major changes and our final project was version 3.0. But I'm extremely pleased with our teamwork and performance from the word start till the final presentation. We were very professional and followed the project brief unlike some groups. I was very frustrated with the fact that we got 4 different opinions throughout each week on our project. I'm not sure whether our presentation was good or bad, because we didn't get any feedbacks. All we were asked was a silly question about why one of our card’s border was a certain colour. It would have been good to know how we could have improved and what we did well. Overall, our game met what it was designed to do, and our play-tests showed us that our game was easily understood and met our design pillar.

[the-omnari-group]

Reflective Statement

It’s been a long one, and although the way I did it was a little less efficient than other groups, I think I made a solid effort for a one-man group. I got all the practical work done, but I didn’t really document that well.

The main thing I learned though, was that feedback and time management are more valuable than you’d think. It’s all fine and dandy to get a focused group of experts to comment, but it’s much better to get a wide sample of average-joes to weigh in. It’s also good to pace things out and not squeeze everything into the eleventh hour – something I had a habit of doing.

And finally, I learned that it’s good to have an idea of where you want to end up. So many people around me ended up dumbfounded when their ideas ended up completely different from the original idea.

[juliandv-creativetech]

Reflective Statement

The first studio 1 project has now come and gone. From watching the presentations and hearing the critiques, which followed, I have an even greater appreciation for the saying ‘less is more’.

I feel that our group worked extremely well together, as each member had different areas of strengths, but we all followed the same vision and contributed equally. I think that because clear communication between Lara, Aaron and I was established early on by being honest about how we felt about aspects of the ‘game’ that we avoided any potential conflicts.

Personally I much prefer minimalistic designs, such as those by designer Paul Rand rather than the likes of David Carson. Minimalism is key for visuals of a presentation and our design language fitted into this nicely. A common theme of circular designs was implemented throughout the presentation to join all the slides together and keep things running smoothly.

[onlyryan]

Reflective Statement

Throughout this design process we went through consistent iteration and were able to pinpoint problems and quickly follow up with mutual agreements. Iteration was absolutely key to finding out how to improve with combination of using people to play test. This meant we got feedback from people and thus were able to reflect and appropriately make changes. Despite we encountered problems, systematic methods to resolve these issues were undergone (repetition/iteration, trial and error, communication, teamwork)....

Overall our group did a sufficient job and our presentation went okay (slides were understandable), however in future it may be of value to slow down at the start and to not over complicate things (jump to conclusions) to avoid regressing back square one. Perhaps we need to take a step back and focus on basics and most quintessential points (design pillars) rather than getting carried away with sophistication of game mechanics (prioritize better).

[sm530]

Reflective Statement

Did our presentation today and got it over and done with. Overall I felt pleased with our performance even though our slides didn’t flow and work together. I can’t really object to the criticism given by the lectures and peers as they all made good points and through this we are able to learn from these mistakes and create something better for future projects (how will you learn if you don’t make mistakes right?). Looking back at our work, I noticed that our designs ate up a lot of our time, time which we could have used on other areas. From this I can say that we need to divide our time equally within all ranges of work. Also more organisation skills would make life easier. Devoting time to learning software’s needed in detail would come in very handy in the future and allow faster completion of stages.