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