Project Management

3T has developed a technique derived from IBM’s Joint Application Development (JAD) called Joint Information Systems Requirements (JISR). This technique is used to define the requirements of operational systems that will help meet real information needs. As a team, the users and data processing personnel participate in an intensive planning and an intensive requirements session under the guidance and facilitation of an experienced JISR leader. Using a step-by-step logical approach and tailored material, the leader guides the group through definition of a system, which meets the requirements of a division, department or area. A JISR has three basic objectives:

To develop an information baseline

• An information baseline is a document, which states the purpose, defines the scope, summarizes the business objectives, and lists the assumptions and constraints concerning the application. It specifies what processes are to be handled in each of the JISR sessions.

To obtain management direction and commitment

• Because the JISR can change the way business is conducted, management must make a commitment to the process. Management’s commitment is also required because the JISR sessions require a great deal of participant time.

To identify the current and new business requirements and relate these requirements to the user areas.

The JISR provides an organized method for gathering and documenting the information necessary to produce a Requirements Document. The JISR also provides a basis to estimate, plan, and schedule JAD (Joint Application Design) Sessions.

To accomplish these objectives, a JISR often includes the following elements:

1. Kickoff with a presentation by the executive sponsor Detailed agenda for the JISR sessions, identifying the participants and specifying their responsibilities for these sessions
2. Overview of the JISR process
3. Definition of the project scope and business objectives
4. Documentation of the business flow and procedures bb
5. Specification of overall system requirements
6. Identification of the number of screens, reports and interfaces for each Business Procedure System constraints, assumptions and priorities