Sherriff is great professor. Whether or not you will enjoy the material really depends on if you are interested in the project management/logistics side of software development, but Sherriff is such an entertaining, engaging professor nonetheless. The quizzes have a full retake at the end, so it's no pressure. Studying at least the day before definitely helps, though. For the project, you're really only given a general theme and the specific project you work on is up to your group. My advice is to not add a lot of complexity to your project, since there's actually less time to write code than you think (considering requirements gathering takes up time in the beginning, and beta testing is well before finals). If you have time, you can always add more features at the end, and I think having a really nice frontend (in addition to having a fully working app) goes a long way.

Sherriff is one of the best professors I've had as a CS student. I'm genuinely excited to go to class everyday (despite it being a 9:30AM) and I always have a laugh in lecture. He knows how to impart knowledge while engaging his students. I would say that he is also a fair person. There are several Guided Practices (i.e. in-class activities) throughout the semester, and you are given one virtual make-up for whatever reason. There are also a couple team evaluations, where you can bring up any concerns and this gives him and the TAs a better sense of how to evaluate your team project.

Like most people have already said, the trajectory of your team project is heavily dependent on the quality of your teammates. I personally had a great vibe going on with most of my group-mates and we managed to put out a decent beta version (currently still in the thicket of the semester). We definitely had a major road bump with one person and that severely hindered our progress, but our TA said that the project will be evaluated based on our circumstances, which I think is chill. On a weekly basis, I definitely spend a lot of time working on the project, each sprint asks for very little, but we're told that they will hold us to a fairly decent standard (meaning working app, good usability, not totally ugly). Working on your app little by little every week and doing a little more than the sprint asks for is for sure the move.

Quizzes so far have seemed fair (I've only taken 2/3 so far). If you go to class, pay attention (not hard b/c it is entertaining), and take a day or two to review before the quiz, you will be more than set. Sherriff also offers an online coursepack as supplementary material and this includes lecture recordings from COVID times (super helpful).

TLDR: This class demands a decent amount of work, but it won't seem like it if you enjoy this kind of project. Sherriff is goated.

- COURSE -
To a lot of students, CS 3240 ends up being their favorite CS class taken at the university. However, that really depends on how passionate you are about CS going into the course. The class is essentially is a guided experience of what it's like to work on a scrum team, designing a piece of software over the course of a semester. It's almost like an internship you do for a grade instead of money or job experience. In my experience, I didn't hate the course, but I wasn't really a huge fan of it either. I think it's almost a bit too free-reign, and the semester-long project's milestones only cover a certain amount of what you're doing, which you're expecting to go above and beyond for. There are TAs assigned to each group, but the extent of how helpful they are really depends on the TA. Basically everything in this class is just going to depend on how good the people surrounding you are. There are 3 exams, which aren't too hard but whose grading can be really confusing. They unfortunately tend to revolve a lot around rote memorization, which I really disliked.

- INSTRUCTOR -
Sherriff is honestly a great professor. He's funny, his lectures are entertaining, and he's very knowledgeable about the subject field. He also tends to end lectures early, so there's no pointless downtime meant to use up all of the 75-minute lecture.

If you're genuinely interested in pursuing a career in CS, this class is basically essential. It's going to let you get a taste of the experience of working on a software development team. However, the group you get assigned to will basically dictate your entire experience in this class.
#tCFS24

Sherriff is super engaging during lecture and jokes around often. As a predecessor to CS 3140 (SDE), it was way easier and less technically intensive. The quizzes/tests are more so centered around software engineering tools and the field itself rather than the nitty gritty technicalities of programming. The only thing that is more difficult about this class is the project you work on with a randomly assigned group where you learn new tools without much guidance. Depending on your group, the project can be harder for you than another one of your classmates which is unfortunate, but for the most part, groups seem to usually work out. #tCFS24

In this class, we worked with a random group of 5 the whole semester to build a web app. I felt like the work was slow paced, and that I probably would've learned more if the groups were smaller, but the workload was really manageable. I loved Professor Sherriff, and he made the material much more interesting. You don't need to do any pre-readings for lectures, so outside work is just coding the project and team meetings. #tCFS24

I loved this class. It was really refreshing taking a chill class thats just about concepts and how to work well on a SWE team. This was super refreshing and made me realize why I enjoyed CS and my perception of that was probably dismantled due to DSA and CSO...but theres just one major project that you develop throughout the semester and its hard to not do well In the class #tCFS24

This class is utterly useless. Professor Sheriff tries to make it interesting, but the subject matter really is quite dry. The project is what made me hate this class the most; it is drawn out over the entire semester with 6 sprint checks and these half-baked nonsense reports made to fit each of your team member's contrived roles on the team. The grading is overly harsh and this class takes itself WAY too seriously. The "positive reinforcement" grading was likely something cooked up in a sterile educational research setting and if anything it stresses you out more since this is the only CS class I know of that cuts off A's at a 95%. Don't take this class if you're a BACS major.

I think a lot of your experience with this class really depends on your group for the project. The semester long project makes up the majority of your grade, so it's important to address any issues with your group at the beginning of the semester. The Django tutorial in the first month of the semester is not hard at all, you just have to start more than 2 days before it's due. As long as your group works together well and turns in something that is functional, you will probably get an A in this class. The quizzes aren't hard at all, and the retake at the end is helpful for making up missed points. Overall, I think I actually learned a lot about scrum development from this class and would recommend to people looking to work in SWE. #tCFF23

I had to take this class for engineering but I would definitely recommend it to any CS BAs. It's not hard at all and the project is actually really enjoyable. It's great to look back on what you have accomplished over the semester. The exams are also not hard as long as you pay attention to his lectures. #tCFF23

Overall, a valuable experience and the course is well structured. Grading is on an XP scale where points on quizzes, sprint checks, etc. add up to your total grade (950/1000 is an A). I'd say it's pretty normal to get an A, as long as you make timely progress on your application and get decent grades on the quizzes (the content isn't difficult--there were three quizzes that tested your knowledge of lecture content and an opportunity to retake at the end of the semester). Prof. Sherriff is very transparent about the schedule and anything related to grading as well. However, your group, which is randomly assigned, makes or breaks your experience for sure. Plenty of groups have the dynamic where everyone contributes, or at least tries to, which makes team evaluations pretty simple and the app gets done. I had the opposite experience where all of my teammates did nothing (no contribution to the app/no communication). I would say that the course syllabus safeguards against this though since it's made pretty clear that people can fail the course for not contributing to the project's codebase, it was more a rare and unfortunate experience. Other than communicating issues early to course staff and attempting to address the problem within the group as soon as possible there's not much you can do. Based on your group and your prior experience, your workload can vary from 2-10 hours a sprint. Overall, I found it a pretty reasonable course, learned a moderate amount about Django / principles of software development in the real world. #tCFF23