Production Schedule

A production schedule is a pre production document which allows us to plan a product. Everyone has access to this document as it is used to see if targets and tasks meet milestones. Can factor in contingencies. Known as a workplan. Would be made by a production manager or the producer. Wouldnt show this to the client but would show the visulisation diagram.


Milestones-The date
Timeframe-How long you allocate for the task
Contingencies-Back up plan-tasks and time


Effective features:

1.Team roles identified 

2.Tasks needed to be completed towards the final product identified.

3.Individual deadlines/ milestones and launch date identified.

4.Contingencies taken into account for delays (feedback, permissions etc).

5.Adaptable

6.Resources taken into account

Ineffective features of a production schedule-weaknesses:

1. Doesn't include a start or end date-
2. If tasks are not clear about what needs to be done-example 
3. Need to factor in additional time based on feedback not meeting milestones. Factor in extra time in case feeedback isnt positive-
4. Realistic time frames 
5. Need other planning documents such as visulisation diagram and script.
6. Be clear about timeframes and resources-
7. Legal and Ethical issues arnt considered

For Garmz Scenario-Negatives:

1-Due to be launched at the end of may so timescales would need to work back from this.

3-client hasn't set milestones for site map.

7-Not mentioned but need to consider the different ethnic groups viewing the website and the organisations such as the W3C and the ASA who will need to check the content on the website is suitable for its viewers.

For Garmz Scenario-Positives:

1-Know who's doing what-Ian-programmer, Alexia-grahic designer, John-buisness manager

2-Site map, visualisation diagram 

3-Feedback-Focus group-face to face
4-Clear timeframe-end of may but adaptable as only needs to be ready for before summer.