Waching daily Mar 3 2018

In the last episode we talked about business knowledge. Remember?

What if someone arrives at your company and asks:

Where is it?

Where is this business knowledge? I want to read it.

What if?

[Giant Consulting] [features]

[Business Agility] [based on busagilitymanifesto.com] [by R. Burlton, R. Ross and J. Zachman]

[Episode 7] [Business Knowledge Management]

Ah! There's a lot of things not written anywhere.

Anyone here can understand and discuss improvements for our business.

Business knowledge must be explicit.

This means it needs to be modeled, or at least written somewhere

where people can search, read, understand, share and even update it.

Of course not all the knowledge is public

and some kind of access restrictions are required.

Damn it!

Well, at least protected our information is. No one has access to anything.

Our...

Not even us! (lol)

Our business knowledge is kept in a portal

which restricts the access for those who can read, search, validate, change...

any information available there.

Whenever the business changes business knowledge changes with it.

So, your company needs to have some kind of structure

to control this versioning.

We have it for source code. Does that fit?

We do configuration management, baselining,

source code versioning, history...

We do basically the same thing. Just not for source code only,

but for all business knowledge.

The business knowledge management needs to be done in a

specifically designed structure:

A business knowledge-base.

The knowledge base here in our company

is the brain of our old collaborators.

When we need to change anything

we ask them: what happens if we change this code?

And what if we change that? Which others will be impacted?

Usually they know how to respond it.

And if they do not know, we reverse engineer source code.

We have a knowledge base that

maintains the relationship between the various elements of our business.

Through this knowledge base it is possible to identify: by changing one component,

which other components will be affected.

Quite different. Hum?

The business knowledg- base is precisely the theme of the next episode

of our series about: Business Agility