L2 Electronics and Mechatronics

~ Development of Outcome ~

Electronics Overview

Learn Electronics Skills

Electronics Project Exploration

Electronics Project Brief

Electronics Design

Level 2 Home

Overview and Teachers Notes

Course Length: Approximately 12 weeks.

AS92005- Develop a digital technologies outcome.

This course is the assessment phase of the Print & Digital Media Course and will assess students against the AS92005 Achievement Standard.

Please ensure students have completed the Graphic Design Skills and Print & Media Design stages before continuing.

Software requirements:

Any Web Browser (eg Chrome, Edge, Firefox or Safari) for Trello

Inkscape: https://www.

Adobe Creative Cloud (there are high school licenses available for schools to purchase)

Suggested Timetable:

1 week planning and "before development"
3 x 2 week "sprints" of development with testing/feedback/replanning in between. Can be shortened.
1 week final reflection, showcase and document redraft.

Teachers! Be aware of the conditions of assessment. From the website:

"Student work which has received sustained or detailed feedback is not suitable for submission towards this Standard. Assessor involvement during the assessment is limited to providing general feedback on aspects of the work that the student may need to revisit."

“There are three responses to a piece of design – yes, no, and WOW! Wow is the one to aim for.”

- Milton Glaser

DEVELOPMENT

You will use project management to help you deliver and you'll need to test your outcome(s) along the way with your clients, stakeholders, end users or classmates.

Following a good process helps you get a good result.

Please ensure students have completed the Graphic Design Skills and Print & Media Design stages before continuing.

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

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

SPRINTS

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

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.

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

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

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.

Now that you have a plan, it's time to develop. You should get in a good routine. Every time you come in to class:

Check and Update Trello
Work on the current "Doing" task in Trello and, when done
Repeat from step 1

The sprints are short, so stay focussed. Good project management and wel written tasks will help you stay on track.

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

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

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

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

Agile Development is about change.

Things may have gone well and they may have gone poorly. But adapting to how things are going is crucial. If things went poorly, change the plan! It is OK to admit to being too ambitious or learning that Blender is really hard and you're going to have to scale back. It's also OK to admit that you might need to upscale your project so you donlt finish too early.

Documentation will help you prove how much work you are doing and how much you are learning and improving. Your teacher will need you to document your progress at this point and you will need to ask at least three people what they think of your work so far.

Listen to the feedback you get and take it in to account when you update your Trello board. Adding and Removing cards is allowed between sprints so make sure your project is on track.

Complete the Sprint#1 Review section of your Development Log now.

Task #4: Sprint 3 - MAP

Just like before, you'll need to test the outcome with others and get their feedback.

It's OK to change things, add tasks or remove items that you don't think you'll need.

Complete the Sprint #2 Review section of your Development Log now.

<------ FINAL OUTCOME & REFLECTION ------>

Congratulations!

You have hopefully made something that you can be proud of. The final review and showcase documentation is required as the last part of your assessment. Below are a few ideas for presentation. Why not upload it to Sketchfab? Or Create a youtube video of your work as if it's on a turntable? Or how about a really high quality render to go in your Development Log?

Complete the "Project Finished" section of your development log now.

Agile Project Management

Agile development is very common in software engineering and involves deliberate planning and testing in short "sprints" of development. You can see from the image above.

Each sprint has a deliberate "Phase" of development and you test, get feedback, review and replan at the end of each so you can keep improving the outcome.

The easiest method to keep track of you "tasks" is using Trello and Kanban. See the video to the right. This method lets you visually see what you are working on, what you've already completed and whats next. Each task should be something measurable that you can complete in one or two lessons like "add materials to barrel". Make sure your tasks are specific and small otherwise they will never move to the done list!

From what you learned above, try to add as many tasks to the "ToDo" list in your Trello board. Make sure they are specific and measurable. Remember making a 3d model involves lots of steps like creating the basic shape, refining the shape, adding materials, rendering, lighting. And tasks can include project management tasks like getting feedback, updating your development log and even updating your Trello board!

Once you have added as many tasks as you can to your Trello board, get it checked by your teacher and make sure it's something you can follow.

Task #1: Fill out Initial Trello Board Plan in your Development Log now.

Page updated

Google Sites

Report abuse