CFP - Knowledge Management for Agile Processes

I spotted this post on the Scrum Development list and thought it worthy of reposting here.



1st Workshop on

Knowledge Management for Distributed Agile Processes:
Models, Techniques, and Infrastructure
(KMDAP '03)

for the

Twelfth IEEE International Workshops on Enabling Technologies:
Infrastructure for Collaborative Enterprises (WET ICE '03).

June 9-11, 2003, University of Linz, Linz, Austria

Up-to-date information on the workshop can be found at

Workshop Description

Knowledge Management (KM) is currently receiving increasing attention in
diverse areas such as medicine and systems engineering. Here, special focus
is put on process-oriented Knowledge Management, where abstract activity
descriptions serve as the primary means to capture, organize, and
distribute knowledge items that are relevant during individual, actual
process steps. Most approaches developed so far rely on static processes as
well as on documents indexed by formalized meta-data and additional
ontologies. However, these approaches are inadequate for highly dynamic and
volatile processes, whose steps cannot be planned in advance, and during
which new, unanticipated "knowledge needs" frequently arise. Such processes
handle mostly informal documents and rely on face-to-face communication
between participants. Typical examples of such processes occur in domains
like medical diagnostics and disaster management.

In Software Engineering, the realization that software development
processes are inherently dynamic inspired an entire new discipline focusing
on "Agile Software Development Processes". These human-centered
methodologies are being increasingly applied in the past couple of years.
However, trading off explicit knowledge captured in documentation for tacit
interpersonal knowledge poses new challenges, especially in the case of
distributed settings, where support by proper Knowledge Management
techniques is essential.

The main goals of this workshop are to bring together practitioners and
researchers from the areas of Knowledge Management and Agile Processes from
different domains to discuss the current state of ongoing research efforts
and to share their practical experiences with adaptation of modern
Knowledge Management techniques by agile teams.

Topics of Interest

Topics of interest include, but are not limited to, the following areas:

- Knowledge management support systems for agile teams
- How to remain agile while applying KM techniques relying on explicit
knowledge representation?
- KM techniques that help making processes more agile
- KM to improve agile processes (self-adaptive processes)
- Collaborative ontology construction and mediation
- Knowledge assets of agile teams
- Knowledge elicitation in distributed agile processes
- Proactive knowledge distribution
- Cooperative adaptation of knowledge in agile processes
- Managing tacit knowledge
- Inter-project knowledge integration and management
- Knowledge visualization for agile teams
- Knowledge annealing

In the context of this workshop, our notion of distribution is a wide
one, encompassing any situation where direct face-to-face communication
between (current or former) process participants is somehow inhibited.

Concerning the notion of agility, a number of interpretations have been
developed by different industries (e.g., see [2] for the Software Industry).
For the purpose of this workshop, we adopt the encompassing view from [1],
where business agility is defined as "the ability to demonstrate flexible,
efficient and swift responses to changing circumstances by maximizing
physical and human resources."


[1] Gartner UK Ltd.: "The Age of Agility", Report prepared by Gartner for
BT, July 2002


Paper Submission

Papers (maximum: 6 pages in 10-pt Times, single-spaced) can be submitted
for review in PDF or RTF format. Papers longer than 6 pages will not be

Please submit your papers via e-mail to

Harald Holz

Authors will be requested to take part in the peer review process and
will be asked to review other submissions. In order to ensure an
anonymous review process, please try to avoid including any information
in the body of the paper or references that would identify the authors or
their institutions. Instead, please provide the names and contact
information of the authors in your submission e-mail. This information can
also be added to the final camera-ready version for publication at a later


Accepted papers will be published in the post-conference proceedings
(publisher: the IEEE Computer Press). Final camera-ready copies may not
exceed six pages and must conform to the IEEE Computer Society Press
Proceedings Author Guidelines,

Each accepted paper should have at least one author register and present
the paper at WETICE-2003 to get the paper published in the Proceedings.


Important Dates

Paper submission deadline: March 7, 2003
Notification of acceptance: April 11, 2003
Final camera ready copies of accepted papers
due to IEEE: May 16, 2003
Advance registration by: May 16, 2003
Workshop: June 9-11, 2003


Workshop Location
Linz is the Upper Austrian state capital, third largest city in Austria,
and located on both sides of the Danube. For more information on Linz,
please see:

For more information on Austria, please see:


Organizing Committee

Harald Holz, University of Kaiserslautern, Germany
Grigori Melnik, University of Calgary, Canada
Martin Schaaf, University of Hildesheim, Germany


Program Committee

Klaus-Dieter Althoff, Fraunhofer Institute for Experimental Software
Engineering (IESE), Germany
Ralph Bergmann, University of Hildesheim, Germany
Ansgar Bernardi, German Research Center for Artificial Intelligence
(DFKI) GmbH, Germany
Ward Cunningham, Cunningham & Cunningham, Inc., USA
Mehmet Goeker, Kaidara Software Inc., USA
Scott Henninger, University of Nebraska-Lincoln, USA
Frank Maurer, University of Calgary, Canada
Charles Petrie, Stanford University, USA
Michael M. Richter, University of Kaiserslautern, Germany
Steffen Staab, University of Karlsruhe (TH), Germany
Laurie Williams, North Carolina State University, USA


Please contact Harald Holz ( with questions and or suggestions.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Dynamic processes

Process - A series of actions, changes, or functions bringing about a result:

When we talk about software process we implicitly (or at least I do) mean formal process. The essence of a formal process is that it is written down and followed. Of course there are a lot of processes that are informal and dependent on a person's knowledge.

Read the early post by Peter on using the FDD approach to formalize the XP process its quite interesting! He rightly concludes that XP is primarily a set of principles rather than a formal process. I feel the same about Agile Modelling, which I would rename as Principle Driven Software Development!

The problem with principles is that different people apply them in different ways and Agile Modelling is a good example where there doesnt seem to be a consensus on anything!

So I guess I have two points to make:

1. A formal process is always superior to an equally effective informal process, for the simple reason its managable and repeatable.

2. Beware - I dont have a formal process that works - masquerading as - No formal process works! - I was clued into this by the example of medical diagnostics being a highly dynamic and volatile process. It has been well established for at least 40 years that there are formal medical diagnostic processes that out perform informal medical diagnostics (by a long way)!

Which I guess brings me to a third point that formal processes lower the skill and experience level of the practioner by embedding knowledge that the practioner is not required to understand or have experience of, whereas the practioner must understand and have the experience when performing informal processes.


I Guru!


I think your last point is important.

There are those who would promote practices over process for the very reason that it highlights crasftmanship and separates the the skillful from the not-so-skillful.

There is a certain ego around "I can do it and not everyone can". This manifests itself in ways like - "the only user interface I need is the Unix command line" and "No, its not available for Windows".

Hence, there is a vocal group producing anti-process feedback. It's luddite thinking which amounts to "keep repeatability out of software - only gurus allowed".

David J. Anderson
The Webzine for Interaction Designers