<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>About the Selection of a Business Process Improvement Methodology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Steven Gross</string-name>
          <email>steven.gross@wu.ac.at</email>
        </contrib>
      </contrib-group>
      <pub-date>
        <year>1990</year>
      </pub-date>
      <fpage>104</fpage>
      <lpage>112</lpage>
      <abstract>
        <p>Organizations seek to change the design of their business processes in order to respond to a changing and challenging environment. A wide variety of business process improvement methodologies exist which aim to support practitioners in this effort. However, the selection of an appropriate approach is by no means trivial. Ideally, the characteristics of the methodology applied should fit the characteristics of the process improvement project in order to yield the best results. In this research proposal, we outline how the design science research methodology (DSRM) is adopted to develop, test, and evaluate a meta-methodology for the selection of an appropriate business process improvement methodology.</p>
      </abstract>
      <kwd-group>
        <kwd>business process improvement</kwd>
        <kwd>process redesign</kwd>
        <kwd>process innovation</kwd>
        <kwd>methodology selection</kwd>
        <kwd>methodology development</kwd>
        <kwd>design science research</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The organic nature of organizations, the need to respond to increasing competitive
pressure and customer expectations, and the ever changing organizational environment, to
only mention a few, are challenges that call for a consideration how business processes
are designed and carried out [Du13]. To respond to these challenges, practitioners use and
rely on methodologies instead of chaotic “trial-and-error” approaches to systematically
derive improved business processes [KTG97]. Business process reengineering as first
introduced by Hammer [Ha90, HC93], and business process redesign as responded by
Davenport and Short [DS90] are historically developed methodologies that aim to guide
practitioners through the process of process improvement. Since then, a variety of new
and refined business process improvement methodologies have been introduced.
The selection of an appropriate methodology plays a key role for the success of the
improvement project [In02] and thus should be considered carefully. However, given the
numerous methodologies on the market, this selection is not a trivial task. Several studies
have undertaken the effort to merge different improvement approaches with the aim to
combine their advantages [GKT93, LC01, HC04, PS10] or focused on customizing
composite methodologies [KTG97, In02]. However, it has been shown that different
methodologies are most appropriate for dealing each with a specific type of problem
[JK84], so the usefulness of holistic improvement approaches can be questioned.
To the best of our knowledge, there is no systematic approach that guides practitioners
through the selection of an appropriate business process improvement methodology that
meets the improvement project’s characteristics. Therefore, it is our intention to address
this research gap accordingly and develop a meta-methodology which guides through the
selection of an improvement methodology that meets the improvement project’s needs.
Against this background, the research question is
−</p>
      <p>How can organizations find a business process improvement methodology
that supports their improvement project most appropriately?
In the following section the background and motivation will first be elaborated. In the
consecutive method section, it will be outlined, how the research question is planned to be
answered. This proposal ends with a description about the expected research contribution.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Background &amp; Motivation</title>
      <p>In the broad sense, a methodology can be defined as “any kind of advice given to analysts
about how they should proceed to intervene in the real world” [JK84, p. 477]. More
concrete, a methodology is a set of principles a user adopts to guide through the actions to
improve a perceived real-world problem situation [Ch84]. The problem in this case is the
discrepancy between the current and the potential state of a business process, in terms of
fulfilling the specified improvement objective(s). A methodology in the context of process
improvement guides through and limits the (potentially unlimited) solution space from all
available- to a specific process design.
2.1</p>
      <sec id="sec-2-1">
        <title>Improvement methodologies and their characteristics</title>
        <p>There is a great number of improvement methodologies available on the market. In this
context we use the term business process improvement generically: it entails all initiatives
to change the design of a business process for the better, e.g. process redesign,
reengineering, -innovation, and -optimization. There exist specific methodologies for
different kinds of processes (e.g. knowledge intense [MBI15] and supply chain processes
[PNR14]) and methodologies for different sectors (e.g. for the public-, construction-, and
education sector [KW05, KBW07, Ab11]). Methodologies also differ in their scope: From
rather narrowly focusing on the act of redesigning the process itself [LC01], to a rather
holistic approach [Po98]. Additionally, methodologies are more or less strict about the
application of the steps and activities involved. For instance, [SB05] is purposely
developed as a structured step-by-step approach, while [KW05] was designed with a
minimum of procedural structure. Both are claiming that their specific methodological</p>
        <p>Selection of a business process improvement methodology 31
