L3 Development of Outcome

~ Delivery & Evaluation ~

L3 Development S3

Back

L3 91909 External

LAUNCH

Delivery is about preparing your finished outcome for the environment where it will actually be used. This could mean publishing a website, exporting an animation for its viewing platform, preparing graphics for print, building a playable game, or preparing a digital model for manufacture.

An outcome that works in your development software may look or behave differently once delivered. Check it on the intended device, platform or physical setting, and consider the experience of the people using or viewing it. This helps you confirm that the finished result works reliably, presents well and meets its purpose.

This final stage brings together presenting your outcome, organising your files and evaluating how your decisions throughout development contributed to its quality.

Task 1 - FINAL OUTCOME

Present your completed outcome so someone can clearly understand what you have created, how it works and how it meets the needs of your intended users.

Include:

A brief introduction: explain what your outcome is, who it is for, and where and how it will be used.
Images of your working file: show the completed outcome within the software you used to develop it.
Images or video of the finished outcome in its intended environment: show what users would actually see, use or experience. Choose views that clearly demonstrate its main features and finish.
Access to the final outcome: provide the appropriate files, export or working link. Include a short demonstration if still images cannot show how it functions.

Check the delivered version. Make sure it opens, plays or runs correctly, required assets are included, and any links and permissions work. For a manufactured outcome, include the digital model as well as photographs of the finished object.

Task 2 - FILES

Provide a link to an organised Google Drive folder containing your project files. Make sure your teacher can open the folder and its contents using the required sharing settings.

Include:

Original working files from each sprint: retain versions that show how your outcome developed, using the native format of your software.
Content and source files: include the images, audio, video, fonts, code or other assets needed to open and work with your project, where licences allow.
Exports from each sprint: include the versions used for testing, feedback or review.
Final deliverable files: clearly identify the finished version intended for use.
Supporting records stored elsewhere: link to relevant planning, testing or feedback records so they can be accessed.

Use clear folder and file names that identify each file’s purpose and version. Check that your working files open with their linked assets, and include brief instructions if specialist software or setup is needed.

Task 3 - EVALUATION

Evaluate both the quality of your final outcome and the effectiveness of your development process.

Use specific examples to explain what you found out, how this influenced your decisions and what difference those decisions made. Support your judgements with evidence from your planning, component trials, testing, feedback and successive versions.

Use the headings below to organise your response. The questions are prompts to guide your discussion; you do not need a separate answer for every question or a repeat of your development log.

Your final outcome

Purpose and requirements: How successfully does your outcome meet your proposal and end-user requirements? Support your judgement with results and feedback. Explain any changes to your original direction and whether they helped you meet the underlying need.
Complex techniques: Which techniques contributed most to the finished outcome? Explain how you applied them and why they were appropriate for the purpose and users.
User experience: How did you apply relevant user experience principles, and what difference did they make? Consider aspects such as clarity, consistency, accessibility, feedback, navigation or how easily an audience can follow the content. Use examples relevant to your outcome.
Data integrity: How did you keep content and assets accurate, complete and usable throughout development and delivery? Explain the checks you used when editing, combining, transferring or exporting files.
Relevant implications: Which implications mattered for your project, and how did you address them through your decisions? Evaluate the effectiveness of your response, using examples such as accessibility, intellectual property, privacy, cultural considerations or sustainability.
Remaining limitations: What is still less successful, and what would you improve next? Explain the likely benefit for the user or the quality of the outcome.

Your development process

Planning and managing development: How did your project management approach help you organise components, prioritise tasks and respond to change? Explain how you managed feedback and, where relevant, collaboration.
Trialling alternatives: What different approaches, components or techniques did you trial? Explain what the comparisons revealed and why your selected approach was most suitable.
Testing and improvement: How did you use testing results to improve functionality and quality? Show how you checked whether your changes were effective.
Ongoing refinement: How did improvements across your design, development and testing build on one another? Include changes that improved the user experience or overall quality, alongside corrections to faults.
Efficient production: Which tools, techniques or working methods helped you produce the outcome efficiently? Explain how they reduced repeated work, supported consistent changes or helped you maintain quality.
Managing files and assets: How did your organisation, version control and backups support development and allow you to make changes confidently?

Bring it together — how your decisions shaped the result

Select a few significant decisions and bring together what you learned from planning, trialling components and testing. Include user feedback, research or expert advice where these informed the decision.

Explain how the information connected. For example, a component trial might reveal a better technical approach, user testing might show why the change matters, and your planning might help you make time to implement and retest it.

For each example, make clear:

What the different sources of information revealed.
How you considered them together, including any competing needs or constraints.
What you decided to change and why.
How you know the decision improved the finished outcome.

For example:

“Users found the opening of my animation difficult to follow. Comparing two editing approaches showed that holding key shots for longer improved understanding, but increased the running time. I reviewed my sprint plan and prioritised the opening sequence over an optional closing scene. This gave me time to adjust the pacing and test it again. Viewers could then explain the main event correctly, and the animation stayed within the intended duration.”

Finish with an overall judgement about the quality of your outcome and how effectively your process supported it. Explain the strongest evidence for that judgement and acknowledge any remaining limitations.

Page updated

Report abuse