@article{KopperKlotzWestneretal., author = {Kopper, Andreas and Klotz, Stefan and Westner, Markus and Strahringer, Susanne}, title = {Shadow IT and Business-managed IT}, series = {Journal of Information Technology Management (JITM)}, volume = {30}, journal = {Journal of Information Technology Management (JITM)}, number = {4}, issn = {1042-1319}, pages = {25}, abstract = {Two concepts describe the autonomous deployment of IT by business entities: Shadow IT and Business-managed IT. Shadow IT is deployed covertly, that is, software, hardware, or IT services created/procured or managed by business entities without alignment with the IT organization. In contrast, Business-managed IT describes the overt deployment of IT, that is, in alignment with the IT organization or in a split responsibility model. The purpose of this paper is to extend the conceptual understanding of Shadow IT and Business-managed IT, comparing the perceptions of 29 CIOs and senior IT managers with the results of a systematic literature review. By doing so, this paper presents a structured and comprehensive view of causing factors, outcomes, and governance of Shadow IT and Business-managed IT in practice. A comparison of academic literature and practitioner perceptions reveals the limitations and gaps of the current research and highlights avenues for future research. The authors find three category-spanning themes occurring as causing factors, outcomes, and—as part of governance measures—factors to improve the IT organization: (1) (Poor) business-IT alignment (2) (lack of) agility, and (3) (lack of) policies. This study is innovative with its comprehensive qualitative interview data that the authors compare to the existing literature. Therefore, the paper brings together theoretical and practical insights into Shadow IT and Businessmanaged IT, which should aid practitioners and scholars in decision making and future research.}, subject = {Corporate Governance}, language = {en} } @article{KaessBrosigWestneretal., author = {K{\"a}ss, Sebastian and Brosig, Christoph and Westner, Markus and Strahringer, Susanne}, title = {Short and sweet: multiple mini case studies as a form of rigorous case study research}, series = {Information Systems and e-Business Management}, journal = {Information Systems and e-Business Management}, publisher = {Springer Nature}, doi = {10.1007/s10257-024-00674-2}, pages = {34}, abstract = {Case study research is one of the most widely used research methods in Information Systems (IS). In recent years, an increasing number of publications have used case studies with few sources of evidence, such as single interviews per case. While there is much methodological guidance on rigorously conducting multiple case studies, it remains unclear how researchers can achieve an acceptable level of rigour for this emerging type of multiple case study with few sources of evidence, i.e., multiple mini case studies. In this context, we synthesise methodological guidance for multiple case study research from a cross-disciplinary perspective to develop an analytical framework. Furthermore, we calibrate this analytical framework to multiple mini case studies by reviewing previous IS publications that use multiple mini case studies to provide guidelines to conduct multiple mini case studies rigorously. We also offer a conceptual definition of multiple mini case studies, distinguish them from other research approaches, and position multiple mini case studies as a pragmatic and rigorous approach to research emerging and innovative phenomena in IS.}, language = {en} } @article{KlotzKopperWestneretal., author = {Klotz, Stefan and Kopper, Andreas and Westner, Markus and Strahringer, Susanne}, title = {Von Schatten-IT zu Business-managed IT: Fachbereichs-IT gezielt gestalten}, series = {Wirtschaftsinformatik \& Management}, volume = {14}, journal = {Wirtschaftsinformatik \& Management}, number = {4}, publisher = {Springer Nature}, issn = {1867-5913}, doi = {10.1365/s35764-022-00421-7}, pages = {282 -- 287}, abstract = {Fachbereichs-IT, Schatten-IT, Business-managed IT. All diese Begriffe beschreiben IT, die neben den eigentlichen, regul{\"a}ren IT-Systemen oder -Prozessen in Unternehmen existieren und von Mitarbeiterinnen und Mitarbeitern der Fachbereiche genutzt werden. Im Fall von„Schatten-IT" handelt es sich um IT-Systeme und -Prozesse (IT-Instanzen), die sich ohne Kenntnis der IT-Verantwortlichen etabliert haben; im Fall von„Business-managed IT" entstehen die IT-Systeme und -Prozesse in Kenntnis der bzw. in Abstimmung mit den IT-Verantwortlichen im Unternehmen.„Fachbereichs-IT" subsumiert Schatten-IT und Business-managed IT. Welche Ursachen f{\"u}hren zu solchen IT-Instanzen, welche Potenziale und Risiken haben diese IT-Instanzen und wie lassen sie sich steuern?}, language = {de} } @inproceedings{KlotzWestnerStrahringer, author = {Klotz, Stefan and Westner, Markus and Strahringer, Susanne}, title = {From Shadow IT to Business-managed IT and Back Again}, series = {Pacific Asia Conference on Information Systems (PACIS): 2020, Dubai}, booktitle = {Pacific Asia Conference on Information Systems (PACIS): 2020, Dubai}, pages = {14}, abstract = {Today, information technology (IT) is not anymore solely deployed and maintained by the IT organization, but also by business units. IT deployed or managed by business units is called Shadow IT (without alignment with the IT organization) or Business-managed IT (in alignment or a split responsibility model with the IT organization), contrasting "classical" IT. However, the responsibility for deployed IT might change over time. Therefore, this paper conceptualizes the progression of the responsibility for IT as a trajectory through initialization, potential transitions, and discontinuance. The paper illustrates this conceptual framework using four exemplary case vignettes of IT instances. Empirical findings of the case vignettes determine indications when employees initialize an IT instance as Shadow IT, Business-managed IT, or IT-managed systems and reasons why the responsibility for an IT instance changes over time. The results suggest that scholars and practitioners should add a temporal dimension to the governance of IT instances.}, subject = {IT-Governance}, language = {en} } @article{KlotzKopperWestneretal., author = {Klotz, Stefan and Kopper, Andreas and Westner, Markus and Strahringer, Susanne}, title = {Causing factors, outcomes, and governance of Shadow IT and business-managed IT}, series = {International Journal of Information Systems and Project Management}, volume = {7}, journal = {International Journal of Information Systems and Project Management}, number = {1}, issn = {2182-7796}, doi = {10.12821/ijispm070102}, pages = {15 -- 43}, abstract = {Shadow IT and Business-managed IT describe the autonomous deployment/procurement or management of Information Technology (IT) instances, i.e., software, hardware, or IT services, by business entities. For Shadow IT, this happens covertly, i.e., without alignment with the IT organization; for Business-managed IT this happens overtly, i.e., in alignment with the IT organization or in a split responsibility model. We conduct a systematic literature review and structure the identified research themes in a framework of causing factors, outcomes, and governance. As causing factors, we identify enablers, motivators, and missing barriers. Outcomes can be benefits as well as risks/shortcomings of Shadow IT and Business-managed IT. Concerning governance, we distinguish two subcategories: general governance for Shadow IT and Business-managed IT and instance governance for overt Business-managed IT. Thus, a specific set of governance approaches exists for Business-managed IT that cannot be applied to Shadow IT due to its covert nature. Hence, we extend the existing conceptual understanding and allocate research themes to Shadow IT, Business-managed IT, or both concepts and particularly distinguish the governance of the two concepts. Besides, we find that governance themes have been the primary research focus since 2016, whereas older publications (until 2015) focused on causing factors.}, subject = {Betriebliches Informationssystem}, language = {en} }