Another challenge passed, another step forward for our team.  I think we’re actually doing really well for ourselves, even if it took a good chunk of time for us to fully pass this challenge.  During the time it took us to pass this, we’ve made a really solid gameplan in order to be able to present during the Senior Show. In addition to this, we took the time to create and test 3 different prototypes in order to decide what game we would be pursuing for the rest of the semester.  These three prototypes were two digital prototypes and one physical prototype. We brought all three of the games to QA and got plenty of feedback on each concept before coming to a decision. In addition to this, we also weighed the pros, cons, and the general risks of each concept against each other.  

For this first reflection, I wanted to focus heavily on the topic of group-based and individual decisions.  For this first few sprints and the general first challenge as a whole, I actually think our team has handled it fairly well.  The first thing I want to discuss was how we divided up the general task work among our group members. Given our interesting team composition of 2 Designers, 1 Producer, and 1 Artist, we’re missing a pretty important role which would be a Programmer. 

Hey everyone, your friendly neighborhood Game Dev here. I had a blog post not too long ago that covered a similar topic but I wanted to delve more into how I’ve developed as a designer rather than just my leadership skills which the other blog post covered.

Stitches was a video game made during the summer of 2019 spanning a 3 month development period.  Through many ups and downs, the team managed to turn out a solid demo that displayed the overall gameplay loop and the general visual style.  While we are proud of the work we did as a whole, the actual process for developing Stitches was a very rocky one for quite some time.

It’s been a really long journey, but we’re finally at the end of development.

Stitches as an overall project has been an incredible learning experience for me. As the Product Owner, I’ve had to really adapt and adjust my general workflow in order to take on all of the new responsibilities that come with the role.