Browse Prior Art Database

Project Magic

IP.com Disclosure Number: IPCOM000014501D
Original Publication Date: 2000-Oct-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 4 page(s) / 47K

Publishing Venue

IBM

Abstract

System for supporting the engagement and management of technology based training projects The system described in this disclosure addresses the need to manage large scale, technology based training projects across the full engagement lifecycle. It incorporates performance support initiatives at all points in the engagement cycle, from sales/consulting, through design, development, testing and deployment. It also supports the deployment of projects to multiple geographies teams. The system specifically supports the development methodology employed by IBM Knowledge Factory. This disclosure only discusses the methodology in passing. Problem statement

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 44% of the total text.

Page 1 of 4

Project Magic

   System for supporting the engagement and management of technology
based training projects

The system described in this disclosure addresses the need to
manage large scale, technology based training projects across the
full engagement lifecycle. It incorporates performance support
initiatives at all points in the engagement cycle, from
sales/consulting, through design, development, testing and
deployment. It also supports the deployment of projects to
multiple geographies / teams.

The system specifically supports the development methodology
employed by IBM Knowledge Factory. This disclosure only discusses
the methodology in passing.

Problem statement

The workflow cycle times for TBT development can be extensive.
While the content itself can take a considerable amount of time
to develop, tools are available to help automate development
tasks. There are no tools however capable of managing the
creative and design cycles. These cycles are affected by a number
of factors:

The gathering, confirmation and approval of content
requirements
The arrangement of this information into "instructional"
terminology
The explanation of the terminology to the project sponsor
The transmission of this to the project team
The approval of all these documents by designated approvers
The level of creativity that occurs in all of these areas

This is complicated by the fact that a number of these elements
are performed by different people with different roles (and
therefore focuses and interests). This leads to continual
confirmation of requirements, firstly with the customer, and
secondly, within the project team -- and as the information
exists in various forms (knowledge, notebooks, PC files etc),
some pieces of information are lost, reinterpreted, guessed or
lost. When this occurs there is a greater chance of producing TBT
that fails to deliver to customer expectation.

The solution

The system addresses these problems by focusing on providing
performance support across defined roles and responsibilities.
The underlying concept is to provide only the information
required by that person's role -- that is, to not inundate all

1

Page 2 of 4

users with information that is not relevant.

Roles

The system provides separate views into the database consistent
with job role. Each view allows you to create and read documents
required for the proper performance of that role. The sequence in
which documents should be created is specified by numbered action
buttons (refer to Figure 1). The documents that are created by
these buttons have built in performance support ("smart forms"),
ensuring that all required questions are asked at the relevant
time. Where answers to questions have development or design
implications, additional questions appear automatically.
Additional detail on documents is set out below.

Figure 1: Numbered action buttons

Workflow

The workflow functionality allows documents to be viewable in
other views as the engagement matures. For example, a "Learning
Requirements" document is...