You are going to follow an agile process to develop your outcome. We will have two "sprints" where your product will get made, tested and then you will get feedback.
Your first feedback session will be end of week 3 or early week 4 during term 4.
After 4 weeks work your product shouldn't be finished but your users should be able to test it and try it out. It should be functional even if not all the features are implemented yet. This could be a paper prototype, a first level of a game, or a first edit of a video.
Managing your project is really important to make sure what you set out to achieve is do able and that you don't leave it to the last minute
In order to plan our project we are going to use Trello an online project planning tool.
Go to trello.com and click "Get Trello for Free" then Sign up with your Google Account
Create a new Workspace, It does not matter what it is called and then Create a new Board from the bar at the top of the page. Give it a name and hit Create
Create 5 columns:
Extra Cool Stuff
Sprint 1 - Minimum Viable Product
Sprint 2 - Minumum Awesome Product
Doing
Done
You can also add your teammates if you have them to the same board and assign tasks to them.
You can then add cards for each of your tasks. Make sure that each of the tasks are small enough that you could possibly complete them in a lesson.
Sprint 1 - MVP
Term 3 week 10, Term 4 week 1 & 2: Monday 23rd September to Friday 25th October
Testing, Trialling and Feedback of MVP
MVP Ready - Week 3: Monday 28th October to Friday 1st November
Sprint 2 - MAP
Term 4, week 4, 5, 6: Monday 4th to Friday 22nd November
Outcome Completed
Term 4, week 7: Monday 25th to Friday 29th November
Outcome exported in correct format (and physically made if needed)
Outcome in the expected environment if digital i.e. uploaded to itch.io
Presentation Slides completed
Print Posters & Assemble
Tech Fair Presentation
Term 4, week 8: Monday 2nd to 5th December
Finishing touches to boards
Checking all links / QR codes work
Set up your display on Thursday 5th December ready for 3pm Start
Now get developing! Your aim is to complete your tasks for sprint 1 so that you can test and receive feedback for your MVP
Remember to check in and update your Trello along the way!
As you work on and complete tasks you should move the task to the appropriate section.
It can also be helpful to colour code tasks for specific members or related tasks.
At the end of each sprint/checkpoint you should archive your tasks.
At this point you need to get some feedback, especially if you have options but not quite sure which path to follow.
Giving and receiving feedback is tough. Feedback should be helpful, could improve the work, move things forward and bring about confidence.
Feedback needs to be constructive… and honest
Use THE FEEDBACK MATRIX - see slides
But what does it mean to be constructive?
Adjective
1. serving a useful purpose; tending to build up
Remember:
Feedback should be helpful
Help with choosing options / give direction
Might identify a gap or something that hasn't been considered
Make sure it feedback given is constructive and relevant
You are trying to get rid of the unintended consequences.
If feedback is unconstructive it can be ill-aimed, irrelevant, antagonistic.