design is beneficial for achieving the improvement goal. These and other characteristics
lead practitioners to be confused by the choice of methodologies available [In02].
2.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Improvement projects and their characteristics</title>
        <p>A business process improvement project has distinct characteristics. Kettinger et al.
[KTG97] for instance identified four characteristics, namely project radicalness, process
structuredness, customer focus, and potential of IT enablement. Project radicalness and
customer focus is what we label as the ‘improvement intensions’, the process
structuredness is part of the ‘business process’ characteristic. We want to add
improvement objectives to this list of characteristics, as these set out the direction of the
improvement effort. The improvement objectives should be derived from the firm’s
strategic vision [DS90]. Typical objectives, to only mention a few, are cost reduction, time
reduction, increased output quality, but also improved quality of work life, empowerment
[DS90], flexibility [JR05] and innovation [In02], or a mix of these. Improvement projects
are likely to have other characteristics that define them, which we intend to identify.
2.3</p>
      </sec>
      <sec id="sec-2-3">
        <title>Finding an appropriate improvement methodology</title>
        <p>As the work of Jackson and Keys [JK84] points out, a problem-solving methodology is
likely to be of use for a specific type of problem and the problem’s context. They
specifically state that “no one methodology is likely to be of use in all circumstances”
[JK84, p. 477]. It is thus crucial to analyze the problem context correctly as well as to
identify the appropriate methodology for this problem [JK84]. In the context of business
process improvement it has also been acknowledged, that specific characteristics of the
improvement project call for different methodologies [KTG97].
Thus, to increase the fitness between the characteristics of the improvement project and
the corresponding methodology (Fig. 1), an appropriate methodology has to be selected
[Ch97]. We define a methodology to be appropriate for an improvement project, if its
characteristics match the characteristics of the improvement project, e.g. the
methodological focus encompasses the type of business process to be improved. In this
way it facilitates to achieve the improvement objectives and intensions for the kind of
business process to be improved. Taking into consideration the elaborated need to find an
appropriate business process improvement methodology, it is the aim of this study to
develop a meta-methodology that assists in finding an improvement methodology that best
fits the characteristics of the improvement project.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Methods</title>
      <p>To develop the meta-methodology, design science research methodology (DSRM) as
introduced by Peffers et al. [Pe07] will be adopted. This methodology is extensively used
for the development and evaluation of artefacts [Br11, DJ12, Sh14]. It consists of six
activities, and in the following, the activities and how they are applied will be described.
The first activity ‘problem identification and motivation’ refers to the specific research
problem and the value of the potential solution [Pe07]. As mentioned, characteristics of
both, the improvement projects and the improvement methodologies have to be identified,
since these determine the fitness between both. Hence, as a first step in this activity, a
systematic literature review will be conducted as described in [Ki10] to get a
comprehensive overview which methodologies for the improvement of business processes
are actually available. The data collected through the literature review comprises for each
methodology the following information (if applicable): Its goal and definition, the entailed
steps and activities, the recommended area of application, the objectives followed, on
which methodology it is built on, and which concepts it deploys. This data will then be
used to find distinguishing characteristics in the improvement methodologies found. To
determine characteristics that differentiate improvement projects, two sources of data will
be used: First, the case studies that describe the application of methodologies found in the
systematic literature review will be analyzed. To complement this data, practitioners will
also be interviewed in the form of semi-structured in-depth interviews [RR12]. To analyze
and interpret the data obtained in this interviews, the grounded theory method will be used
as described in [SR09, ULM10]. These results are essential for the later development of
the meta-methodology. Based on this, we will then justify how the characteristics of the
methodology have to meet the characteristics of the improvement project and that the
meta-methodology is of great use for practitioners.</p>
      <p>In the second activity ‘define the objectives for a solution’, objectives of the solution are
