During the first sprint you should finish the basic requirements of your project. The users should be able to give you feedback on how your project works and looks even if everything is not working 100%
You will need to show evidence of your process. You can do this a variety of ways:
A overview each week
After completing a task in your project management
Key moments
Use bullet points, screen captures, gifs, images, written info to show this evidence.
*** We do not need every single detail - just key points and a quick summary. ***
Get into Trello (or whatever planning tool you are using) and break this sprint down to easy manageable tasks. You have created a final design so think about what you now need to make on the software so that your outcome can become functional.
At the end of 4 weeks you should have something that can be trialled with end users and gives the basic idea of what your outcome is. Think about what the minimum features are and prioritise based on their importance and impact.
Below are some examples to help you get started.
What “basic” looks like:
Low-poly model blocked out
Basic shape and scale are accurate
Saved in correct format (e.g. .obj, .fbx)
Basic UV unwrap if needed
Core features into achievable steps:
Model base shape in chosen software
Check proportions and scale
Organise objects/components logically
Save/export in game-ready format
Prioritise:
Correct geometry and scale
Simple topology
No non-manifold or broken meshes
Testing checklist:
Model opens in 3D software with no errors
Scaled correctly for intended use
No duplicate/floating faces
Can be imported into another program/game engine
Base form matches reference images
What “basic” looks like:
Rough storyboard blocked out in scenes
Basic character/object movement
Placeholder audio or text
Keyframes and transitions blocked in
Core features into achievable steps:
Set up scenes/backgrounds
Design or import rough character/assets
Animate core movement (e.g. walking, talking)
Add simple transitions/cuts
Prioritise:
Story clarity
Key actions/movements
Scene timing and sequencing
Testing checklist:
Scenes follow intended order
Main characters/objects animate correctly
Movement/timing matches the storyboard
No broken transitions
Can export or preview rough animation
What “basic” looks like:
Timeline created and rough cut made
Placeholder footage/audio added
Key scenes/sounds aligned
Intro and outro structure in place
Core features into achievable steps:
Set up project timeline in editing software
Import raw audio/video clips
Trim and arrange in sequence
Add placeholders for transitions, effects, or titles
Balance basic audio levels
Prioritise:
Structure and pacing
Rough visuals/audio aligned to plan
Sound clarity (for voiceovers, music)
Testing checklist:
Project plays through without crashing
Audio is clear and synced
Intro, body, and outro are defined
No silent gaps or missing files
Exported rough cut plays back smoothly
Initial 2D/3D concept or prototype
Measurable digital sketch or model
Rough form and function understood
Basic materials and constraints chosen
Sketch design digitally (or in CAD)
Define key dimensions and measurements
Choose intended materials/processes
Test prototype scale or fit (paper, cardboard, simple print)
Save/export in manufacture-friendly format (e.g. DXF, STL)
Key dimensions and fit
Structural stability
Manufacturing constraints (cut lines, thickness, etc.)
Design opens in CAD/CAM software
All dimensions are clear and accurate
Model/prototype can be manufactured or cut
No overlapping paths or duplicate lines
Chosen materials/tools are compatible
What “basic” looks like:
Rough layout created
Placeholder text/images in place
Colour palette and typography chosen
Core features into achievable steps:
Define purpose and target audience
Create initial sketch or wireframe layout
Place key content blocks
Choose fonts and colours
Import sample content (title, headings, dummy text)
Prioritise:
Layout composition
Visual hierarchy
Consistent style guide
Testing checklist:
Text is legible at different sizes
Layout looks balanced (nothing overcrowded)
Main message is clear
Colours and fonts are consistent
Exportable file format set (e.g. PDF, PNG)
What “basic” looks like:
Playable scene/level with player movement
Placeholder assets and basic UI
Core game mechanic working (e.g. jump, collect, navigate)
Core features into achievable steps:
Set up game project in engine (e.g. GDevelop, Unity)
Add player character and camera
Program basic movement/collision
Add 1–2 interactable objects
Create placeholder UI (e.g. start/restart buttons)
Prioritise:
Core mechanic(s)
Player controls
Game loop (start-play-end)
Testing checklist:
Player can move and interact
Game scene loads without crashing
Restart or respawn works
Core mechanic behaves as expected
No “soft lock” areas (can’t move or progress)
What “basic” looks like:
Homepage and 1–2 content pages
Basic user input form
Database connection established
Data can be sent/received
Core features into achievable steps:
Set up site structure (HTML/CSS/JS)
Create form to capture user data
Connect to a database (e.g. Firebase, SQL)
Set up routes or page navigation
Display stored data
Prioritise:
Form > database connection
Navigation between pages
Basic layout (responsive if possible)
Testing checklist:
Pages load and navigate correctly
Data submitted goes to the database
Stored data displays on a page
Layout does not break on screen resize
No console or loading errors
Focus on creating all the elements / parts / components that will get your outcome up and functioning. You might have placeholder graphics at this point.
During development you need to also test:
Perform testing to ensure individual components work as expected.
Conduct integration testing to check how different components work together.
While you are developing think about:
People – the end users and also who you will use to trial and the end of this sprint
Objects – static and interactive, including other objects the people and/or prototype interact/s with
Location – where this will be used, the places and environments
Interactions – are these digital or physical, between people, objects and the location
This is very important. It allows you to see whether your idea is meeting its purpose and end user requirements.
Examples of Trialling Questions
(in a website development context), linked to relevant implications
Does this site adhere to legal requirements? (content and images meet copyright requirements)
Is the site accessible? (via multiple devices, alt tags)
Does the site function properly? (images display, image quality and resolution correct, all navigation links work)
Is the site readable (usability)? (proofing of spelling, grammar, appropriate font sizes and colour contrast)
Is the site aesthetically pleasing? (have design principles such as repetition, alignment, proximity, white space and typographical conventions been followed)
Does the site meet end user requirements? (what were they? have they been addressed?)
From the feedback I have received I will develop...