The project I got was pretty interesting and a good chance to learn a lot I probably wouldn't have learnt from a normal unit. However, the unit structure is stupid. A good chunk of time is spent just writing reports and the marking rubrics are perhaps the vaguest documents I've ever seen in my life (most of them just say "wow" for the maximum marks section, I still have no idea what to make of this). 20% of the grade comes from a timesheet for the hours you've worked exclusively on the project, calculated as (hours_worked / 100) * 20. These hours don't include time spent watching lectures, writing reports, or informal group meetings, so to get full marks you'd have to spend >120 hours on this unit (or just lie, I guess). I luckily got a good group which made the unit enjoyable overall, but if you get a bad group then I could imagine this being the worst unit in the entire CS degree.

It's ok. The amount of enjoyment you'll get out of this unit is highly dependent on the team you're assigned. If you have a good team this unit is a blast. If you get a bad team, it will be the worst unit you'll do in your degree. Outside of that, there's a lot of reflections to write. Every three weeks you must reflect on how you and your team are performing. There's also a massive reflection based on all the lectures due mid sem. I personally didn't enjoy the lectures very much but a few of them are good. The most enjoyable part about the unit for me was developing an application for the client, you work on it practically all semester with your team.

Good class. Lots of projects from industry and academe to choose from. Having a mentor is also quite useful in acquiring information from those with experience. A bit frustrating is the constant need to create reports which takes away some time in working on the actual projects