L1 Audio Visual
~+~ Development Sprint 1 ~+~

Set up your project files before you continue developing your outcome.

Create a clear folder structure for your project. Depending on your outcome, this could include folders for:

• • working files

  • images, media, models, or assets

  • code, scripts, styles, or project files

  • exported or published versions

  • screenshots and evidence

  • testing and feedback

  • backup or old versions

Use clear file and folder names so you can tell what each file is and which version it belongs to.

You should also set up a backup system. This might be:

• Google Drive

• OneDrive

• GitHub

• school network drive

• external drive

• another folder for backup copies

Before making major changes, save a new version or make a backup copy so you can return to an earlier working version if something breaks.

In your document, add screenshots or notes showing how your project files, exports, evidence, and backups are organised.

Development evidence shows your progress, testing, and improvements.

You need to collect at least one clear piece of development evidence each week. This evidence should show what you developed, what you tested, what changed, and what still needs to be improved.

During Sprint 1, focus on creating the core structure and basic functionality of your outcome. This is the first working version, so it may still include placeholder content, rough assets, draft layouts, or unfinished visual details.

Your Sprint 1 development might include:

• setting up the main structure, layout, sequence, scene, model, or framework

• creating key components, pages, screens, scenes, sections, models, or assets

• adding placeholder or draft content

• building basic interaction, navigation, movement, timing, or functionality

• setting up technical elements such as canvas size, timeline, database structure, export settings, engine scenes, CAD components, or document setup

• testing individual components to check they work as expected

• testing how different components work together

• making changes based on what you discover during testing

Evidence could include:

• • screenshots of your working file, software, code, model, timeline, scene, layout, or project setup

  • before-and-after screenshots

  • short screen recordings or video captures

  • exported previews, renders, builds, prototypes, or test files

  • testing notes or checklists

  • screenshots of errors, issues, fixes, or improvements

  • brief comments explaining what you developed, tested, changed, and why

Develop the first working version of your outcome.

Focus on the core components that will get your outcome set up and functioning. It does not need to be polished yet, but it should be developed enough to test.

As you work, collect evidence each week.

For each piece of evidence, briefly explain:

• what you developed

• what you tested

• what worked

• what needed fixing or improving

• what you changed or will change next

During development, think about:

• People - who will use, view, interact with, or give feedback on your outcome?

• Components - which parts need to work on their own?

• Connections - how do the components work together?

• Context - where, how, and why will the outcome be used?

• Interactions - how will users move through, control, view, read, listen to, or experience the outcome?

Evidence

In your document, include at least one clear piece of development evidence per week.

• This could be an image, screenshot, screen capture, short video, exported preview, render, prototype, or testing note.

• Make sure your evidence is easy to understand. Add short comments or annotations explaining what the evidence shows and why it matters.

Don’t forget to move your Trello tasks as you go!