<!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>Questioning the Design of Business Process Maturity Models</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Amy Van Looy</string-name>
          <email>Amy.VanLooy@UGent.be</email>
          <email>amy.vanlooy@hogent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Manu De Backer</string-name>
          <email>Manu.DeBacker@UGent.be</email>
          <email>Manu.DeBacker@econ.kuleuven.be</email>
          <email>Manu.DeBacker@ua.ac.be</email>
          <email>manu.debacker@hogent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Geert Poels</string-name>
          <email>Geert.Poels@UGent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ghent University, Department of Management Information Science &amp; Operations Management</institution>
          ,
          <addr-line>Tweekerkenstraat 2, B-9000 Ghent</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>K.U.Leuven, Department of Management Informatics</institution>
          ,
          <addr-line>Naamsestraat 69, B-3000 Leuven</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University College Ghent, Department of Management &amp; Informatics</institution>
          ,
          <addr-line>Voskenslaan 270, B-9000 Ghent</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Antwerp, Department of Management Information Systems</institution>
          ,
          <addr-line>Prinsstraat 13, B-2000 Antwerp</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
      </contrib-group>
      <fpage>51</fpage>
      <lpage>60</lpage>
      <abstract>
        <p>The importance of business process management goes without saying. As its realization is less straightforward, maturity models have been developed to gradually assess and improve business processes. Although their aim is to assist organizations, the proliferation of maturity models also confuses organizations. They have no overview of existing models and their differences, which makes an informed choice difficult. Choosing the right business process maturity model (BPMM) is however important, as previous research indicated the existence of different maturity types being measured by the existing models [1]. We now add further design elements to our comparative framework by conducting a content analysis of 69 BPMMs. Afterwards, the identified design elements are transformed into a questionnaire that practitioners can use to find the BPMM that best fits their needs. In this paper, we present 16 questions to be included in the questionnaire, without elaborating on the mapping of individual maturity models.</p>
      </abstract>
      <kwd-group>
        <kwd>business process maturity</kwd>
        <kwd>business process management</kwd>
        <kwd>business process orientation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Today’s globalized market is characterized by demanding customers and growing IT
possibilities. Organizations are therefore increasingly relying on their way of
working, i.e. business processes, to excel [
        <xref ref-type="bibr" rid="ref2 ref26 ref3">2,3</xref>
        ]. However, merely modeling and
deploying a business process does not imply that your business process is also an
excellent one, or at least a good one. Therefore, the notion of ‘maturity’ is introduced
as a measure to indicate how excellent business processes can perform [
        <xref ref-type="bibr" rid="ref2 ref26 ref4">2,4</xref>
        ]. Maturity
requires continuous process improvements, which are not easy to realize. Hence,
business process maturity models (BPMMs) have been designed from which
organizations gradually benefit. In general, a maturity model (MM) is a tool to
systematically assess and improve capabilities, i.e. abilities or competences, to reach a
goal. Translated to BPMM, it concerns the capabilities of business processes and their
organizations to reach business (process) excellence. An example is given below.
      </p>
      <p>Level 5 - Innovating
• Continuously improving practices
(as proactive behaviour)
Level 4 - Predictable</p>
      <p>• Quantitatively managed practices
Level 3 - Standardised</p>
      <p>• Standardised end-to-end practices
Level 2 - Managed</p>
      <p>
        • Repeatable practices within the work unit
