Highlight Report (1)

7/28/2019 Highlight Report (1)

1/6

SHU Level 5Integrated Project

HIGHLIGHT REPORT

V1.0

Project Stage 1:

28/01/13 to 08/04/13

Group: Stillwater

Emily Burcham: B1032563


2/6

Document History

Document Owner Emily Burcham

Document Location This document is only valid on the day it was printed and theelectronic version is located at: http://emilyburcham.wordpress.com/

Document Status draft

Meeting History Date of next meeting: 09/04/13

meetingnumber

meeting date Nextmeeting date

Summary of changes Changesmarked

1 26/02/13 05/03/13 defined idea Colin

2 05/03/13 12/03/13 Added group to asana Colin

3 12/03/13 19/03/13 Timeline was modified Colin

4 19/03/13 26/03/13 Easter roles defined Daren

5 26/03/13 09/04/13 (unable to attend)checked that charlotteknew role over Easter

Colin

Approvals This document requires approvals to be signed off and filed inproject files.

Name Responsibility Date of issue Meetingnumber

Colin Pons Client 29/01/13 1,2,3,4,5

Daren Eagles Client 29/01/13 1,2,3,4,5

Anna MellorMeecham

ProjectManager

18/02/13 1,2,3,4,5

Distribution This document has been distributed as follows

Name Responsibility Date of issue

Version

Colin Pons Client 29/01/13 1,2,3,4,5Daren Eagles Client 29/01/13 1,2,3,4,5

Emily Burcham Project Manager 18/02/13 1,2,3,4,5

Anna MellorMeecham

Project Manager 18/02/13 1,2,3,4,5

2 | P a g e
http://emilyburcham.wordpress.com/http://emilyburcham.wordpress.com/


3/6

Purpose The purpose of this Highlight Report is to provide the ProjectBoard with a summary of the stage status at intervals defined bythe Board. The Board will use the report to monitor stage andproject progress. The Project Manager (who has produced thisreport) also uses the report to advise the Project Board of any

potential problems or areas where the Board could help.

Content The Highlight Report below goes beyond the minimumrecommended PRINCE2 content for a Highlight Report. This isone of the least prescriptive project reports in that the ProjectManager, together with the Board should decide whatinformation they need to see regularly included.

Quality Criteria

Accurate reflection of checkpoint information Accurate summary of Risk & Issue Logs Accurate summary of plan status

Highlighting any potential problem areas

3 | P a g e


4/6

3. Highlight Report

1. Project Information:They are creating a cinematic for a game, following the

Crytek brief, where the user finds themselves atStonehenge, which turns into a portal to different world. Asthey go through the portal they enter an underwater worldrun by a tribal community. When the king of the pyramidtemples is killed by the evil queen in order for the locked upevil king to rule, the good queen and the community mustkill the evil king who is trapped in one of the pyramidtemples before the evil queen releases him.

2. Project Status:Over the Easter break they are finishing building modelsand are currently texturing these models ready to be placedin the Cryengine

Budget Project

Planned Expected Variance

Planned(%ofprojectcomplete)

Delivered%

Variance+/-

hours 252 247 -5 70% 60% -10CompletionDate

29/04/13

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 apercentage of time, showing what the group is expected to have completed and howmuch they have completed, with them being slightly behind on what they expected.

3. Products to be Completed during this period

Keydeliverables

Planned Date Achieved Date Variance Explanation

Initial ideasand conceptart

26/02/13 26/02/13 n/a -

Models andstructure ofenvironments

19/03/13 27/03/13 7 days Models tookslightly longeras there wasmore to dothan planned

Texturing ofmodels andenvironments

27/03/13 - - -

4 | P a g e


5/6

Composition oflevel andmodels

01/04/13 - - -

Animation ofcharacters and

environments

08/04/13 - - -

Filming ofcinematic

18/04/13 - - -

Finalizingproduct anpresentation

29/04/13 - - -

4. Change Control

ChangeImpact

Budget (days) Schedule

More time added to model making 7 Time was taken outof texturing themodels tocompensate

5. Issues and Opportunities:Overall the groups workflow is very consistent and

they communicate well to meet deadlines. Therewere some issues with the concept art being slightlylate and with software crashing, losing work.However these are issues that the group hasovercome by cooperating with each other. The groupalso wasnt very confident on how to texture correctlyand on how to use the Cryengine. However this wasresolved by talking to their tutor David who set upsome tutorials on texturing and on using theCryengine.

6. Major Risks:There was a slight risk when one of the groupmembers went abroad and missed the last meetingbefore Easter. This meant she also lost a bit of timeto complete work; however she kept in contact andthrough talking to the group she has managed tocatch 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 theircinematic ready for handover.

5 | P a g e


6/6

Work Based Structure:

WBSNo

Detail DeliveryDeadline

DeliveredBy:

Notes Approved

1 Initial ideas 20/02/13 Group - Colin &

DarenResearch

2 presentation 26/02/13 Group - Colin &Daren

3 Concept drawing 19/03/13 Charlotte - Me &Anna

4 Asset modelling 19/03/13 Mark Took a while longer as there was more todo than thought

Me &Anna

5 Level design 19/03/13 Jamie - Me &Anna

6 Character and plantdesigns

19/03/13 Adam Concept design waslate so creaturedesign took longer

Me &Anna

7 Environment design 09/04/13 Jamie May take longer depending on whenthe textured assetsare ready

Me &Anna

8 UV mapping 09/04/13 Adam - Me &Anna

9 Asset texturing 09/04/13 Mark - Me &

Anna10 Building texturing 09/04/13 Charlotte - Me &Anna

6 | P a g e

Documents

Highlight Report (1)