L3 Development of Outcome

Overview

L3 Design Final

Back

L3 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 components
build components using appropriate tools, techniques, and conventions
test that components work 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
address relevant implications as you develop
document important decisions, changes, 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

Core Structure / Functionality

During the first sprint, you will build the basic working version of your outcome. This should include the core structure, key pages/components, navigation, and basic functionality needed for users to understand and interact with your outcome.

By the end of this sprint, your outcome does not need to be polished, but it should be developed enough to test whether the main structure and functionality work.

Minimum Marketable Product
MMP

Content / UX / Quality Improvements

During the second sprint, you will develop the outcome further by adding key content, assets, visual design details, and user experience improvements.

You should use testing and feedback from Sprint 1 to make informed changes. By the end of this sprint, your outcome should feel more complete and should be ready for more meaningful trialling with users, a client, stakeholder, or expert.

Minimum Awesome Product

MAP

Refinement, Extras & Polish & Extras

During the third sprint, you will focus on refining your outcome into a high-quality final version. This includes fixing issues, improving usability, polishing visual and technical details, and making sure the outcome is suitable for its purpose and end users.

You should use evidence from testing and trialling to justify the final improvements you make.

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 left 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 layout, colour, typography, buttons, icons, or images
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 for what a component may look like......

To test the component you pick one of these areas and you would explore the different options you have. You already have the first option which is based of your ideas but can it be better?

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

Once they have each component sorted they put them all together to test and then trial.

In terms of sprints for this example the first scoring system that is rough would be Sprint 1, basic functioning outcome, this video would be sprint 2 - refining and then they talk about the 3rd sprint - polishing.

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:

creating pages, scenes, screens, models, layouts, or sections
making assets, content, media, graphics, or interface elements
building interactive features, navigation, animations, or functionality
testing components to check they work as intended
trialling parts of the outcome with users, clients, stakeholders, or experts
fixing issues or improving the outcome based on feedback
preparing the final outcome for delivery/export/publishing

As you set up your board:

add your development tasks as individual cards
organise your cards into a sensible order
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, feedback, and fix/improve tasks
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 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

Add the screenshot to your document under:

Overall Project Development Tasks

FURTHER RESOURCES

CASE STUDIES

Web

Branding

Page updated

Report abuse