L3 Development of Outcome Overview

L2 Design Final

He kai kei aku ringa

There is food at the end of my hands

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