L2 Development of Outcome
Overview

L2 Design Final

Back

L2 Development S1

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

Development is the stage where you turn your final design into a working digital media outcome.

During development you will:

break your final design into smaller parts or components
build these parts using appropriate tools, techniques, and conventions
organise your files, assets, and versions so your work is easy to manage
test that each part works as intended
trial your outcome, or parts of your outcome, with others
use testing and feedback to improve the quality, functionality, usability, and fitness for purpose of your outcome
consider relevant implications as you develop, such as accessibility, usability, copyright, privacy, cultural appropriateness, or file management
document important decisions, changes, testing, feedback, and improvements as your outcome develops

The Development Process

At this stage, you will use project management to organise and manage the development of your outcome.

Development works best when the project is broken into smaller, manageable tasks. This helps you decide what needs to be built first, what can be improved later, and what evidence you need to collect as your outcome develops.

In this project, you will work through three development sprints. Each sprint will include planning, developing, testing, trialling where appropriate, reviewing, and improving your outcome.

By the end of each sprint, you should have a working version, component, or improvement that can be tested and used to guide your next steps.

Minimum Viable Product

MVP

Basic Framework / Functionality

During the first sprint you should build 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 finished yet.

Minimum Marketable Product MMP

Refining - Adding Content / Aesthetics

This may be broken down further into more than one sprint depending on the scope of your project. During these sprints it should be all about working up your product to make it as refined as possible. The core parts should be finished so that all the parts work well together.

Minimum Awesome Product

MAP

Making it Juicy - Extras & Polishing

During the last sprint it should be all about making your product as exciting, polished, and complete as possible. Making sure it looks the best it can and all the bells and whistles work.

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 be developing 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 stage.

Think about your final design, purpose, end-user requirements, and specifications. 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 refinement.

Once you have written the aim for each sprint, this overview will be 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 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.

These are some ideas of what a component might look like.

To test the component, you can choose one area and explore the different options you have. You have already chosen the first option, which is based on your ideas, but could it be better?

This video is a good example of what components are. There are three main components, and they are finding solutions for each one individually.

Once each component has been developed, they put them all together to test and trial the full outcome.

In terms of sprints for this example, the first scoring system that is roughly built in Sprint 1 is basic functioning. This video would fit into Sprint 2, where they refine and test the individual parts. Sprint 3 would focus on polishing, improving the user experience, and making the final outcome feel complete.

Example Development Tasks for 3D Models (for game assets or an online platform like Sketchfab)

Example Development Tasks for Animation

Example Development Tasks for Audio-Visual (e.g. video, podcast, music track)

Example Development Tasks for DFM Product

Example Development Tasks for Graphic Design (e.g. Branding Package, Book, Comic etc)

Example Development Tasks for Video Games

Example Development Tasks for Website (with Database)

Task 2 — Breaking My Outcome into Components and Tasks

You should already have a development board set up to help you manage the full development process across Sprint 1, Sprint 2, and Sprint 3.

Your board should be set up with these lists:

Backlog (To Do) — all the tasks/components you think you will need to complete
Ready / Next Up — the tasks you are planning to work on soon
Doing — the tasks you are currently working on
Testing / Review — tasks or components that need to be tested, trialled, checked, or reviewed
Done — tasks that have been completed

Start by adding all of your possible development tasks into the Backlog. These tasks should come from your final design, requirements, specifications, and the components needed to create your outcome.

Your cards might include tasks for:

setting up project files, folders, templates, scenes, pages, or workspaces
creating the main structure of your outcome, such as layouts, screens, scenes, models, sequences, or levels
developing original assets, such as images, graphics, models, animations, audio, video, interface elements, or written content
building advanced features, interactions, effects, movement, navigation, database functions, or technical systems
refining visual style, usability, accessibility, timing, performance, or technical quality
testing components to check they work as intended
trialling parts of the outcome with users, clients, stakeholders, teachers, or experts
fixing issues or improving the outcome based on testing, trialling, and feedback
preparing the final outcome for export, delivery, publishing, presentation, or handoff

As you set up your board:

add each development task as a separate card
keep each card small enough that it can be completed, tested, or reviewed
organise your cards into a sensible order, starting with the core structure before refinement and polish
use labels or card titles to show which sprint each task belongs to
add priority labels such as Must have, Should have, and Could have
include cards for testing, trialling, feedback, and fix/improve tasks
add brief notes, screenshots, or links to evidence where useful
move cards across the board as you work

You will keep updating this board throughout development. It should show how you are managing your time, tasks, testing, feedback, and improvements.

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, trialling, feedback, and improvement tasks
enough detail to show how your outcome will be developed, tested, and refined

Add the screenshot to your document under:

Overall Project Development Tasks

FURTHER RESOURCES

Page updated

Report abuse

L2 Development of OutcomeOverview