The production schedule is used to plan the timescale that each part of the the project will need completing withing and how long they will take. Is used to make sure that deadlines are met or a milestone date (the date something needs to be completed by). Allows us to manage our time and see how long should be spent on different tasks or activities. Organising tasks and personalle.
Planning Document used to organise and set timeframes (hrs/mins/weeks) and milestones ~(actual date) for planning taskes products and team members.
Effective features of a production schedule.
Tasks listed in order so team knows what needs to be completed in chronological order
Prioritises order of tasks and time frames for eachtask
Can be viewed at all stages of production so can see if everyone is on task and can be refered back to
Identified team roles so who has to do each task
Adaptable as it is a working document so can be edited and manipulate
Plan for contingancies and backup plans
Plan for resources like hardware, software or equipment
Indervidual deadlines or milestones and launch date is identifiable
Time factored in for permisions or contracts from the client like a release and consent form (applicable to every scenario)
Doesnt have equipment
Doesnt have dates like a start date
All tasks are not included or clear about what needs to be done
Need to factor in additional time based on feedback, not meeting milestones
Need to be realistic about timeframes for activities and tasks, which task will take the longest amount of time
Other planning documents are needed to evidence the tasks like a visualisation diagram, storyboard, script
Wouldnt be shown to client, design matherials or planning materials would be shown
Timeframes need to be clear, so that if other parts of production are done then there would be delays
Resources need to be clear, hardware, software, models, personnel
No mention of ethical, legal issues that need to be addressed. Conciderations not taken into account, appropriate agencies to be contacted or forms completed like release and concent forms from models, intellectial property
- Sometimes can be called a Workplan
- Can look similar to a gantt chart
- Would be created by producer or production manager
- Important for team work as each task reflects and has an effect on the next task, the one after it
Garmz scenario:
Tasks listed in order so team knows what needs to be completed in chronological order- Alexia design vidualisation diagram, Ian create sitemap
Prioritises order of tasks and time frames for eachtask - Ian coding in features like the images of models, layout and navigation of the webpage takes longer than Alexia creating the visualisation diagram
Can be viewed at all stages of production so can see if everyone is on task and can be refered back to- If Alexia forgets what she needs to do next she can refer back to it
Identified team roles so who has to do each task - Alexia is a graphic designer so creates visualisation diagrams, Ian is coder so writes code language and creates sitemap
Adaptable as it is a working document so can be edited and manipulated - If Alexia creates a visualisation diagram and Garmz doesnt like it there needs to be adaptablity for the diagram to be changed so a change in timescales and deadlines
Plan for contingancies and backup plans - have backup models if the one being used is ill, use a different software to code if the one that is going to be used stops working
Plan for resources - camera & models for images, software like javascript or html5
Indervidual deadlines or milestones and launch date is identifiable - would have milestones for creating visualisation diagram for Alexia and then a different milestone for imagery
Time factored in for permisions or contracts - models sign contracts as need consent for imagery of them or location permisions for taking images
All tasks are not included or clear about what needs to be done - If John missed anything off of the production schedule such as the creation of a sitemap thne it would make it hard for Alexia and Ian to know what to do as it is one less planning document
Need to factor in additional time based on feedback, not meeting milestones - need to make sure that there is time left for Alexia to reflect on feedback and change the designs before the end of may when the release date is.
Need to be realistic about timeframes for activities and tasks, which task will take the longest amount of time -
Other planning documents are needed to evidence the tasks like a visualisation diagram, storyboard, script - Alexia to create a visualisation diagram of the different pages of the webiste and app, Ian make sitemap to plan the naviagtion
Wouldnt be shown to client, design matherials or planning materials would be shown
Timeframes need to be clear, so that if other parts of production are done then there would be delays
Resources need to be clear, hardware, software, models, personnel -
No mention of ethical, legal issues that need to be addressed. Conciderations not taken into account, appropriate agencies to be contacted - forms completed like release and concent forms from models so that their images can be used on the websites
A production schedule is a way of organising a project by setting
timescales and milestones that each specific task need to be completed within.
This allows for more effective planning and management of deadlines.