Meeting Report

Information
N° : 001
Participants : AHU, EFA, KPO, SPA, SWU
Redactor : AHU
Date : 29/07/2009
Length : 1h00

Topics
1 – Knowledge base needs

1 – Knowledge base needs

Questions sent before the meeting to the team leader :
- What knowledge is generated during a project ?
- What knowledge and information do we have to keep in memory ?
- What are the existing files/documents created during a project ?
- What information/knowledge do you need to understand a previous project ?
What are you looking for ?
- What are you not able to find presently ?

Those questions are judged as too wide by them, so they don’t really know what to
answer.

About knowledge generated during project, there is the using of different objects to
do the same function.

One of the problem with knowledge base and documentation could be the language,
the knowledge should be capitalized in English but most of the staff is more
comfortable with Thai.

Information and knowledge generated during project are available in different

document :
- Source code
- Customer documents
- E-mail

But most of the time the project’s documents are not up to date, several changes are
made between the beginning and the end. Mostly those change request information
can be found in e-mails.

Frontware International
One other problem is that Frontware has different customers and they all work in
different way.

Mostly there is 2 types of document for the project :

- Document who describes functionality, how it is supposed to work and what it

should be done.
- Document who describes how to do it with technical information.

There is many type of document to manage, example : video for client.

A file can be related to different project, keyword and description research is needed.

Also knowledge mapping should be usefull, who know what (skills) and who worked
on what (projects).

The knowledge base should have to include right management (access, write…).

ToDo
- Have a look at google desktop search (AHU)

Frontware International