Change is inevitable when software is built and deployed. It’s not particularly problematic to manage change if there is just one system. But in a large global IT organization, with several systems and people who develop, problems may arise. If organizations don’t control change, change will control the organization. Software Configuration Management (SCM) is a set of activities to manage change by identifying objects that are likely to change, establishing relationships among them, managing different versions of the objects, controlling the changes imposed and reporting on the changes made. A way to support the work of SCM is to follow standards. A standard can be compared to a type of rule, but also a directive. In this study we examined how a multinational organization applies standards within SCM. We examined the challenges with applying standards. We also examined whether there are deviations from standards, and in such cases why did the deviations arise and what are the following consequences? The study is based on a qualitative case study that employed interviews with developers, IT architects, operations manager and solution leader. The result of this study shows that some of the challenges in applying standards within SCM are: legacy systems, globalization, CMDB and ITSM-related tools (and their processes). The study also shows that standardization within maintenance is complex and that it’s easily breach and forgotten. The study shows that the consequence of this is that the developers must constantly compromise with standards. The result of this compromise is that it’s possible to carry out the business, but the solutions may not meet standards. In this study we concluded that the organization need to direct more attention towards maintenance, and less on new development.