Master’s Thesis – Final Presentation Design, … › file › nlauwxmrz0dd ›...

Chair of Software Engineering for Business Information Systems (sebis)

Faculty of Informatics

Technische Universität München

wwwmatthes.in.tum.de

Master’s Thesis – Final Presentation

Design, Implementation and Evaluation of a

Community based Enterprise Architecture

Management Knowledge PlatformMartin Gernegroß, 09/25/2017, Munich

Introduction

▪ Motivation

▪ Fundamentals

Research Context

▪ Research Objectives and Questions

▪ Research Approach

EAM Information and Collaboration Platform

▪ Stakeholder Interviews

▪ Structure

▪ Development Approach

▪ Demonstration

Evaluation

▪ Industry Partner

▪ User Survey

Limitations

Future Work

Outline

© sebisMaster's Thesis -Final Presentation - Martin Gernegroß 2

Introduction

▪ Motivation

▪ Fundamentals

Research Context





▪ Structure


▪ Demonstration

Evaluation


▪ User Survey

Limitations

Future Work

Outline


Introduction

Situation at the industry partner today

▪ Distributed information

▪ Silo solutions for knowledge management

▪ Inefficient communication channels

▪ Hard to understand or low quality material

▪ No single point of truth for definition of terms and standards

▪ New challenges like aim for agility and lean EAM

There is a strong need for…

▪ A central “enterprise wiki” which contains relevant information for all EAM stakeholders

▪ Well structured and qualitative content

▪ Prevention / eradication of silo solutions

▪ Enhancement of community thinking and collaboration

▪ Enhancement of EAM awareness and architectural thinking


Motivation

Introduction

What is a platform?


Fundamentals

https://anemina.com/trolltunga-norwegen-bucket-list/

http://iliketowastemytime.com/swedens-draugen-oil-platform

https://www.tum.de/die-tum/aktuelles/pressemitteilungen/detail/article/33749/https://www.u-bahn-muenchen.de/netz/u6/

Introduction

What is a platform?

A knowledge platform in this context is:

A central place where employees can exchange, discuss, present, collaboratively

create, and find important know-how required for performing their daily work. It is…

• accessible for everyone,

• managed by the employees themselves,

• the single point of truth, and

• interconnected with other solutions.

Why not “Wiki”?

• Lack of social interaction

• Lack of intranet like content

• Hierarchical structure

• Industry partner: bad reputation of the term “wiki”


Fundamentals

Introduction

▪ Motivation

▪ Fundamentals

Research Context





▪ Structure


▪ Demonstration

Evaluation


▪ User Survey

Limitations

Future Work

Outline


Research Context

Research Objectives

▪ Identification of the key requirements for an EAM information and collaboration

platform

▪ Creation of a prototype to demonstrate and evaluate the suitability

Research Questions

▪ RQ1: What are the reasons for the rare use of existing knowledge management

solutions in the organization as of today?

▪ RQ2: What information must an EAM knowledge platform provide to support the

stakeholders, especially agile teams, at their work?

▪ RQ3: What is a suitable structure for the contents?

▪ RQ4: Is the proposed EAM knowledge platform a suitable solution for the EAM

community?


Research Objectives and Questions

Research Context

Design science method by Peffers et al. 2007


Research Approach

Problem

Identification &

Motivation

Define Problem

Show importance

Objectives of

the Solution

What would a

better artifact

accomplish?

Design and

Development

Artifact

Demonstration

Find a suitable

context

Use artifact to solve

problem

Evaluation

Observe how

effective, efficient

Iterate back to

design

Communication

Scholarly

publications

Professional

publications

Inte

rfa

ce

Th

eo

ry

Ho

w to

Kn

ow

led

ge

Me

tric

s, A

na

lysis

Kn

ow

led

ge

Dis

cip

lina

ry K

no

wle

dg

e

No

min

al P

roce

ss S

eq

ue

nce

Problem-

centered

Approach

Objective-

centered

Approach

Design &

Development

centered

Approach

Client/Context

Initiation

Possible Entry Points for Research

Introduction

▪ Motivation

▪ Fundamentals

Research Context





▪ Structure


▪ Demonstration

Evaluation


▪ User Survey

Limitations

Future Work

Outline




Stakeholder Interviews

4

8

5

0

2

0123456789

Satisfaction with today’s Situation

15

0

2 2

0

2

4

6

8

10

12

14

16

English German Both n/a

Platform Language

17

02

Platform operating Level

International

National

n/a

2

3

13

1

Stakeholder Role

Management

Business

Architect

DevOps

17

11

Willingness to contribute Content in Future

Yes

No

n/a

16

11

1

Stakeholder Level

Expert

Team Lead

Manager

SeniorManager


RQ1: Reasons for the rare use of existing knowledge management solutions:

▪ Too many different solutions with similar purpose

▪ Restricted access

▪ Bad search functionality

▪ Bad data or content quality

▪ Unappealing design

▪ Bad usability

▪ Missing integration

But also: Fear of sharing information to a wider audience, especially in early state




RQ2: High-level information blocks required by the stakeholders



Topic Description

„EAM for Business“ Provide easy to understand basics of EAM, like what?, how?, why? and who? Including a

glossary and FAQ.

EAM Methodology Provide the EAM methodology in a structured, easy to navigate, searchable and user centric

way (e.g.: principles, processes, templates)

EA Repository High-level entry point with all relevant instructions and direct access to respective reports

Councils Provide general information about the existing councils, their mission / objectives, criteria for

relevant projects, members, decisions etc.

