We thought this lesson was very successful as we had also completed our first mission.

The "large delivery" mission: It was very frustrating repeatedly getting it slightly wrong but we eventually came somewhat successful, being able to knock over the first half, but not the second. In the next lesson, we aim to reverse the robot and do the other side.

This is what I would call our most successful missions and transfer between mission yet, we allowed for 4 seconds to quickly set it up and move it again.

This is what I would call the least successful experiment, when completing our second mission, we got the placement slightly wrong and it tipped over after striking he flap at the wrong angle.

This attempt started with our usual first mission and we experimented with ways to go to the next mission, after speaking to peers, we discovered that the robot did not have to go exactly on the path, so we quickly changed our objective, opting for a more efficient and easier route.

We were able to successfully complete the first part of the next mission - it took a long time and over 17 attempts but we finally got there!

We toyed around with the coding and the timing - what was most hard was the the angles and finding out the most efficient way to turn

We then made some small adjustments to our previous mission, to make it easier to transition between that mission and our next.

We started brainstorming what we should do next, after looking at other teams and their strengths. We were then able to add "Transportation Journey" as the third and "Air Drop" as the fourth

Making the order so far:

1. M12 Large Delivery - Chicken Part

2. M14 Bridge

3. M04 Transportation Journey

4. M08 Air Drop

This order is fully apt for the process, using information that we gathered ourselves through testing, communicating with classmates and consulting videos available online.

We did more coding and went back and fourth, we ran into a problem between M14 and M04, there is a small hook-like object sticking out on the M14 Piece, more often then not causing the EV3 to spur off slightly in the wrong direction, causing all further commands to be off.

We overcame this by ensuring the EV3 would go by a slightly different angle, although we cannot be certain this will fix it, we do know that 9 times out of 10 this alteration will ensure the EV3 to continue going the right way.

It was hard finding a solution and toying around with it to make it as precise as possible, but we managed in the end.

All of this can be seen on the timelapse which is attached below.

We learnt new teamwork skills, were able to approach opportunities with coding in a new way, which we learnt through thinking outside the box and making many adjustments.

We faced many challenges from not being able to get the turn right, to struggling with assembling the vehicle and having difficulties with coding.

We overcame this mostly from a lot of trial and error and consulting YouTube videos and classmates for advice.

We worked well together and achieved a good final product.