← Back to context

Comment by spectre256

9 years ago

I have a similar story for a college course also titled "Software Engineering". Essentially, it was a course on how to properly execute the waterfall model of design.

We were assigned teams of four, wrote hundreds of pages of requirement papers, design papers, everything papers. Then we wrote the code in PHP in one night.

For the final section of the class, 3 teams of 4 were merged into teams of 12. It's obvious that no college students have the desire or ability to manage a team of 12, as it's a huge task even for an experienced manager. The overhead of having 12 people involved was incredible. Fortunately, more than half the students in the group were happy to be "fired": we didn't talk to them at all, did the work in a smaller, more nimble group, and everyone got a good grade.

Sounds quite outdated with the excessive documentation, etc. However, believe that learning a sequential process first has some advantages in shaping the mental model and experience with pros/cons later when learning agile. What do you think?