Knowledge Sharing Pattern Language


Pattern

KSP13
Quickly Made

Dimensions and Knowledge Flow:
 


I2
Knowledge Sharing
in an Organization

 


Work Results
L1 Project Establishment
 

Project
Manager  

<--- 

Organization

   

Problem Time available is very limited to have the work results implemented and having the defined level of quality.
 
Initial Context Some earlier similar kind of work results exist. A Reuse Approach (KSP26) has been defined and initiated.
 
Roles

A Project Manager defining (intermediate) work results. Organization represented by a person being the named owner for the reusable assets.
 

Forces In most of the customer projects, the time-to-market is very critical. If, in such a time pressure, every work result is made "from scratch" there will normally not be adequate time for testing the work results. These together make it very reasonable to reuse earlier work results when possible. This can be done by reusing earlier ones or buying some produced by others. IPR related matters, however, must be very well considered.
 
Solution
 

To use existing work results:
  1. When defining required work results check for existing: in the organization and external ones.
  2. Maintain the Assets. Support projects how to utilize the existing assets. Study needs and decide maintenance and other activities.
  3. Check IPR and Applicability. Check applicability of the potential assets. Check the IPR situation (availability for the project, possible needs for protecting own IPRs).
  4. Check the terms of use and use the selected assets according to the terms.
  5. Suggest (and study) changes. If changes are implemented to selected assets, check if those should also be implemented to the reusable assets.
  6. Study and Update Changes. Study suggested changes and decide possible actions.
     
Resulting Context Shortened time-to-market and through earlier tested work results even better quality compared to starting from scratch.
 
Instances

To be used always when defining work results. Check if it is possible to reuse something.

One potential pitfall is reuse because of reuse and not because of business or effectivity reasons. This could lead to a situation where efforts are taken to establish reusable assets that will not have adequate return of investment.
 

Process Connection Software engineering
 

Home
Catalog

Last changes at 19th January 2008