inferred, given the problem definition and general knowledge about what is possible and
feasible [Pe07]. The desired features and functionality of the meta-methodology are closer
described in this section, based on the results from the first activity and the research
background.</p>
      <p>In the third activity ‘design and development’ the methodology is created. This is done by
using the theory and knowledge obtained in the first and the objectives defined in the
second activity. The main task will be to find out how to match characteristics from a
project systematically with characteristics of an appropriate methodology. Since it is</p>
      <p>Selection of a business process improvement methodology 33
impractical to do this for every improvement methodology, methodologies with similar
characteristics will be grouped.</p>
      <p>The fourth activity is ‘demonstration’. Here, the artifact, in this context the
metamethodology, will be used to solve one or more instances of the problem [Pe07]. We
perform this step by conducting a case study, in which practitioners with an experience in
the field are asked to use the meta-methodology to select an appropriate improvement
methodology for fictional improvement projects. We will conduct semi-structured
indepth interviews [RR12] with the participants to get an insight about the perceived
usefulness of the meta-methodology and use this feedback to modify it accordingly.
‘Evaluation’ is the fifth activity and aims to measure how well an artifact supports a
solution to the problem [Pe07]. First, it will be assessed whether the developed
methodology fulfills the objectives defined in the second activity of DSRM. Since to the
best of our knowledge there is no other methodology that aims to guide through the
selection of an improvement methodology, it cannot be evaluated against another
approach. Therefore, we introduce usability, comprehensibility, and completeness as an
initial set of measures, while acknowledging that these still need to be extended and
refined. To evaluate this quality attributes it is planned to design and conduct a controlled
experiments with students, which is one evaluation method proposed in [He04]. The
metamethodology should also produce the same output given the same project characteristics.
To evaluate this consistency, different descriptions of fictional improvement projects with
distinct characteristics will be created during the design of the experiment. A group of
students will then be provided a random project description, with the aim to use the
metamethodology to select an improvement methodology. The results can then be used to asses
the consistency of outputs for students with the same project descriptions.
The last activity ‘communication’ aims to disseminate the research results [Pe07].
4</p>
    </sec>
    <sec id="sec-4">
      <title>Expected contribution</title>
      <p>The main contribution of this work is the development of a meta-methodology for
selecting a business process improvement methodology. This will be of great help for
practitioners in the initial phase of an improvement project. No two improvement projects
are alike [In02] and the use of the developed meta-methodology is expected to save time
during the selection process and will ultimately lead to better improvement results through
meeting the improvement project’s characteristics.</p>
      <p>The second contribution is the theoretical analysis of the characteristics of improvement
methodologies, improvement projects and their interrelationship. For the further
development of improvement methodologies, this theoretical basis can help to assess
whether more targeted improvement methodologies for certain project characteristics still
need to be developed.
[Du13]
[KTG97]
[Ha90]
[HC93]
[DS90]
[In02]
[GKT93]
[LC01]
[HC04]
[PS10]
[JK84]
[Ch84]
[MBI15]
[PNR14]
[KW05]</p>
      <p>Dumas, M., et al.: Fundamentals of Business Process Management. Springer-Verlag
Berlin Heidelberg, 2013.</p>
      <p>Kettinger, W.J.; Teng, J.T.C.; Guha, S.: Business process change: A study of
methodologies, techniques, and tools. MIS Quarterly, 21/1, pp. 55-80, 1997.</p>
      <p>Hammer, M.; Champy, J.: Reengineering the Corporation: A Manifesto for Business
Revolution. Harper Business, 1993.</p>
      <p>Davenport, T.H.; Short, J.E.: The new industrial engineering - information technology
