Embedded Files
DEVELOPMENT
DEVELOPMENT
Your Project
Your Project
Now you have to take what you have designed and the skills you have learnt and make your outcome. Make sure you read all the instructions carefully and know exactly what you intend to make before starting this assessment. Your teacher is only allowed to give you very basic feedback now and is not allowed to help you. This is a test to see if you can work independently and put all your knowledge into practice to make a cool outcome.
You will document your process in your working log and will need to handed in for assessment.
The Development Process
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.
Agile Project Management
Agile Project Management
Agile development is very common in developing Tech outcomes and involves deliberate planning and testing in short "sprints" of development.
Your teacher will set up milestone dates for you and your class where you will all test each other's outcomes and provide simple feedback to help you refine your plan for the next sprint.
Watch the video here for a quick overview and lesson on the tools and techniques you'll need to use.
Screen to Gif
Screen to Gif
Screen to Gif is an intuitive and powerful tool for collecting short snippets of development. This can be used to show cool things you have developed or options you were testing as they happen. You can put gifs straight into your google docs!
Project Management of the Development Process
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.
SPRINTS
SPRINTS
Minimum Viable Product
Minimum Viable Product
MVP
MVP
Basic Framework / Functionality
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
Minimum Marketable Product MMP
Refining - Adding Content / Aesthetics
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
Minimum Awesome Product
MAP
MAP
Making it Juicy - Extras & Polishing
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.
BACK UP YOUR WORK
BACK UP YOUR WORK
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.
Task #1: Project Management - Overview of your Development Stages
Task #1: Project Management - Overview of your Development Stages
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.
Task #2: Sprint 1 - MVP
Task #2: Sprint 1 - MVP
An MVP aims to test an idea with real users before committing a large budget to the product’s full development, learn what resonates with the target market, and attract early feedback to iterate and improve the product.
It can help minimize waste, focus on learning quickly, and test fundamental hypotheses for the business model. The sooner you determine whether your product appeals to customers, the less effort and expense you spend on a product unlikely to succeed.
S1 - Project Management
S1 - Project Management
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.
MVP Task Examples
MVP Task Examples
Aim: Create a functional MVP that allows the product to be tested and validated by early adopters.
Take the final design and create a MVP focusing on the the basic structure and layout.
Select a basic colour scheme and typography.
Create the simple logo (if needed).
Add the text
Have all the graphic elements on the page in a basic form
Demonstrate the core functionality
Conduct user testing session with the MVP.
Collect feedback on usability and functionality.
Reflect - where to
S1 - Develop & Test
S1 - 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
S1 - Trial & Feedback
S1 - Trial & Feedback
This is very important. It allows you to see whether your idea is meeting its purpose and end user requirements.
Task #3: Sprint 2 - MMP
Task #3: Sprint 2 - MMP
Aim
S2 - Project Management
S2 - Project Management
Task #4: Sprint 3 - MAP
Task #4: Sprint 3 - MAP
Aim
S3 - Project Management
S3 - Project Management
PRESENTING YOUR PROJECT
PRESENTING YOUR PROJECT
Final Presentation
Final Presentation
Add slides
CASE STUDIES
CASE STUDIES
Branding
Page updated
Report abuse