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.
“You’ve got to start with the customer experience and work back toward the technology - not the other way round.”
-- Steve Jobs --
Prototype development is part of the software development life cycle. The main advantage of a prototype is that it simulates the real product and helps to attract users since they can look and feel the final product ensuring that they will be interested in your project. Design errors can be found out early with prototype development and corrected before they get implemented.
PROJECT MANAGEMENT
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.
To create this check out the information on our Project Management Page
SPRINTS
As we work through an Agile process we break the prototype 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.
Basic Framework
Basic Framework
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%
Refining
Refining
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.
Making it Juicy
Making it Juicy
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.
THE DEVELOPMENT PROCESS
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.
WHAT IS A PROTOTYPE?
Prototypes are built so that designers can think about their 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.
“They slow us down to speed us up. By taking the time to prototype our ideas, we avoid costly mistakes such as becoming too complex too early and sticking with a weak idea for too long.”
-- Tim Brown --
PROTOTYPE & TESTING PROCESS
You will need to pay attention to these four key components of prototyping and testing:
People – including those whom you are testing and the observers
Objects – static and interactive, including other objects the people and/or prototype interact/s with
Location – places and environments
Interactions – digital or physical, between people, objects and the location
https://uxdesign.cc/importance-of-prototyping-in-designing-7287c7035a0d?gi=6721821e4d3b
HOW DOES A PROTOTYPE HELP?
You should create as many prototypes as you need before the final product. A prototype allows you to:
Understand the scope for Project Management
Evaluate technical feasibility
Enhance the quality of your outcome
Present your idea to the end user more clearly
Risk reduction
Reduce costs
Simulate the real product + Quick and easy to create
Receive focused feedback
WHY YOU SHOULD PROTOTYPE?
Gives the end user a complete idea of how the outcome will look in the final result.
Allows you to streamline the design development process, focusing on important elements.
Allows you to identify unnecessary elements that are best abandoned.
Reduce your workload of developing the final project outcome.
TRIALING 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.
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 trial 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 trials together to test your outcome. In each sprint you will be focusing on different aims/goals so the components you trial 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.
Testing your Idea
This is very important. It allows you to see whether your idea is meeting its purpose and end user requirements.
Examples of Testing 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...
At this point you are going to repeat the above as many times as you need based on how many sprints you have.
THEN......
FINAL OUTCOME AND HOW TO EVALUATE
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
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
CASE STUDIES
Web
Branding
Page updated
Report abuse