Week 6: Viability Presentation

Our Viability Presentation this week has gone very poorly. We've recieved a red light, and feedback says that it feels like we've moved backwards from last week. Now it's time to figure out what went wrong and how to make sure we can catch up as quickly as possible.

What went wrong?

• A lack of effective communication amongst team members has lead to a disjointed vision of the game.
• We'd only met up twice this past week, rather than the regular three times.
• We've been struggling with design decisions
• There has been a slight lack of collaboration in the past week. It's proven tough to integrate all the artists' work.
• There were some unmanaged expectations amongst the group - some group members were expecting different outcomes this week.
• This is bad! The key to smooth teamwork is having everyone on the same page.
•  In summary, the entire team should have had a hand in creating the presentation.
• What actually happened was that I promised them I'd take care of the presentation, then presented something that didn't align with the group's vision or the task's requirements.

All we can do is look forward from here. Damage control:

• Assessing the situation was the first step to moving forward. Acknowledging what went wrong and why was integreal.
• Apologising to teammates was the next step. As team leader (and the one who wrote the presentation), this mistake is largely on my shoulders.
• Finally, we need to take steps to ensure such mistakes don't happen again.
• From now, all group members will be involved in the creation of presentations
• Presentations will be practiced amongst the team prior to the delivery date.

What have we learned from this? Coping strategies for future:

• Delegating a lot of the content aggregation to individual team members.
• Collating content in a team environment (either skype or a working bee)
• Fully discussing the framework / plan for the presentation before beginning work on it