and business process redesign. Sloan management review, 31/4, pp. 11-27, 1990.
Ing-Long, W.: A model for implementing BPR based on strategic perspectives: An
empirical study. Information &amp; Management, 39/4, pp. 313-324, 2002.</p>
      <p>Selection of a business process improvement methodology</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Guha</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Kettinger</surname>
            ,
            <given-names>W.J.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Teng</surname>
            ,
            <given-names>J.T.C.</given-names>
          </string-name>
          :
          <article-title>Business process reengineering: Building a Comprehensive Methodology</article-title>
          .
          <source>Information Systems Management</source>
          ,
          <volume>10</volume>
          /3, pp.
          <fpage>13</fpage>
          -
          <lpage>22</lpage>
          ,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>K.T.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Chuah</surname>
            ,
            <given-names>K.B.</given-names>
          </string-name>
          :
          <article-title>A SUPER methodology for business process improvement ‐ An industrial case study in Hong Kong/China</article-title>
          .
          <source>International Journal of Operations &amp; Production Management</source>
          ,
          <volume>21</volume>
          /5/6, pp.
          <fpage>687</fpage>
          -
          <lpage>706</lpage>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>Hwang</surname>
          </string-name>
          , I.-S.;
          <string-name>
            <surname>Chung-Li</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>A Systematic Approach to Optimizing Business Processes beyond ISO 9000: A Taiwanese Case Study</article-title>
          .
          <source>International Journal of Management</source>
          ,
          <volume>21</volume>
          /3, pp.
          <fpage>349</fpage>
          -
          <lpage>360</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Pepper</surname>
            ,
            <given-names>M.P.J.</given-names>
          </string-name>
          ; Spedding,
          <string-name>
            <surname>T.A.</surname>
          </string-name>
          :
          <article-title>The evolution of lean Six Sigma</article-title>
          .
          <source>International Journal of Quality &amp; Reliability Management</source>
          ,
          <volume>27</volume>
          /2, pp.
          <fpage>138</fpage>
          -
          <lpage>155</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Jackson</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Keys</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Towards a System of Systems Methodologies</article-title>
          .
          <source>The Journal of the Operational Research Society</source>
          ,
          <volume>35</volume>
          /6, pp.
          <fpage>473</fpage>
          -
          <lpage>486</lpage>
          ,
          <year>1984</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Checkland</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Systems thinking, systems practice</article-title>
          .
          <source>Wiley: Chichester</source>
          <year>1984</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>Manfreda</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Buh</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ; Indihar, Š.M.
          <article-title>: Knowledge-intensive process management: a case study from the public sector</article-title>
          .
          <source>Baltic Journal of Management</source>
          ,
          <volume>10</volume>
          /4, pp.
          <fpage>456</fpage>
          -
          <lpage>477</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <surname>Palma-Mendoza</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Neailey</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Roy</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Business process re-design methodology to support supply chain integration</article-title>
          .
          <source>International Journal of Information Management</source>
          ,
          <volume>34</volume>
          /2, pp.
          <fpage>167</fpage>
          -
          <lpage>176</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <surname>Kawalek</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Wastall</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Pursuing Radical Transformation in Information Age Government: Case Studies Using the SPRINT Methodology</article-title>
          .
          <source>Journal of Global Information Management</source>
          ,
          <volume>13</volume>
          /1, pp.
          <fpage>79</fpage>
          -
          <lpage>101</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [KBW07]
          <string-name>
            <surname>Khan</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Bali</surname>
            ,
            <given-names>R.K.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Wickramasinghe</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          :
          <article-title>Developing a BPI framework and PAM for SMEs</article-title>
          .
          <source>Industrial Management &amp; Data Systems</source>
          ,
          <volume>107</volume>
          /3, pp.
          <fpage>345</fpage>
          -
          <lpage>360</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <source>[Ab11] [Po98] [SB05] [JR05] [Ch97] [Pe07] [Br11] [DJ12] [Sh14] [Ki10] [RR12] [SR09]</source>
          <string-name>
            <surname>Abdous</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <year>h</year>
          .:
          <article-title>Towards a framework for business process reengineering in higher education</article-title>
          .
          <source>Journal of Higher Education Policy and Management</source>
          ,
          <volume>33</volume>
          /4, pp.
          <fpage>427</fpage>
          -
          <lpage>433</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <string-name>
            <surname>Povey</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>The development of a best practice business process improvement methodology</article-title>
          .
          <source>Benchmarking for Quality Management &amp; Technology, 5/1</source>
          , pp.
          <fpage>27</fpage>
          -
          <lpage>44</lpage>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <surname>Sola</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Baines</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Developing and evaluating a methodology for business process improvement</article-title>
          .
          <source>Business Process Management Journal</source>
          ,
          <volume>11</volume>
          /1, pp.
          <fpage>37</fpage>
          -
          <lpage>46</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          <string-name>
            <surname>Jansen-Vullers</surname>
            ,
            <given-names>M.H.</given-names>
          </string-name>
          ; Reijers,
          <string-name>
            <surname>H.A.</surname>
          </string-name>
          :
          <article-title>Business process redesign in healthcare: towards a structured approach</article-title>
          .
          <source>INFOR: Information Systems and Operational Research</source>
          ,
          <volume>43</volume>
          /4, pp.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          <string-name>
            <surname>Chatzoglou</surname>
          </string-name>
          , P.D.:
          <article-title>Use of methodologies: an empirical analysis of their impact on the economics of the development process</article-title>
          .
          <source>European Journal of Information Systems</source>
          ,
          <volume>6</volume>
          /4, pp.
          <fpage>256</fpage>
          -
          <lpage>270</lpage>
          ,
          <year>1997</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          <string-name>
            <surname>Peffers</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , et al.:
          <source>A Design Science Research Methodology for Information Systems Research. Journal of Management Information Systems</source>
          ,
          <volume>24</volume>
          /3, pp.
          <fpage>45</fpage>
          -
          <lpage>77</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          <string-name>
            <surname>Bragge</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , et al.:
          <article-title>Designing a Repeatable Collaboration Method for Setting Up Emerging Value Systems for New Technology Fields</article-title>
          .
          <source>JITTA : Journal of Information Technology Theory and Application</source>
          ,
          <volume>12</volume>
          /3, pp.
          <fpage>27</fpage>
          -
          <lpage>46</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          <string-name>
            <surname>Dietz</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ; Juhrisch,
          <string-name>
            <surname>M.</surname>
          </string-name>
          :
          <article-title>Negotiating language barriers - a methodology for crossorganisational conceptual modelling</article-title>
          .
          <source>European Journal of Information Systems</source>
          ,
          <volume>21</volume>
          /3, pp.
          <fpage>229</fpage>
          -
          <lpage>254</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          <string-name>
            <surname>Shrestha</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , et al.:
          <article-title>A Method to Select IT Service Management Processes for Improvement</article-title>
          .
          <source>JITTA : Journal of Information Technology Theory and Application</source>
          ,
          <volume>15</volume>
          /3, pp.
          <fpage>31</fpage>
          -
          <lpage>55</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          <string-name>
            <surname>Kitchenham</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , et al.:
          <article-title>Systematic literature reviews in software engineering - A tertiary study</article-title>
          .
          <source>Information and Software Technology, 52/8</source>
          , pp.
          <fpage>792</fpage>
          -
          <lpage>805</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          <string-name>
            <surname>Rubin</surname>
            ,
            <given-names>H.J.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Rubin</surname>
            ,
            <given-names>I.S.</given-names>
          </string-name>
          :
          <article-title>Qualitative Interviewing: The Art of Hearing Data</article-title>
          .
          <source>SAGE Publications</source>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          <string-name>
            <surname>Seidel</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Recker</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          :
          <article-title>Using grounded theory for studying business process management phenomena</article-title>
          . In
          <string-name>
            <surname>(M. de Marco; C. Loebecke</surname>
          </string-name>
          ; L. Willcocks, eds.):
          <source>The 17th European Conference on Information Systems</source>
          . Faculty of Economics of the University of Verona,
          <source>Verona: Association for Information Systems</source>
          .
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [ULM10]
          <string-name>
            <surname>Urquhart</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Lehmann</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ; Myers,
          <string-name>
            <surname>M.D.</surname>
          </string-name>
          :
          <article-title>Putting the 'theory' back into grounded theory: guidelines for grounded theory studies in information systems</article-title>
          .
          <source>Information Systems Journal</source>
          ,
          <volume>20</volume>
          /4, pp.
          <fpage>357</fpage>
          -
          <lpage>381</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [He04]
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A.R.</given-names>
          </string-name>
          , et al.:
          <article-title>Design science in information systems research</article-title>
          .
          <source>MIS Quarterly</source>
          ,
          <volume>28</volume>
          /1, pp.
          <fpage>75</fpage>
          -
          <lpage>105</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>