This weeks lecture covered how to plan projects and how to do good discovery/research. At the very start of the project it was stated that the only way to avoid total chaos is to plan a project. This is something I have practised in the past, more partially in college when studying animation which from this lecture I will defiantly set up a weekly planner for my team which I will talk more about later.
Something I found quite interesting was to know your team and what are everyone's functions. I think this is a very important thing for the team to discuss to understand what peoples strong points are and what possible ‘weak points’ people may have. This would be important to understand for assigning roles etc.
Scope and constraints was also mentioned which was another very good point to think about for this project. This is to identify how much time we have in the project, what tech is available and whats in or out. This got me thinking to understand what should be prioritized and what needs to be set to the side for things which may not be fully relevant to the brief, but if theirs time we could work on them. As well as this ‘scope creep’ was mentioned which is how a projects requirements can increase overtime, for example adding unnecessary elements which can take up time from the requirements of the project itself.
Frameworks was a new term for me which are structured methodologies and tool sets that guide the design process, similar to a road map.
The first example of this was a ‘Design Council Double Diamond’ which includes four main stages with the first two being ‘discover’ and ‘define’ and the second diamond including ‘develop’ and ‘deliver’.