Business Capability Maps Current Practices and Use
Business Capability Maps Current Practices and Use
net/publication/323378815
Business Capability Maps: Current Practices and Use Cases for Enterprise
Architecture Management
CITATIONS READS
8 6,847
5 authors, including:
All content following this page was uploaded by Matheus Hauder on 26 February 2018.
Page 4604
3. Research approach Both organizations were working on large
transformations within their enterprises and stated that
We conducted this research in collaboration with the BCM was being used as the central artifact to steer
two organizations. One organization is an automotive and orchestrate the EA transformation. However, they
company, headquartered in Europe with approximately also stated that definitions of concrete use cases for a
120,000 employees. The other organization is an capability-based EAM are still missing. On the basis of
insurance company, headquartered in Europe with this feedback, we sharpened our RQs and conducted a
approximately 30,000 employees. Both organizations literature review, considering various journals and
have profound knowledge about BCMs and their use in online catalogs (i.e., ScienceDirect, IEEE Xplore
EAM and assisted us in defining our research scope Digital Library, ACM Digital Library, and Google
and possible use cases. Group discussions with these Scholar). Related work about BCM is illustrated in
organizations helped us to ensure that a wide range of Section 2 while EA metrics that need to be considered
relevant use cases was considered for our expert for the use cases are shown in Section 5.
interviews. Hence, the use cases considered in our
expert interviews are based on input from research Define interview guideline and use cases: Based on
(literature review) and relevant topics from practice. our findings from the literature review and the
The evaluation of the use cases and the identification feedback from the research partners, we defined an
of current challenges and benefits of a capability-based interview guideline and use cases for the evaluation.
EAM are based on expert interviews with 25
organizations. We aimed to have intensive discussions The interview guideline is divided into three parts (1.
with practitioners who have profound knowledge about general information about interview partner and
BCMs. Thus, we used a qualitative research approach, company, 2. benefits and challenges of BCM, and 3.
rather than a quantitative one. The research took place evaluation of use cases) and follows a semi-structured
from September 2016 to June 2017 and is illustrated in approach to discuss a wide range of aspects.
Figure 2. An overview of the interview partners is
illustrated in Table 1. Table 1: Interview partners
Head Experience
ID Industry
Identify problem and motivate: In the first phase, we count (~k) EAM (yrs)
defined the scope of our research, concretized our RQs, Org.01 Insurance 30 5
and conducted a literature review. The activities were Org.02 Automotive 120 10
conducted in strong collaboration with our research Org.03 Energy 60 6
partners. We had several group discussions with Org.04 Financial Services 60 12
enterprise architects at the respective organizations. Org.05 Financial Services 13 6
Org.06 Insurance 44 8
Sep 2016
Org.07 Logistic 500 10
Identify problem • Literature review Org.08 Chemicals 65 7
& motivate • Definition of research questions
Org.09 Media 3.5 4
Oct 2016
Org.10 Chemicals 17 4
• Derive interview guideline Org.11 Telecom 225 10
Define interview Org.12 Information Tech. 380 18
• Define capability-based use cases
guideline & use
cases Org.13 Consumer Goods 57 3
Nov 2016 Org.14 Telecom. 150 25
• Conduct expert interviews
Conduct • Continuous optimization of Org.15 Insurance 10 8
interviews interview guideline and use cases Org.16 Conglomerate 350 >20
Org.17 Financial Services 6 10
Apr 2017
• Aggregation of interview results Org.18 Financial Services 0.5 3
Analyze • Identify state-of-the art usage and Org.19 Conglomerate 375 4
interviews trends of BCM in the EA practice
Org.20 Financial Services 11 16
May 2017 Org.21 Information Tech. 85 10
• Aggregation of results Org.22 Conglomerate 150 7
Report • Communication and discussion of
findings findings with interview partners Org.23 Financial Services 3.5 10
Org.24 Public Sector 1 7
Jun 2017
Figure 2: Research approach Org.25 Consumer Goods 18 6
Page 4605
Conduct
12 interviews:10We interviewed 25 organizations 7
(“Org.<number>”
10 in Table 1)
9 9from Germany and 6
6
Switzerland. The participants were identified on the
8
basis 6of contacts
4
5 from 5previous research projects
4
and 5
postings
4 on social media platforms (e.g., LinkedIn).2 2 4
4
Each 2interview lasted approximately one0hour and was
0 3
conducted via phone
Yes, Yes,
call orYes,in person.No
We onlyn/a 3
considered people for
intensive our interviews
frequently barely that had profound 2 2 2 2 2
knowledge about EAMStrategic
and stated that further insights 2
Operational
about BCM support their EAM strategy. The experts 1 1
1
received the interview guideline about one week before 0
the interview. After each interview, we reviewed our 0
interview guideline and updated our questions based on 1 2 3 4 5 6 7 8 9 10 n/a
the gathered information. Our interview partners Figure 3: Years of use of BCM
operated in various branches, which indicates that
BCMs do not have a branch focus. There are two peaks in Figure 3, one at two years of
experience, the second at seven years. The peak at two
Analyze interviews: After the completion of all years underlines that using BCMs within EAM
interviews, the gathered information was aggregated activities is still in the early stages in some
and analyzed for findings. The analysis of the organizations. The second peak at seven years can be
interview follows the matrix-based method by Webster explained by the growing popularity of the EAM
and Watson [23]. The findings were aggregated to discipline in the interviewed organizations: on average,
statistics that illustrate the general use of BCMs in the interviewed organizations have about eight years of
practice (see Section 4) and implemented use cases experience with EAM, so a considerable number of
(see Section 5). organizations introduced BCMs in their EAM activities
very quickly.
Report findings: The findings were aggregated and 92% of the interviewees stated that BCMs are used
documented in a presentation and communicated to the for strategic purposes and 76% said that they are used
interview partners. as operational decisions support. Although our results
show that BCMs serve mostly for strategic purposes,
4. Use of BCMs the statistic reveals the multifacetedness of BCMs in
organizations. A correlation between the experience
level and the type of use could not be proven.
4.1 Current use of BCM
12 7
Of the 25 surveyed organizations, 23 use BCMs. 10 6
Most of them use BCM to strengthen the 10 9 9 6
communication between the management and IT, 8 5
achieve transparency in the EA, and develop target
architectures that consider business characteristics. The 6 5 5 4
two organizations that do not use BCM provided clear 4 4
4 3
reasons: a lack of understanding and acceptance by 2 2 2 2
stakeholders and missing data. 2 2
In our interviews, we asked the participants how many 0
0 1
years they have been using BCMs and whether the
Yes, Yes, Yes, No n/a
BCM is used for strategic purposes (e.g., EA intensive frequently barely 0
investments and target architecture) or operational 1 2 3
purposes (e.g., analysis of dependencies and number of Strategic Operational
applications in each capability). Figure 4: Strategic vs. operational
Figure 3 provides an aggregated overview of the use of BCM
answers regarding the years of use. Figure 4 provides One question in the interviews asked which data are
an overview of how many organizations use BCMs for mapped to single business capabilities. On the basis of
strategic and how many do so for operational purposes. our literature review and group discussions with our
research partners, we asked about the mapping of ten
information objects illustrated in Table 2 that consider
Page 4606
architectural (e.g., applications and technologies), 4.2 Challenges of BCM
business-related (e.g., projects and business demands),
and other metrics that might affect EA decisions. The Although we outlined the benefits of BCMs for
results show that most of the interviewed organizations EAM, our results revealed the novelty of the concept.
map their applications, responsibilities, and processes Thus, we asked the respondents to describe challenges
on the BCM. Applications still have a major role that arise when defining and communicating the BCM
within architectural decisions; they are measurable and to stakeholders within the organization. Figure 6
further data objects can be assigned to these (e.g., provides an overview of the most mentioned
costs, incident tickets, and interfaces), which enable challenges. A lack of understanding is the most
the analysis of the EA from different viewpoints. The mentioned challenge (by 64% of organizations);
results also show that practitioners devote much business capabilities differ from business process
attention to assigning responsibilities, also called thinking and require a mind shift within the
capability “owner,” during the interviews. organization. Our results show that this poses a hurdle,
Some interviewees provided us with additional underpinned by missing acceptance (by 44% of
information mapped to their BCM, including capability organizations) and lack of management support (28%).
priority, strategic direction, interfaces, business Operative challenges (e.g., creation efforts) were also
organizations, business functions, and mentioned, which show that the implementation of a
locations/regions (named by three organizations). capability-based EAM calls for major efforts.
IT Business
Table 2: Information mapped to BCMs Intra
Business demands
1 2 Trainings/Wo
Yes
Business objects
Responsibilities
7
7
Technologies
Applications
No
User stories
Processes
Services
Lectu
Projects
17 n/a
Costs
16
Page 4607
5. Use Case evaluation The following enumeration provides an overview
of the additional use cases that were evaluated during
our interviews. Each use case can be illustrated on a
5.1 Overview of use cases
BCM (like Figure 7 and 8) using heat maps.
We evaluated 14 use cases on their usability. The Application extended support: Both industry
use case is described in the prepared interview partners mentioned that applications that have
guideline for the interview partners. Figure 7 and 8 already run out of support by the software vendor
illustrate two use cases (application lifecycle and produce extensive costs for extended support. A
capability spanning applications, respectively) in heat map on business capabilities indicate the
detail. All use cases assume a full mapping of amount of applications that have run out of support
applications to their supported business capabilities. (red = high, yellow = medium, green = low).
Application lifecycle: This use case addresses the Cost vs. user count ratio: In the literature, the
retirement dates of applications. The age of an number of users indicates the importance of an
application is a complexity driver for EAs (e.g., application because a failure of an application
high amount of customization and extended support might hinder users in their daily work [14], [24].
costs); thus, applications nearing retirement should Other researchers argued that the number of users
be addressed early by enterprise architects [2], [17] indicates the complexity of an application (e.g.,
[24]. Heat mapping (red, yellow, and green) in number of business requirements and incident
UseFigure
Case (01/14):
7 indicatesApplication Lifecycle
which applications call for tickets) [2], [17]. However, in this case, we evaluate
Description
furtherand Visualization
attention from a lifecycle point of view. A the number of users from a different viewpoint.
business capability that is supported by applications Applications with a low number of users but high
Capabilities with a high amount of applications with an upcoming retirement date in
thatfuture
the near lose software
may require specialsupport
attention inmight lead further
order to prevent to costs (e.g.
operating costs should be evaluated on their need.
unnecessary
because of extendedcosts due to extended support costs or
support). Decomposition can save high operating costs with a
security issues due to missing updates from small business impact. Color-coding at the
software providers. capability level indicates the ratio of operating
costs and number of users on average.
Capability < 6 months
Capability Capability
Cloud candidates: Our industry partners mentioned
5 < 1 year
Capability Capability Capability
12 < 5 years
Page 4608
Guided Research - Using Business Capability based Heat Maps © sebis 17
capability level illustrates the number of that are on extended support, on average, for each
dependencies to other business capabilities. application (percentage) within a business
capability.
Harmonization potential: Functional redundancy is
an indicator for complexity of the EA and We evaluated whether the interviewed
avoidable IT costs [17], [18]. Redundancies of organizations have already implemented (or plan on
applications within a business capability indicate implementing) the use cases and the benefit of each use
harmonization potentials. case (transparency or deriving of concrete actions). We
also asked for the feasibility of each use (effort for
IT costs: The literature already discussed intensely implementation in an EA tool, gathering information to
that the amount of IT costs (e.g., for releases, realize use cases, etc.). On the basis of the benefit and
upgrades, and operating) are a crucial factor for EA the feasibility, we calculated a benefit/feasibility rating
decisions [14], [17], [20], [24]. A heat mapping for each use case. The results are illustrated in Section
should indicate the average operating costs for each 5.2.
application within a business capability.
5.2 Implementation of use cases in practice
Projects: Our industry partners mentioned that a
mapping of running EA projects within business In every interview, we elaborated whether the
capabilities supports the long-term planning of IT interviewed organization plans to implement or has
budget and projects. A heat mapping indicates the already implemented the use cases. The results are
number of EA projects or average project costs in illustrated in Figure 9. Although the results show a
each business capability. fragmented picture, some use cases deserve higher
attention. Use cases that aim to decrease hidden
Business impact: Based on discussions with our complexity in EAs (e.g., harmonization potential and
industry partners, a measure to determine the capability spanning applications) are highly identified
business impact – or business value [16], [20] – of in EAM practice (or planned practice). Use cases that
a business capability supports the long-term support EAM decisions based on expenses (e.g.,
planning of the EA and projects. A heat mapping projects and IT costs) are also in use or planned for
indicates the importance of a business capability. implementation. The results also show that many use
cases are in the “planned” status, which proves the
Agile team organization: One industry partner novelty of capability-based EAM.
mentioned that the BCM is used in the EAM to 25 1 1 1 1 1 1 2 1 1 1 1 1 2 1
evaluate the staffing of their project teams; their
project team organization strongly aligns with agile 20 7 7
software engineering principles. The definition of 12 12 11
13
15
user stories is one essential process in their agile 15 4
16
6 18 19 19
approach. These user stories are mapped to the 21 22
22
addressed business capabilities and provide advice 10 4 6
5
as to whether a project team addresses one or 5
13 5
several business capabilities. Heat mapping 5 11
1
5
8 2 2
indicates missing or incorrect staffing within a 7 7 6
4 4 1
3 3 3 2
business capability. 0
2 1
0 0
Harmonization potential
Cloud candidates
Projects
IT costs
Application lifecycle
Business impact
Infrastr. comp.
Compliance issues
Page 4609
Two use cases (i.e., infrastructure component – high
Application Capability
extended support and agile team organization) are spanning applications
lifecycle
implemented by none of the organizations. The experts Projects
mentioned that these use cases would not bring any Cloud
Infrastr. Comp. –
benefit or new insights for EA optimization. Decisions extended support
candidates
Feasibility
impact on their EA. 4/1
3.00
3.60 6/5
7/5
3.66
The experts were asked to estimate for each use 3/5
3/2 3.30
3.87
Page 4610
In our second RQ, we evaluated which concrete use attractive in the community. Of the 25 organizations,
cases are considered by the experts as useful for EAM 23 have BCM on their EAM agenda and are planning
practice. We defined 14 use cases with two industry on implementing or have already implemented use
partners in advance and discussed their feasibility and cases for a capability-based EAM. However, the results
benefit in the interviews. Moreover, we elaborated also show that the experts face major challenges (see
which of the mentioned use cases are already Figure 6) considering organizational and conceptual
implemented, planned, or out of scope by the experts. challenges.
The results in Figure 9 show a fragmented picture; Our results also show that there are dedicated use
although some use cases reveal complexity in the EA cases that gain more attraction (e.g., capability
(e.g., capability spanning applications and spanning applications and harmonization potential)
harmonization potential), the results also show that than others (e.g., agile team organization and
some organizations are still at the very beginning applications with extended support). This positioning is
(many use cases are “planned”). However, the results based on a benefit/feasibility rating that was evaluated
of our study also show that organizations consider both for each case during the interviews.
the feasibility and benefit in their use case choice; the Our results shed light on the BCM for EAM
results in Figure 10 show that there are dedicated use research. It provides a state-of-the-art report and
cases that are feasible for implementation, bring high illustrates the current benefits and challenges. The
benefit, and raise high attraction in the EAM results can be used in practice for selection of use
community (correlation between the implementation cases. Moreover, the results act as a signal for those
plan in Figure 9 and the benefit/feasibility rating in organizations that are still evaluating whether they
Figure 10). The results also show that there are use should use BCMs in their EAM practice or not; a large
cases that are neither planned for implementation nor number of organizations already considered this
bring any benefit or are not feasible (e.g., agile team approach in their EAM. Further research should
organization and infrastructure component – extended conceptualize the heat mapping of the use cases and
support). Although the research provides further derive a clear methodology on how to define and
insights into BCM for EAM research, there are some communicate the BCM approach in large
limitations within the results. Our results provide organizations. Furthermore, clustering of organizations
transparency about challenges when defining a BCM in based on attributes, such as size, industry sector, or
large organizations, whereas clear solutions are not experience with EAM, could be evaluated to make
provided yet (e.g., methodologies and software support more precise recommendations for particular use cases.
to decrease effort). Our results do not provide any
insights on how organizations approach BCM 8. References
definition and what must be considered when starting
respective activities (e.g., how to define business [1] M. M. Al-Debei and D. Avison, “Defining the Business
capabilities, how to approach barriers of acceptance in Model in the New World of Digital Business”, in:
organizations). Moreover, the results derive and Proceedings of the 14th Americas Conference on
evaluate concrete use cases, but do not provide Information Systems (AMCIS), Toronto, Canada, 2008,
concrete information as to how heat mapping should be pp. 1–11.
conceptualized within each use case.
[2] P. Aleatrati Khosroshahi, J. Beese, and S. Aier, “What
Drives Application Portfolio Complexity?”, in: 18th
7. Conclusion IEEE Conference on Business Informatics (CBI), Paris,
France, 2016.
In this research, we aim to reveal the status of [3] P. Aleatrati Khosroshahi, M. Hauder, A.W. Schneider,
BCMs in EAM practice and to identify and evaluate and F. Matthes, ”Enterprise Architecture Management
concrete use cases for a capability-based EAM Pattern Catalog V2”, Technical Report 1.0, Technical
approach. We followed a qualitative research approach University of Munich, Germany, 2015.
and conducted expert interviews with 25 organizations
among various industries. The evaluated use cases [4] P. Aleatrati Khosroshahi, M. Hauder, and F. Matthes,
were defined in strong collaboration with two “Analyzing the Evolution and Usage of Enterprise
European-based organizations from the automotive and Architecture Management Patterns”, in: 22th Americas
the insurance industry. Each interview took Conference on Information Systems (AMCIS), San
Diego, USA, 2016.
approximately 1 hour and was conducted in person or
via telephone. Our results show that BCMs are at the
very early stages in EAM practice but are highly
Page 4611
[5] T. Barroero, G. Motta, and G. Pignatelli, “Business [15] Y. Malhotra, “Knowledge management and business
Capabilities Centric Enterprise Architecture”, in: P. model innovation”, IGI Global, Hershey, PA, USA,
Bernus, G. Doumeingts, M. Fox (Ed.), Enterprise 2001.
Architecture, Integration and Interoperability, vol. 326,
Springer, Boston, USA, 2010, pp. 32-43. [16] Microsoft Corporation, “Microsoft Motion - Heat
Mapping Tool,” 2006. Retrieved from:
[6] J. Beese, S. Aier, and R. Winter, “On the Role of http://blogs.microsoft.co.il/files/folders/2034/download.
Complexity for Guiding Enterprise Transformations”, aspx [Accessed 9 April 2017].
in: D. Aveiro, R. Pergl, M. Valenta (Ed.), Advances in [17] M. Mocker, “What is complex about 273 applications?
Enterprise Engineering IX. EEWC, Lecture Notes in Untangling application architecture complexity in a case
Business Information Processing, vol. 211, Springer, of european investment banking”, in: 42nd Hawaii
Cham, Switzerland, 2015, pp. 113-127. International Conference on System Sciences, Hawaii,
USA, 2009.
[7] D. Beimborn, S. F. Martin, and U. Homann,
“Capability-oriented modeling of the firm”, in: IPSI [18] A. W. Schneider, T. Reschenhofer, A. Schütz, and F.
Conference, Amalfi, Italy, 2005. Matthes, “Empirical Results for Application Landscape
Complexity”, in: 48th Hawaii International Conference
[8] A. Bharadwaj, O. A. El Sawy, P. A. Pavlou, and N. V. on System Sciences, Hawaii, USA, 2015.
Venkatraman, “Digital Business Strategy: Toward a
Next Generation of Insights”, MIS Quarterly, 37 (2), [19] J. Scott, A. Cullen, and M. An, “The Anatomy Of A
2013, pp. 471-482. Capability Map”, Forrester, 2010.
[9] E. Bouwers, J. Visser, and A. van Deursen, “Criteria for [20] M. Sykes and B. Clayton, “Surviving Turbulent Times:
the evaluation of implemented architectures”, in: IEEE Prioritizing IT Initiatives Using Business Architecture”,
International Conference on Software Maintenance in: Advances in Computer Science: an International
(ICSM), Software Engineering Research Group, Delft, Journal, 2012, pp. 44-50.
Netherlands, 2009, pp. 73-82.
[21] The Open Group, TOGAF Version 9.1 framework.
[10] J. P. Brits, G. Botha, and M. Herselman, “Conceptual
Framework for Modeling Business Capabilities”, in: [22] U. Weber and V. Schmidtmann, “Differentiate. Der
Proceedings of the Informing Science and IT Education neue strategische Imperativ für den CIO”, 2008.
Joint Conference, 2007, pp. 151-170.
[23] J. Webster and R. T. Watson, “Analyzing the past to
[11] A. Freitag, F. Matthes, C. Schulz, and A. Nowobilska, prepare for the future: Writing a literature review”, MIS
“A method for business capability dependency Quarterly, 26(2), 2002, pp. xiii-xxiii.
analysis”, in: International Conference on IT-enabled
Innovation in Enterprise (ICITIE), Sofia, Bulgaria, [24] F. Yilmaz, “Tool Support for Capability-Based
2011. Application Portfolio Management - Conceptualization,
Prototype Implementation, and Evaluation”, Masters
[12] W. Keller, “Using capabilities in enterprise architecture Thesis, Technical University of Munich.
management”, White Paper, Object Architects, 2009.
Page 4612