Phase Three, the development phase, is all about taking your design ideas and developing them to a high standard in the finished product (outcome).
Working through an Agile process, we break the outcome development into stages called SPRINTS. These are short 4 week development cycles where you try to complete a set amount of work.
The three sprints are:
Minimum Viable Product (MVP) - develop the basic elements and functionality. The MVP prioritizes getting a basic, functional product working quickly. It emphasises basic functionality over everything else. It is used to test basic functions and gather user feedback, to help you understand what users think of it.
Minimum Marketable Product (MMP) - develop all elements, improved aesthetics, content, and functionality. The MMP should allow users to test and see the components and functions in your outcome, even if they don't look perfect. Still, keep it small, keep it simple. Then really listen to what people have to say about it!
Minimum Awesome Product (MAP) - complete all elements, functionality, conventions, and aesthetics. This is the "best you can do" version, a finished version to share with the World.
Watch this great video to understand the differences:
Components (also called elements) are the fundamental components that artists, designers, engineers, and creators use to build visual works.
You've probably already thought about and researched some of these during your design stage.
Now it's time to plan how you are going to develop all of these components through your three sprints.
Here's your task:
Find the table in your workbook (part three)
Identify the components that make up your project.
Think about what you will need to do to develop these components
First decide what is most important to do in your first sprint (your Minimum Viable Product), to create the basic components and functionality.
Then think about what is important in the other two. By the third sprint this component should be complete.
Once you're happy add these to your Trello boards as individual cards.
It's SOOOOO important to remember though that your plan may change after you complete your MVP. That's the whole point of Sprints - your testing and trialling will discover things you might not have thought about.
I've created a few examples to help you understand this approach - see below.
There are 4 key UX principles we need to think about for development. These are the FUCA principles (functionality, usability, conventions, and aesthetics). I've added a little key to mine to show which are relevant for each component...
See the next page for more about the FUCA principles.
Using the right tools and techniques is a critical part of your project.
Digital tools are considered "programs, websites, applications, and other internet and computerized resources that facilitate, enhance and execute digital processes and overall digitization efforts". In other words they are what we use to create a digital outcome.
Digital techniques are the many different ways that we use those tools, in other words how we use the tools to create a digital outcome.
So for example:
The tool I will use:
Photoshop - which is good for single raster images- to give it the photo-realistic appearance
The techniques I will use:
Applying a metallic effect
Using layer masks
Adjusting colours
Using brushes to create a cloud effect
Applying filters
Modifying an image with blur, soften, and clone stamp
There are a huge range of tools and techniques that you could use so it's important to identify and use those that are right for your project.
It is also important that you use the right tools and techniques complexity for your NCEA Level - using Tools and Techniques is part of the standard that you are working towards.
You will find some examples of tools and techniques for the different types of projects in the NCEA Ako section.
Using efficient tools and techniques is a requirement for excellence. These are different from your choice of advanced or complex techniques as they are more linked to the process you used than the digital outcome you created.
Here's a few examples:
applying version control methods
using planned and systematic testing, not trial and error
using Google Forms to collate trialling information
using storyboards, run-sheets, flow-diagrams, etc. to efficiently manage production of the outcome
demonstrating efficient software techniques appropriate to the media
creating customised styles and master pages
I've also put a few more examples in the NCEA Ako section for your project domain.