Organizational Development for Knowledge Management at Water ...

eduction, and total ownership cost. Focus on measures that correlate to related
business performance measures.
9. Training: Secure computer-training facilities to allow "hands-on" training for users.
Transformed business processes will be simulated in a training environment for user
testing and acceptance.
Key Task 1: Requirements
This task is aimed at narrowing the functional scope of the selected groupware application to
only those functions that enable the achievement of mission-related measures (that is, reduction
in cycle time). For example, given a groupware application, conduct a functional analysis of the
application. At minimum the analysis should include the function name, description and release.
List all of the functions that the groupware application is capable of performing (such as, add a
new document). This list should not include any extended or custom functionality. Focus on the
base functionality of the groupware.
Once a list has been prepared, convene the community members to review the list. Leaders
should aim at obtaining consensus over which functions meet the general requirements of the
community's needs within the first release of the KnowledgeBase. Enter 1 for ―release‖ if the
community requires the function in the first release. Enter 2 or 3, respectively, if the community
feels as though that particular function can be postponed for a later release. The community is
expected to base its functionality decisions on lessons learned and past experiences, and the
requirements of the project.
Work Product: Requirements Traceability Matrix - Excel spreadsheet containing the following
elements: REQ ID, REQUIREMENT (or Function Name), DESCRIPTION, RELEASE (version of
the implementation that will contain the corresponding function), NEW or EXISTING,
FULL/PARTIAL, COMMENTS, DOCUMENTS
Key Task 2: Inventory
The inventory offers community members the opportunity of identifying all information
associated with established business processes. With the help of a facilitator or community
leader, convene a session of community members and conduct a brainstorming session on
information that is either inputs to or outputs of the community's business processes.
Once the list has been developed, assign each member the responsibility of reviewing the
baseline list and adding information not captured during the community session. Compile the
baseline list along with the individual input from community members. This will become the
baseline inventory for the community.
Work Products: Inventory List - Excel spreadsheet containing the following elements: ASSET
ID#, NAME, DESCRIPTION, BEST PRACTICE, RECORDS MANAGEMENT META DATA
(SSIC data)
Key Task 3: Taxonomy
The objective of taxonomy building in the community is to provide an intuitive structure for users
who are interested in obtaining information from or contributing to a community's practice.
Convene the community to brainstorm a list of categories based on the prepared inventory list.
The objective of the taxonomy brainstorming session is to develop as complete a list as
possible. Disregard the length of the list. The actual list can be finalized during a separate
community session. See Taxonomy. Tip 1: Limit the final consolidated list to 9 categories. Tip
2: Limit sub categories to 3 levels.
Once the group has developed a list, distribute the list to group members and have them
conduct a personal assessment of the list. Community members add, consolidate, or
recommend deletions to the list. Community leaders will consolidate the group and individual
C-63
©2011 Water Research Foundation. ALL RIGHTS RESERVED.