What should people learn about SCM? Lund University is one of only a couple of universities in the world that has a dedicated full-time course (200 hours) on SCM - and we also give a smaller introductory course (28 hours) around Europe. However, even if the courses work and are attractive from a student perspective, it is not clear if we teach the right things and in particular at the right levels from the industry's perspective.
The full-time course is intended for students who want to make SCM a larger or smaller part of
their future career. They might become your future colleague - or jump in as configuration
manager when you leave for a better job. They might also "just" become the "SCM-knowledgable
person" that can fix SCM-matters for a team in case it is needed.
The introductory course, on the other hand, has more modest goals and aims at giving students an awareness of what SCM is and why it is needed. These students might become your company's future employees (or even project managers) and you might find it helpful if they can understand the "SCM-lingo" you speak and are able to follow the simple SCM-processes you try to implement and enforce.
Even if the "theory" of SCM is rather well established, it is not so clear about how important different aspects of SCM is in real life for practitioners. What is that gets applied every day and where a deep understanding is needed - and what things are more on the "nice to know" level in case it should happen once in a while?
Join the discussion and help shape the future of SCM education. What skills would you like future colleagues/employees to have? What should they just have heared about and what should they be able to apply? Do you have any ideas for "problems" that students can discuss and try to solve during exercise sessions? Do you have things you think are important for them to investigate and explore during tool labs? Do you have proposals for "case studies" they could do for the project part of the full course?