Level 1 – Initial
• Ad hoc practices
Currently, a BPMM proliferation exists [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This proliferation raises questions about
the differences between BPMM designs. To our knowledge, some comparative
attempts have been made by Hüffner [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], Lee, Lee, and Kang [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], Maier, Moultrie,
and Clarkson [
        <xref ref-type="bibr" rid="ref27 ref9">9</xref>
        ], and Rosemann and de Bruin [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Nonetheless, they do not intend
to offer a comprehensive comparative study on a large number of BPMMs. For this
purpose, two research questions are raised.
      </p>
      <p>RQ1. On which design elements do existing BPMMs differ?</p>
      <p> A comparative framework is built to classify existing BPMMs.</p>
      <p>RQ2. Which BPMM must be chosen when?
 A questionnaire is derived from the comparative framework to obtain a
practical instrument that managers can use while choosing a BPMM.</p>
      <p>We start with defining a maturity model in section 2, and more specifically a BPMM
in section 3. Section 4 clarifies the methodology. It is followed by presenting (section
5) and discussing (section 6) the BPMM comparative framework (RQ1) and the
BPMM questionnaire (RQ2). Finally, we summarize the results and future research.</p>
    </sec>
    <sec id="sec-2">
      <title>Maturity Model (MM)</title>
      <p>
        An overall definition for a maturity model (MM) is provided by Tapia et al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]:
‘MMs have been developed to assess specific areas against a norm. Based on
maturity assessments, organizations know the extent to which activities in such areas
are predictable’ [11,pp.71].
      </p>
      <p>
        MMs share some design elements, independent of whether they deal with business
processes, business-IT alignment, e-government, quality management, etc. Table 1
lists those design elements found in the literature on MM design [
        <xref ref-type="bibr" rid="ref11 ref12 ref13 ref14 ref15 ref4">12,13,4,14,11,15</xref>
        ].
The emphasis is on who measures maturity (i.e. assessors – ‘WHO’), and how it is
measured (i.e. assessment method – ‘HOW’). Furthermore, the table clarifies what is
measured as maturity, i.e. capability areas and their improvements necessary to reach
each consecutive level (i.e. improvement method – ‘WHAT’).
      </p>
      <p>
        Business Process Maturity Model (BPMM)
Translated towards business processes, BPMMs are evolutionary models for
measuring (AS-IS) and improving (TO-BE) maturity, or ‘the extent to which an
organization consistently implements processes within a defined scope that
contributes to the achievement of its business goals’ [16,pp.2]. Mature business
X
X
X
X
X
X
X
X
X
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]
      </p>
      <p>
        X
X
X
X
X
X
X
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]
      </p>
      <p>
        X
X
X
X
X
X
X
X
[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]
      </p>
      <p>
        X
X
X
X
X
X
X
X
X
processes acquire the necessary capabilities to reach excellence. Capabilities are
competencies (e.g. skills and knowledge) to achieve the targeted results, i.e. the
ability to perform, or the expected performance of a business process. Related
capabilities are collected into capability areas. Maturity levels indicate the growth
through all capability areas together. Sometimes, capability levels are present to
indicate the growth through each capability area separately [
        <xref ref-type="bibr" rid="ref10 ref17 ref18">17,18,10</xref>
        ].
      </p>
      <p>
        Capability areas differentiate a BPMM from other MMs. Previous research [
        <xref ref-type="bibr" rid="ref1 ref19">1,19</xref>
        ]
has identified six main capability areas from the definitions for three fundamental
domains in the business process literature: (1) business process (BP), (2) business
process management (BPM), and (3) business process orientation (BPO).
      </p>
      <p>
        First, business process definitions implicitly focus on business process modeling