Decisions Provide all relevant decisions for specific products / capabilities.

Blueprint Provide an overview of existing technologies / solutions in general and for specific use cases /

products / capabilities.

Transition EA Provide relevant information regarding up to date transition and target EAs like decisions, heat

maps and „construction sites“. E.g. based on capability map structure. Target EA

Responsibilities Provide information regarding contact persons or responsible persons, no matter which topic.

Instructions / Best

Practices / User Stories

Provide instructions and best practices for EAM relevant topics (e.g.: how to analyze the

current EA with the help of different tools)

Current Topics Provide up to date information regarding activities (e.g.: current projects, trainings) for each

department (especially EAM Governance)

Management Business

Enterprise

Architects

DevOps


RQ3: (more detailed structure during demonstration)


StructureEAM in a Nutshell

EAM Overview and

Fundamentals

EAM Best Practices

Enterprise Business and

Application Architecture

Enterprise Technology

Environment

EAM CoPs

EAM Glossary

EAM FAQs


In general, agile Scrum based approach including e.g.: User Stories, Daily

Meetings, Backlog, focus on Working Product

1. Elaborating and transferring known information, e.g.:

▪ Methodology

▪ Councils and workgroups

▪ Tools and platforms -> EAM Repository

2. Working groups were formed with relevant stakeholders to create first ideas and

content, e.g. for: EAM in a Nutshell, Stakeholder oriented pages,

Target/Transition EA, Best Practices, Blueprint

3. Provision of a place and structure for the management of CoPs to increase

awareness and popularity of the platform.


Development Approach

30 Days

1-7 Days

Product Backlog Sprint Backlog Sprint Working Product

Sprint Planning

Sprint Review &

Retrospective

Daily Scrum



Demonstration

Introduction

▪ Motivation

▪ Fundamentals

Research Context





▪ Structure


▪ Demonstration

Evaluation


▪ User Survey

Limitations

Future Work

Outline


Evaluation

Only positive feedback during the final presentation.

Furthermore, decision on continuing the development:

-> Willingness by all participants to overcome the prototypical status


Industry Partner – Final Presentation

Decision on the future of the EAM information and collaboration platform

Continue the development, focusing on the following points:

1. Development of final scope and implementation roadmap and also the positioning of the platform at BMW in common with ITPM Next

2. Define roles and administration (especially Area Owners, e.g. for “Target EA”)

o Setup of one or more work groups by motivating / convincing suitable employees

o Further elaboration of the respective content driven by the Area Owner

3. Active participation also by managers / team leads!

4. Retirement of intranet / PLAZA presences with architectural contexts and other silo solutions from EA departments

5. Active promotion

o Advertisement on the intranet, email signature, workshops, flyers / posters etc.

Cultural Change: Shaping a new culture of information sharing

Cease of Project

1. No longer support for any content / sites

2. Furthermore distributed information in separate / silo solutions

Evaluation

Furthermore, a user survey with 14 participants has been conducted


User Survey

4

41

5

User Involvement

Interviews & D/I Only Interviews

Only Design/Impl. None

2

2

9

1

0

Stakeholder Group

Management

Business

EnterpriseArchitects

DevOps

n/a

Evaluation

▪ Very positive feedback, especially regarding mission, content and structure

▪ However, criticism regarding the stakeholder oriented content


User Survey

GeneralQuestions

PlatformCharacteristics

Others

Active participation in the future

Clear mission and objectives

Suitable to achieve its goals

Potential to act as key enabler ofagile and lean EAM

Clear structure

Easy to navigate

Appealing design

Valuable content

Stakeholder specific content useful 15%

0% 20% 40% 60% 80% 100%

29%

71%

36%

43%

77%

71%

43%

31%

57%

71%

29%

36%

50%

15%

21%

57%

38%

43%

0%20%40%60%80%100%

Strongly Agree Agree Neutral Disagree Strongly Disagree

0%

28%

7%

8%

8%

16%

Introduction

▪ Motivation

▪ Fundamentals

Research Context





▪ Structure


▪ Demonstration

Evaluation


▪ User Survey

Limitations

Future Work

Outline


Limitations

▪ Just a prototype(too little content; just used actively by a small amount of employees as of today)

▪ Industry partner focus(mainly designed and developed based on the industry partner’s needs)


Introduction

▪ Motivation

▪ Fundamentals

Research Context





▪ Structure


▪ Demonstration

Evaluation


▪ User Survey

Limitations

Future Work

Outline


Future Work

▪ Active promotion(key success factor: user base; e.g.: email campaign, posters, prominent intra-net entry)

▪ More content(overcome prototypical status)

▪ Further improvement of stakeholder oriented pages(due to partially negative feedback; highly depended of previous point)

▪ Replacement of existing solutions(single point of truth; clearly communicate mission)

▪ Integration with other tools(e.g. EAM repository; automated population of KPIs -> graphs, heat-maps)

▪ Workshops / Trainings (teaching the culture of information sharing; overcome technical hurdles)


Technische Universität München

Faculty of Informatics

Chair of Software Engineering for

Business Information Systems

Boltzmannstraße 3

85748 Garching bei München

Tel +49.89.289.

Fax +49.89.289.17136

wwwmatthes.in.tum.de

Martin Gernegroß

M.Sc.

17132

[email protected]

151 2022 1028

http://wwwmatthes.in.tum.de/

Master’s Thesis – Final Presentation Design, … › file › nlauwxmrz0dd ›...

Documents

Transcript of Master’s Thesis – Final Presentation Design, … › file › nlauwxmrz0dd ›...