Embedded Files
He iti hau marangai e tū te pāhokahoka
Just like a rainbow after the storm, success follows failure.
We are often discouraged when we face challenges and we reach the point when we just want to give up.
Failures are ingredients to success. Making mistakes is essential to learn from them.
By working through the problem you'll eventually see the rainbow at the end.
What development involves
What development involves
Development is the stage where you turn your final design into a working digital outcome.
You will not make everything all at once. You will build your outcome in smaller parts, test each part, and improve it as you go.
During development you will:
break your final design into smaller tasks or parts
use the right tools and techniques to build your outcome
organise your files, assets, and versions clearly
test that each part works or looks the way it should
get feedback from others and use it to make improvements
fix problems and improve the quality of your outcome
take screenshots and write short notes to show what you have done, tested, changed, and improved
By the end of development, your outcome should be finished, tested, organised, and ready to present.
The Development Process
The Development Process
At this stage, you will use project management to organise the development of your outcome.
Development works best when the project is broken into smaller tasks. This helps you decide what to build first, what needs testing, and what can be improved later.
In this project, you will work through three development sprints. Each sprint will include planning, building, testing, getting feedback, improving, and documenting your progress.
By the end of each sprint, you should have a working part of your outcome, or an improvement, that can be tested and used to guide your next steps.
Minimum Viable Product
Minimum Viable Product
MVP
MVP
Basic working version / Build the main parts
Basic working version / Build the main parts
During the first sprint, you should focus on creating the basic structure of your outcome. This might be the first working version, the main layout, the key model parts, or the first section of your media outcome.
The goal is to have something working or visible that you can test and get feedback on.
Minimum Marketable Product MMP
Minimum Marketable Product MMP
Add and improve / Build more detail and improve quality
Add and improve / Build more detail and improve quality
During the second sprint, you should add more content, features, details, or sections to your outcome. You should also use testing and feedback from Sprint 1 to improve your work.
The goal is to make your outcome more complete and better match your final design.
Minimum Awesome Product
Minimum Awesome Product
MAP
MAP
Final Improvements and polish
Final Improvements and polish
During the third sprint, you should finish the remaining parts of your outcome and focus on quality. This includes fixing problems, improving details, checking that everything works or looks as intended, and preparing your final outcome for submission.
The goal is to have a finished outcome that is tested, organised, and ready to present.
Task 1 - Write the Overview of your Development Stages
Task 1 - Write the Overview of your Development Stages
Before you start developing your outcome, it is helpful to plan what you are trying to achieve across the full development phase.
You will develop your outcome over three sprints. Each sprint should have a clear aim so you know what you are focusing on and what needs to be completed by the end of that sprint.
Think about your final design, purpose, users, and requirements. Work backwards from what your final outcome needs to be, and decide what should be developed first, what can be improved later, and what will need final polishing.
Once you have written the aim for each sprint, this overview will stay in place. At the start of each sprint, you will break the aim down into more specific tasks and update your planning as your outcome develops.
For each sprint, write 1–2 sentences explaining:
what part of the outcome you will focus on
what you hope to have working or completed by the end
why this stage is important for your final outcome
Project Management & Components
A digital media outcome can feel too big to manage if you think about it as one whole project.
To make development easier, you need to break your outcome into smaller parts. These smaller parts are called components.
A component might be:
a page, screen, scene, or section
a visual element, such as a layout, colour, typography, button, icon, or image
a piece of content, such as text, video, audio, animation, or graphics
an interactive feature, such as navigation, links, menus, forms, filters, or transitions
a technical requirement, such as responsive layout, accessibility, file optimisation, testing, or publishing
A good project management task is small enough that you can clearly complete it, test it, and move it across your board.
Avoid broad tasks like “make website” or “finish game”. Instead, break your outcome into smaller cards that show what you are actually developing, testing, or improving.
Example Development Tasks for 3D Models (for game assets or an online platform like Sketchfab)
Example Development Tasks for 3D Models (for game assets or an online platform like Sketchfab)
Task 2 — Breaking My Outcome into Components and Tasks
Task 2 — Breaking My Outcome into Components and Tasks
You should already have a development board set up to help you manage your work across Sprint 1, Sprint 2, and Sprint 3.
Your board should be set up with these lists:
All Tasks — all the tasks or components you think you will need to complete
Ready / Next Up — the tasks you are planning to work on soon
Doing — the task you are currently working on
Testing / Review — tasks that need to be tested, checked, or reviewed
Done — tasks that have been completed
Start by adding all of your possible development tasks to All Tasks. These tasks should come from your final design and the components needed to create your outcome.
Your cards might include tasks for:
setting up project files and folders
creating the main structure of your outcome
making assets, models, pages, scenes, screens, or sections
adding details, features, movement, sound, images, text, or interactions
testing that parts of your outcome work or look as intended
getting feedback from another person
fixing problems or improving your outcome
preparing your final outcome for export, presentation, or submission
As you set up your board:
add each task as a separate card
keep each card small enough to complete, test, or review
organise tasks in a sensible order
use labels to show which sprint each task belongs to
add labels for testing, feedback, and fixing/improving where useful
add screenshots, notes, or links to show evidence of your progress
move cards across the board as you work
Your board should show how you are managing your time, tasks, testing, feedback, and improvements during development.
Task 3 - Project Management Evidence
Task 3 - Project Management Evidence
Take a screenshot (or screencast using screen to gif) of your project management board once you have added your development tasks.
Your screenshot should show:
the board lists/columns
your development task cards
sprint labels or card titles
priority labels, where useful
testing, feedback, and improvement tasks
enough detail to show how your outcome will be developed, tested, and refined
Add the screenshot (or gif) to your document under:
Overall Project Development Tasks
Now lets get making!
Page updated
Report abuse