Taken in Semester 1, 2016. If you get put with a bad team you will be set up for failure. Don't waste your time doing well in the course, because you will be brought down by the rest of your team anyway and your effort will count for nothing. Talking to the course coordinator regarding team allocations is a waste of time. The staff protect each other, and this course allows slacker students in your team to benefit from your hard work, while you are negatively impacted by them. At the end of the day, if you are put into a team that is unmotivated, or is not of your calibre, it doesn't matter how much 'team maintenance' you do for the team, you will not succeed.
The software project was a joke, technically uninteresting, and does not teach you any of the skills expected of a software developer in the 'real world'. They emphasise that working in a team is a requirement in the 'real world' - but fail to enforce realistic actions and consequences that come with these 'real world' situations. I also dealt with some nepotism, where course coordinator favoured a student in my team due to their relationship outside of the course that affected the outcome of my grade.
I certainly wouldn't recommend this course unless it was absolutely necessary for your degree.
Also make sure you follow up with every grade that is questionable. We lost a significant portion of our marks for a section, that when I followed up with the course co-ordinator, basically accused us of not doing (before investigating further), when in reality they missed the section entirely during marking.
Semester 2 - 2015
Is lecture attendance necessary?
Is the textbook necessary?
No positive points
Your team allocation will determine your success with this course
If your team allocation is bad, you are set up for failure
I cannot overstate this enough... TP2 is difficult. It tests your ability to work with others, your time management, and technical knowledge to the limits. One of the hardest courses I've ever had to do. But on the other hand, its also what makes studying engineering so rewarding, because if you can pull it off, your final project will be something to be proud of. This is what your 3 years of studying basically leads up to.
Get in early and smash out basic functionality in the first half of semester. This course could basically be called 'Debugging: Circuits and Programming Hell', so you really don't want to spend the weeks leading up to the end of term just trying to get a power supply working!
This course is almost entirely self taught. You're given a brief (which can change slightly multiple times over semester), and as long as you meet the required functionality, you can basically do what you want. The reasons why I rate learning materials, activities and course content low, is due to the fact you and given the bare minimum of information to work with. But that's what the course is. It's not a course where you are taught, but one where your problem solving is put to the test.
I never had any difficulties in contact lecturers and tutors. The one downside I can think of when I took it, is that the marking criteria came out very late in the term.
Like Team Project I, this is a course where you only get out what you put in. While your success is largely dictated by the quality of your team, you'll be required to invest a lot of time, energy (and money!) into TP2 if you're looking for a good grade. That said, it's a very rewarding course if you manage to demonstrate a working product.
There are a number of seminars and 'client meetings' throughout the semester which are relatively easy marks, so make sure you prepare for them adequately. Also make sure you're in constant communication with your team, and aim for steady progress throughout the semester. This is a course where it's simply impossible to scramble together a good grade in Weeks 12 and 13.