Browse Prior Art Database

Just-In-Time Process Documentation Delivery

IP.com Disclosure Number: IPCOM000114569D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 4 page(s) / 113K

Publishing Venue

IBM

Related People

Hanney, LC: AUTHOR

Abstract

ISO9000 requires process documentation unless it can be demonstrated that the task is obvious. In order to meet this need, people often write process documentation which is so voluminous as to be unusable. Instead of referring to the documentation, users often 're-invent the wheel' as far as processes are concerned.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Just-In-Time Process Documentation Delivery

      ISO9000 requires process documentation unless it can be
demonstrated that the task is obvious.  In order to meet this need,
people often write process documentation which is so voluminous as to
be unusable.  Instead of referring to the documentation, users often
're-invent the wheel' as far as processes are concerned.

      Even if they are motivated to find the proper documentation, it
is often difficult to do so, and they end up giving up and managing
as best they can.

      Thus, instead of tried and  tested best of breed processes,
ad-hoc ones are generated, and this can have serious negative effects
on the quality of the product.  Furthermore, it also has negative
effects on the efficiency of the organisation, as it results in the
proliferation of processes, and new people therefore have to learn
several new processes when in an ideal world they would only have to
learn one.

      This invention applies 'Just-in-Time' stock control methods to
process documentation delivery.

      Every development project has a schedule.  The schedule says
when various team members are due to commence the required tasks.

      The schedule and the process documentation are both usually
held on-line, and can be machine processed (for example, if the
schedule is in the SuperProject Tool then it can be exported for
other processing).

The invention proposes a three-stage implementation process to ensure
use of proper processes.
  1.  A one-time effort in index-building for process documentation.
       Thus the process documentation relating to Design Inspections,
       for example, would be identified, as would the documentation
       relating to System Test.
  2.  A once-in-a schedule effort at identifying when specifically
       named tasks are to be done by each contributor.
      This would identify, for example, that John Smith is scheduled
to
       start high level design for the XYZ component on 1 November.
  3.  A once-a-day execution of a Process Progress Monitor, which
uses
       the information prepared in stages 1 & 2.
      A brief description of the logic for this monitor would be
        a.  Identify today's date
         b.  Identify the activities to start today, and the
contributors
             to those tasks
         c.  Identify the process documentation associated with the
             tasks, and EITHER
             1) Send the appropriate documentation to the
contributors or
             2) Send the contributors a note along the lines of
               "I notice you...