Factors that lead to the failure of this team: - Too high complexity - Improper leadership - Expectations set too high - Lack of motivation Complexity: - Very high block count - Hard to navigate through code - Bugs - Lag - Many people couldn't understand the code itself Leadership: - Most team members weren't utilized - Members weren't clearly told what to do - Some members didn't have sufficient skills - Difficulty collaborating Expectations: - Too many things were expected to be finished at a time - Each task also took too much effort - The expectations of what the OS should contain were too high in general, considering this is just a Scratch OS Motivation: - All the listed points lead to the loss of motivation - People were busy with other parts of their lives - OS Wars became boring - Several people of the team were leaving - Blue OS VI ultimately died (Possible) solutions to these problems for future OS Wars: - Keep things as simple as possible (this is CRUCIAL!) - Only build upon something if time and ability permits - Be as clear and concise as possible with team members - Keep all members engaged (e.g. use a points/rewards-based system) - Prioritize only a few (about <4) tasks at a time and continue when they're finished - Communicate to team members frequently - Encourage effective time management - Follow good coding habits (comments, simplicity, organization, etc) Optional readings: https://en.wikipedia.org/wiki/KISS_principle http://suckless.org/philosophy/
