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.

Throughout the development process you are going to work through sprints to create the outcome. Design errors can be found out early with this development process and corrected before they get implemented.

PROJECT MANAGEMENT OF THE DEVELOPMENT PROCESS

At this stage it is very important and helpful to project manage the development of your outcome.

By breaking down this project down into manageable task you should successfully produce what you set out to create, and will hopefully be a well thought out and high quality outcome.

As we work through an Agile process we break the outcome development into stages called sprints and under each sprint you will plan out the specific tasks that you need to complete.

In general you will have these areas you are working through.

Minimum Viable Product

MVP

Basic Framework / Functionality

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%

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 as possible. Making sure it looks the best it can with all the bells and whistles.

TASK 1 - Overview of your Development Stages

“You’ve got to start with the customer experience and work back toward the technology - not the other way round.”

-- Steve Jobs --

It is helpful to understand what you are trying to achieve over the 12 weeks.

Think about what you want your outcome to look like and work backwards to plan what the aim of each sprint is.

Once you have written the aim and explained what that involves this will be left.

When you start on each sprint you will do some planning and break your aim into tasks. As you work through the sprints you may need to change your expectations but no need to change this overview.

THE DEVELOPMENT PROCESS

The development process allows us to build our outcome step by step and this means we can think about our solutions in a different way, as well as to fail quickly and cheaply, so that less time and money is invested in an idea that turns out to be a bad one.

Throughout development you will use iterative improvement to:

use appropriate tools, techniques and conventions for the purpose and end users
Apply appropriate data integrity and testing procedures
Use information from testing procedures to improve the quality and functionality of the outcome
considered relevant implications.

TESTING OF COMPONENTS

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.

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?

You repeat this with different components and put all the best tests together to trial your outcome. In each sprint you will be focusing on different aims/goals so the components you test might be different or some could be the same.

What is Data Integrity

Data integrity refers to the accuracy, consistency, reliability and trustworthiness of data throughout its lifecycle.

It can describe the state of your data e.g. valid or invalid

What Data Integrity could look like...

Checked content is accurate
Used reliable sources
Spell checked
Proofread
Security flaws
Technical Errors

Why you need to Back up!

There are many ways to do this. At the start you need to work out how you are going to back up and plan how often you are doing this.

SPRINT 1 - Minimum Viable Product

During this sprint you are working through getting the basic framework and functionality up and running.

PLANNING

Get into Trello 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.

DEVELOP & TEST

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

TRIAL & FEEDBACK

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...

SPRINT 2 - Minimum Marketable Product

PLANNING

Get into Trello and break this sprint down to easy manageable tasks.

DEVELOP & TEST

Refine and Enhance Features:

Improve and expand on the core features based on feedback from the MVP.
Add additional functionalities that provide value to users.

User Experience and Interface Improvements:

Enhance the UI/UX design to make the product more attractive and user-friendly.
Implement more detailed and polished design elements.

Performance Optimisation:

Optimise the code to improve the product’s performance and responsiveness.
Ensure the product works smoothly across different devices and platforms.

Advanced Testing:

Conduct more thorough testing, including usability testing, performance testing, and compatibility testing.
Fix bugs and improve overall product stability.

TRIAL & FEEDBACK

FINAL OUTCOME & EVALUATION

By the end you should have a well thought out outcome, that works as expected (functional) and looks good (aesthetics).

TO EVALUATE

Did your final outcome meet your proposal / brief?

What tools, techniques and conventions you have used?
What you have done to ensure your outcome has good data integrity?
What did you/others trial / test?
What you improved from your trialing and testing?
What relevant implications were important to your project and how have you addressed these?
How were you informed by research or previous experiences? etc

FURTHER RESOURCES

Evidence

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, images, written info to show this evidence.

We do not need every single detail - just key points and a quick summary.

CASE STUDIES

Web

Branding

Page updated

Report abuse