After months of designing, developing, and testing, your digital outcome is now complete and ready for use!

The launch marks the delivery of a fully functional product that meets the needs of its intended end users. Through a careful evaluation process, we reflect on how project management, trialling, testing, and feedback shaped the outcome, ensuring it is both high-quality and fit for purpose. 

This evaluation highlights the successes, challenges, and improvements made throughout the project, demonstrating the impact of an iterative, user-focused development process.

By the end you should have a well thought out outcome, that works as expected (functional) and looks good (aesthetics). 

Evidence to show

• Final photos, images, videos of your outcome in it's intended environment

• Images of the final outcome in the software you developed it in

You need to provide access to your files (needed for moderation purposes. 

as part of your final outcome you should have a link to a google folder that has Permissions: Set to “Anyone with the link can view.” 

It needs to include the following

• Be Organised: Use clear and logical folder structure with appropriate folder names. All files should be named clearly to reflect their version and purpose so they can be easily identified.

• Contents included:

~ All versions of your outcome. These are the original progress files from each sprint e.g. photoshop file, premiere pro file, godot file, vsc file etc

~ Any content or source files used in the project

~ Exported files from each sprint e.g. mp4 file

~ The final deliverable files

This is a justification where you explain how and why your outcome addresses your proposal and unpacks the process you went through to develop your outcome

For Excellence you need to:

• synthesise information gained from the planning, testing and trialling of components  

• discuss how this information led to the development of a high-quality digital technologies outcome.

HOW TO STRUCTURE YOUR EVALUATION

~ INTRO ~ 

Part 1: What you have developed 

• State what the outcome is you designed and developed

• Explain its function / how it works

• Identify who the end users are

• Give context for where and how it will be used. 

~ BODY ~

Use specific evidence from your whole process to back up your points

Part 2: Judgement on whether you meet your proposal / requirements  

• Make a judgement on whether the outcome met the original proposal and requirements.

Did my outcome do what I originally set out to do?

• Give specific examples of what was achieved and what may not have been.

Which requirements were met? Which weren’t? Why?

Were there unexpected challenges that prevented some requirements from being achieved?

• Show how the final outcome aligns with the plan or purpose set out at the start.

How close is the final outcome to the design I proposed?

Part 3: Synthesised Information from planning, testing, and trialling - (Excellence)

This is what you did and what you learned from planning, testing, and trialling components.

• What planning tools or methods did you use (e.g., Kanban board using Trello, agile methodology to work through 3 sprints)?

• What were the key components or features you tested during development?

• What did you discover from testing each component (e.g., what worked, what didn’t)? *only give a couple of main examples

• How did client, stakeholder, expert, peer or end user feedback influence your next steps?

• What adjustments did you make to your materials, design, or functionality based on testing or feedback?

• Did you identify any patterns or repeated issues through testing?

• How did your results from one sprint affect what you did next?

• How did you combine insights from multiple sources (planning, testing, and feedback) to guide your decisions?

Part 4: How this Information (from part 3) Led to a High-Quality Outcome - (Excellence)

This focuses on the improvements, the final quality of the product/outcome and how planning, testing, and feedback contributed to quality.

• How did your project management help you stay on track or manage your time effectively to achieve what you did?

• How did iterative development (multiple sprints / testing etc) improve the final product?

• What specific improvements made your outcome higher quality or more functional?

• In what ways did the changes you made improve the look, function, or performance of your outcome?

• How did testing and feedback help make your outcome more user-friendly or reliable?

• How did learning from earlier mistakes lead to a better final result?

• What did you do differently after each sprint to improve quality?

• How did your decision-making and reflection help ensure your final outcome met user needs and expectations?

• If you were to continue developing it, what further improvements would make it even more high quality? 

~ CONCLUSION ~

A strong conclusion should summarise key points, reinforce your argument, and leave a final impression on the reader. 

Part 5: Conclusion

• Make a statement judging your process and the affect on your outcomes quality. 

• Reflect on the overall process.

• Summarise what was learned from planning, testing, and evaluating.