SHU Level 5 Integrated Project: Highlight Report

You might also like

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 6

SHU Level 5 Integrated Project

HIGHLIGHT REPORT V1.0 Project Stage 1: 28/01/13 to 08/04/13 Group: Stillwater

Emily Burcham: B1032563

Document History
Document Owner Document Location Emily Burcham This document is only valid on the day it was printed and the electronic version is located at: http://emilyburcham.wordpress.com/ draft Date of next meeting: 09/04/13
meeting date Next meeting date Summary of changes Changes marked

Document Status Meeting History


meeting number

1 2 3 4 5

26/02/13 05/03/13 12/03/13 19/03/13 26/03/13

05/03/13 12/03/13 19/03/13 26/03/13 09/04/13

defined idea Added group to asana Timeline was modified Easter roles defined (unable to attend) checked that charlotte knew role over Easter

Colin Colin Colin Daren Colin

Approvals
Name

This document requires approvals to be signed off and filed in project files.
Responsibility Date of issue Meeting number

Colin Pons Daren Eagles Anna Mellor Meecham Distribution


Name

Client Client Project Manager

29/01/13 29/01/13 18/02/13

1,2,3,4,5 1,2,3,4,5 1,2,3,4,5

This document has been distributed as follows


Responsibility Date of issue Version

Colin Pons Daren Eagles Emily Burcham Anna Mellor Meecham

Client Client Project Manager Project Manager

29/01/13 29/01/13 18/02/13 18/02/13

1,2,3,4,5 1,2,3,4,5 1,2,3,4,5 1,2,3,4,5

2|Page

Purpose

The purpose of this Highlight Report is to provide the Project Board with a summary of the stage status at intervals defined by the Board. The Board will use the report to monitor stage and project progress. The Project Manager (who has produced this report) also uses the report to advise the Project Board of any potential problems or areas where the Board could help. The Highlight Report below goes beyond the minimum recommended PRINCE2 content for a Highlight Report. This is one of the least prescriptive project reports in that the Project Manager, together with the Board should decide what information they need to see regularly included.

Content

Quality Criteria

Accurate reflection of checkpoint information Accurate summary of Risk & Issue Logs Accurate summary of plan status Highlighting any potential problem areas

3|Page

3. Highlight Report
1. Project Information: They are creating a cinematic for a game, following the Crytek brief, where the user finds themselves at Stonehenge, which turns into a portal to different world. As they go through the portal they enter an underwater world run by a tribal community. When the king of the pyramid temples is killed by the evil queen in order for the locked up evil king to rule, the good queen and the community must kill the evil king who is trapped in one of the pyramid temples before the evil queen releases him. Project Status: Over the Easter break they are finishing building models and are currently texturing these models ready to be placed in the Cryengine

2.

Budget
Planned hours Completion Date Expected Variance Planned (%of project complete)

Project
Delivered % Variance +/-

252 29/04/13

247

-5

70%

60%

-10

The figures for the budget are a culmination of hours each task is estimated to take, with them taking slightly longer than expected. The figures for the project are a percentage of time, showing what the group is expected to have completed and how much they have completed, with them being slightly behind on what they expected. 3. Products to be Completed during this period
Key deliverables Planned Date Achieved Date Variance Explanation

Initial ideas and concept art Models and structure of environments Texturing of models and environments

26/02/13 19/03/13

26/02/13 27/03/13

n/a 7 days

Models took slightly longer as there was more to do than planned -

27/03/13

4|Page

Composition of level and models Animation of characters and environments Filming of cinematic Finalizing product an presentation 4.

01/04/13 08/04/13 18/04/13 29/04/13

Change Control Impact Budget (days) 7 Schedule Time was taken out of texturing the models to compensate

Change More time added to model making

5.

Issues and Opportunities: Overall the groups workflow is very consistent and they communicate well to meet deadlines. There were some issues with the concept art being slightly late and with software crashing, losing work. However these are issues that the group has overcome by cooperating with each other. The group also wasnt very confident on how to texture correctly and on how to use the Cryengine. However this was resolved by talking to their tutor David who set up some tutorials on texturing and on using the Cryengine.

6.

Major Risks: There was a slight risk when one of the group members went abroad and missed the last meeting before Easter. This meant she also lost a bit of time to complete work; however she kept in contact and through talking to the group she has managed to catch up with this work over Easter.

7.

Outlook and Next Period: The next step for our group is to finish texturing their models and to composition and animate their cinematic ready for handover.

5|Page

Work Based Structure:


WBS No Detail Delivery Deadline Delivered By: Notes Approved

1 2 3 4 5 6 7

Initial ideas Research presentation Concept drawing Asset modelling Level design Character and plant designs Environment design

20/02/13 26/02/13 19/03/13 19/03/13 19/03/13 19/03/13 09/04/13

Group Group Charlotte Mark Jamie Adam Jamie

Took a while longer as there was more to do than thought Concept design was late so creature design took longer May take longer depending on when the textured assets are ready -

Colin & Daren Colin & Daren Me & Anna Me & Anna Me & Anna Me & Anna Me & Anna Me & Anna Me & Anna Me & Anna

8 9 10

UV mapping Asset texturing Building texturing

09/04/13 09/04/13 09/04/13

Adam Mark Charlotte

6|Page

You might also like