Traditionally Configuration Management has been focused on the CMDB and change management. With modern software development methods like Agile and Scrum, do we still need to do these old-fashioned things? Is the CMDB just a git repo and change management nothing but stories and a Kanban board? If not, what extra is it that CM can contribute and how should it be done?
There are also many things that are done differently from the traditional Waterfall method - which of these things are related to CM and how should they be handled?
Many questions - hopefully interesting and with some constructive discussions maybe also some useful answers.