and deployment. The latter means running processes in real life. It requires modeling
or predefining business processes in textual or graphical descriptions [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. For
instance, ‘a process is a series of interconnected activities that takes input, adds value
to it, and produces output. It’s how organizations work their day-to-day routines’
[2,pp.xxii]. Both aspects are selected as main capability areas.
      </p>
      <p>
        Secondly, BPM involves continuously managing and improving business
processes, guided by process owners. Gillot [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ], Gulledge Jr. and Sommer [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]
summarize four foci in BPM definitions: (1) modeling, (2) deployment, (3)
optimization, or improving business processes based on real metrics, and (4) the
management of business processes, each with a process owner and a cross-functional
team. For instance, Weske [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] defines BPM as ‘concepts, methods, and techniques to
support the (1) design, (4) administration, (2) configuration, enactment, and (3)
analysis of business processes’ [20,pp.5]. Similarly to BP, these four foci are selected
as main capability areas. BPM differs by also addressing optimization and managerial
efforts for one, more or all business processes.
      </p>
      <p>
        Some authors go beyond these four BPM areas by also referring to organization
management. Particularly, by adopting (5) a process-oriented culture with rewards
linked to the performance of business processes instead of departments, and (6) a
horizontal structure [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. For instance, McCormack [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ] defines BPO as ‘an
organization that emphasizes process, a process oriented way of thinking, outcomes
and customers as opposed to hierarchies’[24,pp.6]. Although the distinction between
BPM and BPO is not always explicitly made, e.g. in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], it allow separately
examining the different nuances.
      </p>
      <p>
        Consequently, six main capability areas are derived from the BP, BPM and BPO
definitions. Each area must be assessed and improved in order to reach business
process maturity. It turned out that some BPMMs measure BPM maturity, by
addressing the first four capability areas, whereas others measure BPO maturity, by
also addressing the cultural and structural capability areas [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
    </sec>
    <sec id="sec-3">
      <title>Methodology</title>
      <p>4.1</p>
      <p>BPMM Sample (N=69)
The research scope was set to generic business processes. It excludes BPMMs
addressing specific process types, such as in the initial software engineering maturity
models. However, models that integrate various specific BPMMs were withheld to
represent those specific topics. Also maturity models for supply chains and
collaboration processes were selected to study cross-organizational value chains.</p>
      <p>Data was collected during the second quarter of 2010. First, we searched for
articles in academic databases and search engines on the Internet by using the
combined keywords of ‘process’ and ‘maturity’. Secondly, we traced the references in
the identified articles to get access to other relevant sources.</p>
      <p>We acknowledge some restrictions regarding the accessibility of articles (in Ghent
University engines), the language (English, Dutch, French or German), and the
keywords. Notwithstanding these limitations, the technique turned out to be fruitful in
terms of the number of maturity models identified.
4.2</p>
      <p>
        Content Analysis
Due to the lack of a Meta theory on BPMM designs, the variables within each design
element of Table 1 were primarily identified by the ‘Grounded Theory’ [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ], which
systematically generates: (1) ‘codes’, i.e. BPMM attributes or variable values, (2)
‘concepts’, i.e. variables, (3) ‘categories’, i.e. design elements to group variables, and
(4) a ‘theory’, i.e. a comparative framework. The successive coding stages were:
initial (open) coding: we read the collected texts by constantly going back and
forth to compare existing BPMM designs. Hence, we identified possible attributes
and variables;
intermediate (axial) coding: the attributes and variables were rethought and linked
to the initial design elements. It resulted in the variables to be included in the
framework;
advanced (selective) coding: we reread the collected texts to encode what is
literally written in these texts to the obtained variables.
5.1
      </p>
      <p>BPMM Comparative Framework (RQ1)
The comparative framework, shown in Figure 2, was built iteratively.
(1) Assessors
(2) Assessment method
(3) Improvement method
(1.1) Assessment unit
•Numberof assessed organisations</p>
      <p>(1.2) Lead assessor
•Identity of the lead assessor
(1.3) Assessors and respondents
•(Numberof assessors)
•Functionalrole of respondents
•(Business orIT background of
respondents)
(2.1) Data collection technique
•Type of data collection techniques
•Numberof assessmentquestions
•(Assessmentduration)
•Rating scale</p>
      <p>(2.2) Calculation
•Type of maturity calculation
•Type of capability calculation</p>
      <p>(2.3) Representation
•Type of maturity representation
•Type of capability representation
(3.1) Capability areas &amp; domains
•Presence of capability areas,i.e.
clusters
•Numberof BPs</p>
      <p>(3.2) Lifecycle levels
•(Numberof maturity levels)
•(Numberof capability levels)
•Labelling of levels
•External view of levels</p>
      <p>(3.3) Architecture
•Type of architecture
•Architecture details</p>
      <p>After coding the identified variables, descriptive statistics were used to enhance our
dataset and to keep only those variables important to our questionnaire (RQ2).
Variables without fundamental differences among the collected BPMMs were
eliminated, because of less differentiating power. This applies to the number of
lifecycle levels, which was mostly three to six levels, with a mode of five levels. To
maintain the quality of the questionnaire, we also decided to eliminate all variables
with missing values on more than one third of the collected BPMMs, i.e. (1) the
number of assessors, (2) the background of respondents, and (3) the assessment
duration. All variables eliminated at this stage are italicized in Figure 2. Nonetheless,
they remain important design elements.
The final step is to transform the comparative framework into a questionnaire that
practitioners can use to select a BPMM. For this purpose, the 16 resulting variables
were reformulated into a similar number of questions, available in appendix. Their
comprehensiveness was approved by other BPM scholars within the faculty.</p>
    </sec>
    <sec id="sec-4">
      <title>Discussion</title>
      <p>We have found 16 design elements on which existing BPMMs substantially differ.
Consequently, they can be used to motivate the choice for one or another BPMM. We
deliberately excluded a discussion on the methodology and validation used to design
the particular BPMMs. Notwithstanding their relevance for BPMM credibility, such
information remains elusive in many design documents (e.g. found on websites or
white papers). However, this does not necessarily exclude rigorous research, which
makes a comparison arguable. For reasons of objectivity, the comparative framework
was restricted to the BPMM design itself.</p>
      <p>We advise organizations to choose a BPMM that best fits their needs. Therefore,
our questionnaire allows answering only those questions that are considered as
relevant by a particular organization. However, given the importance of capability
areas, we make Q11 mandatory. This implies that an organization must decide
whether to address BPM maturity, or BPO maturity. Next, further refinements can be
optionally made by answering the other 15 questions.
7</p>
    </sec>
    <sec id="sec-5">
      <title>Future Work</title>
      <p>The 16 questions will be used to create a decision table, which visually maps only the
proven BPMMs to the variables and the trade-offs of each variable (i.e. expected
efforts and benefits). Its use will be tested in real business scenarios by conducting
field studies. We will first ask practitioners to indicate which questions they consider
the most important for their organization. For instance, some organizations may prefer
a BPMM that certifies the assessed maturity level, whereas other organizations may
look for an informal and quick assessment with only a few assessment items. Based
on these answers, the decision table will select a BPMM that best fits such
requirements. Afterwards, interviews will be conducted to evaluate whether
practitioners are satisfied with the result, and whether they will use the resulting
BPMM in their organization.
8</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>Business process maturity has received a lot of attention in the business process
literature, but mainly as individual maturity models. To our knowledge, no
comprehensive overview currently exists. Our research tries to fill this gap by
conducting a comparative study on a sample of 69 BPMMs. This paper only focuses
on a small, though important part of that research. Particularly, it presents a
questionnaire with 16 questions, derived by a content analysis of the design
documents from the sampled BPMMs. It can be used by practitioners to select a
BPMM that best fits their organizational needs.</p>
      <p>Indeed, organizations wishing to start improving business process maturity must
first choose a BPMM out of a wide array. Since existing BPMMs vary on many
design elements, this choice may impact their further progression in business process
management. Frequently, such organizations are not aware of those differences.
Therefore, our questionnaire supports their BPMM choice by considering the most
important design differences among existing BPMMs.</p>
    </sec>
    <sec id="sec-7">
      <title>Appendix</title>
      <p>Q8. Idem Q7, but for capability levels (applicable if Q16: continuous architecture)</p>
      <p>Q10. Idem Q9, but for capability levels (applicable if Q16: continuous architecture)
(3) Improvement method
(3.1) Capability areas and domains
Q11. Which capability areas must be primarily assessed and improved?</p>
      <p>BPM maturity, i.e. primarily focusing on business process modeling, deployment,
optimization and management (e.g. for team initiatives)
BPO maturity, i.e. combining BPM maturity with a process-oriented culture and structure
(e.g. for top management initiatives)
Q12. How many business processes must be assessed and improved? More options are
possible.</p>
      <p>One, i.e. a single business process or sub process
More, i.e. more than one, but not all business processes. Assessment questions deal with a
particular business domain or value chain and their (sub) processes
All, i.e. all business processes in the involved organization(s) or supply chain. Assessment
questions focus on how the organizations deal with business processes in general
(3.2) Lifecycle levels
Q13. What must the labels of the lifecycles indicate? More options are possible.</p>
      <p>Business process optimization
E.g. from ‘initial’, to ‘managed’, ‘standardized’, ‘predictable’, and ‘innovating’ processes
Business process management
E.g. from ‘BPM initiation’, to ‘BPM evolution’, and ‘BPM mastery’
Business process integration</p>
      <p>E.g. from ‘ad hoc’, to ‘defined’, ‘linked’, ‘integrated’, and ‘extended’ processes
Q14. To which extent must the lifecycles take into account possible relationships between
individual organizations?</p>
      <p>No notion, i.e. all lifecycle levels are limited to one organization
E.g. from ‘initial’, to ‘managed’, ‘standardized’, ‘predictable’, and ‘innovating’ processes
Highest levels, i.e. as from the highest levels, external relationships are taken into account
E.g. from ‘ad hoc’, to ‘defined’, ‘linked’, ‘integrated’, and ‘extended’ processes
All levels, i.e. as from the lowest levels, external relationships are taken into account
E.g. from ‘ad hoc’, to ‘planned’, ‘aware’, and ‘reflexive’ collaboration
(3.3) Architecture
Q15. Must a road map be defined per capability area and/or overall maturity? More options
are possible.</p>
      <p>Continuous, i.e. capability levels exist and are linked to each capability area separately.</p>
      <p>Staged, i.e. maturity levels exist and are linked to all capability areas together.
Q16. How much guidance must the road map give on your journey towards higher maturity
levels and/or capability levels?</p>
      <p>Descriptive, i.e. the road map is limited to a high-level description, without criteria.
Implicit prescriptive, i.e. the road map has criteria interwoven in the assessment questions
Explicit prescriptive, i.e. the road map has a separate list of criteria</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>Van</given-names>
            <surname>Looy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>De Backer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Poels</surname>
          </string-name>
          , G.:
          <article-title>Which maturity is being measured? A classification of business process maturity models</article-title>
          .
          <source>In: 5th SIKS/BENAIS Conference on Enterprise Information Systems</source>
          , pp.
          <fpage>7</fpage>
          --
          <lpage>16</lpage>
          ,
          <string-name>
            <surname>Eindhoven</surname>
          </string-name>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Harrington</surname>
          </string-name>
          , H.J.: Process Management Excellence. Paton Press, California (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. vom Brocke, J.,
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          : Foreword. In: vom Brocke, J.,
          <string-name>
            <surname>Rosemann</surname>
          </string-name>
          , M. (eds.):
          <source>Handbook on Business Process Management 2</source>
          , pp.
          <fpage>vii</fpage>
          --ix. Springer, Berlin (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Maier</surname>
            ,
            <given-names>A.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moultrie</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clarkson</surname>
            ,
            <given-names>P.J.</given-names>
          </string-name>
          :
          <article-title>Developing Maturity Grids for Assessing Organizational Capabilities: Practitioner Guidance</article-title>
          .
          <source>In: 4th International Conference on Management Consulting</source>
          , pp.
          <fpage>1</fpage>
          --
          <lpage>29</lpage>
          , Vienna (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. OMG:
          <article-title>Business Process Maturity Model (BPMM) - Version 1</article-title>
          .
          <issue>0</issue>
          (
          <issue>1 June 2008</issue>
          ), Online available, http://www.omg.org/spec/BPMM/1.0/PDF
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Sheard</surname>
            ,
            <given-names>S.A.</given-names>
          </string-name>
          :
          <article-title>Evolution of the Frameworks Quagmire</article-title>
          .
          <source>IEEEComputer</source>
          <volume>34</volume>
          (
          <issue>7</issue>
          ),
          <fpage>96</fpage>
          --
          <lpage>98</lpage>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hüffner</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The BPM Maturity Model - Towards a Framework for Assessing the Business Process Management Maturity of Organizations</article-title>
          . GRIN,
          <string-name>
            <surname>Munich</surname>
          </string-name>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kang</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>An Overview of the Business Process Maturity Model (BPMM)</article-title>
          .
          <source>In: Advances in Web and Network Technologies, and Information Management</source>
          , pp.
          <fpage>279</fpage>
          --
          <lpage>288</lpage>
          . Springer: Heidelberg (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Maier</surname>
            ,
            <given-names>A.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moultrie</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clarkson</surname>
            ,
            <given-names>P.J.:</given-names>
          </string-name>
          <article-title>A Review of Maturity Grid based Approaches to Assessing Organizational Capabilities</article-title>
          . In: Academy of Management Annual Meeting.
          <source>California</source>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Rosemann</surname>
          </string-name>
          , M.,
          <string-name>
            <surname>de Bruin</surname>
          </string-name>
          , T.:
          <article-title>Application of a Holistic Model for Determining BPM Maturity</article-title>
          .
          <source>BPTrends (February</source>
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Tapia</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          et al.:
          <article-title>Towards a Business-IT Alignment Maturity Model for Collaborative Networked Organizations</article-title>
          . In: 12th International EDOC conference, pp.
          <fpage>70</fpage>
          --
          <lpage>81</lpage>
          ,
          <string-name>
            <surname>Munich</surname>
          </string-name>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knackstedt</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pöppelbuss</surname>
          </string-name>
          , J.:
          <article-title>Developing Maturity Models for IT Management - A Procedure Model and its Application</article-title>
          .
          <source>Business &amp; Information Systems Engineering</source>
          <volume>1</volume>
          , pp.
          <fpage>213</fpage>
          --
          <lpage>222</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13. de Bruin, T. et al. :
          <article-title>Understanding the Main Phases of developing a Maturity Assessment Model</article-title>
          .
          <source>In: 16th Australasian Conference on Information Systems</source>
          , pp.
          <fpage>1</fpage>
          --
          <lpage>10</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Mettler</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rohner</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Situational Maturity Models as Instrumental Artifacts for Organizational Design</article-title>
          . In: 4th International Conference on DESRIST, pp.
          <fpage>1</fpage>
          --
          <lpage>9</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. van Steenbergen,
          <string-name>
            <surname>M.</surname>
          </string-name>
          et al.:
          <article-title>The Design of Focus Area Maturity Models</article-title>
          .
          <source>In: 5th International Conference on DESRIST</source>
          , pp.
          <fpage>317</fpage>
          --
          <lpage>332</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. ISO/IEC: Information Technology -
          <source>Process Assessment - Part 7: Assessment of Organizational Maturity - ISO/IEC TR 15504-7</source>
          :2008(E). ISO/IEC, Geneva (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Hammer</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The Process Audit</article-title>
          .
          <source>Harvard Business Review (April)</source>
          ,
          <fpage>111</fpage>
          --
          <lpage>123</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>McCormack</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Supply Chain Management Maturity</article-title>
          . In: McCormack,
          <string-name>
            <surname>K.</surname>
          </string-name>
          (ed.)
          <source>Business Process Maturity. Theory and Application</source>
          , pp.
          <fpage>73</fpage>
          --
          <lpage>103</lpage>
          . Booksurge Publishing, South Carolina (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Van Looy</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Backer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poels</surname>
          </string-name>
          , G.:
          <article-title>Defining Business Process Maturity. A Journey towards Excellence</article-title>
          .
          <source>FEB Working Paper</source>
          <year>2011</year>
          /725. Ghent University, Ghent (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          : Business Process Management. Springer, Berlin (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Gillot</surname>
            ,
            <given-names>J.-N.:</given-names>
          </string-name>
          <article-title>The Complete Guide to Business Process Management</article-title>
          . Booksurge Publishing, South Carolina (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Gulledge</surname>
            Jr,
            <given-names>T.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sommer</surname>
            ,
            <given-names>R.A.</given-names>
          </string-name>
          :
          <article-title>Business Process Management: Public Sector Implications</article-title>
          .
          <source>Business Process Management Journal</source>
          <volume>8</volume>
          (
          <issue>4</issue>
          ),
          <fpage>364</fpage>
          --
          <lpage>376</lpage>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>McCormack</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johnson</surname>
          </string-name>
          , W.C.:
          <article-title>Business Process Orientation: Gaining the e-Business Competitive Advantage</article-title>
          . St. Lucie Press, Florida (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>McCormack</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Introduction to the Theory of Business Process Orientation</article-title>
          . In: McCormack,
          <string-name>
            <surname>K.</surname>
          </string-name>
          (ed.)
          <source>Business Process Maturity. Theory and Application</source>
          , pp.
          <fpage>1</fpage>
          --
          <lpage>18</lpage>
          . Booksurge Publishing, South Carolina (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Glaser</surname>
            ,
            <given-names>B.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Strauss</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          :
          <article-title>The Discovery of Grounded Theory: Strategies for Qualitative Research</article-title>
          . Transaction Publishers, New Jersey (
          <year>1967</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          <source>(2</source>
          .3) Representation
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          Q9.
          <article-title>If maturity levels are applicable (Q16: staged architecture), how must the calculated maturity level be displayed? More options are possible</article-title>
          .
          <source>Textually</source>
          (e.g. '
          <article-title>defined' or 'quantitatively managed') Numerically (e.g. 3, or 3.7, or 67%) Graphically Matrix,i.e.table with questions in the rows, levels in the columns, explanations in the cells</article-title>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>