| |
|
|
 |
|
|
| |
 is
getting the right people in the right place at the right time and creating
a productive and synergetic environment
for them to work. This is what we do best. Our concept is ideal for
creating system development deliverables with minimal interruption
of day-to-day operations. |
|
|
|
|
|
|
| |
|
|
| |
|
Business experts apply suitable tools and techniques to evaluate their business processes, procedures, and problems. The deliverable can be a business process reengineering initiative or a set of requirements for automation to support the existing approach.
|
|
| |
|
|
| |
|
Rules analysts extract business expertise and management decisions from business specialists. Business and system analysts evaluate the identified rules to extract the impacted business processes and required business data relationships. Potential deliverables are a compilation of current or planned business rules, a business process diagram, and a business data model with key attributes and relationships.
|
|
| |
|
|
| |
|
Data analysts identify business data entities, relationships, and attributes with the appropriate metadata based on the expertise of business specialists. These definitions should span application boundaries and organizational units. The primary deliverable will be an entity-relationship diagram with all critical attributes assigned to entities.
|
|
| |
|
|
| |
|
Process engineers work with executives and operational managers to design workflows and decision support information to optimize organizational performance. The deliverables are leveled process maps and outlines of procedural documentation.
|
|
| |
|
|
| |
|
Workflow analysts and business specialists create detailed workflow diagrams and procedures with recommended technology solutions to meet organizational goals. The deliverables can be used immediately in manual operations and may form the basis for requirement definition of automated solutions.
|
|
| |
|
|
| |
|
System and business specialists brainstorm, evaluate, and select approaches to solve business needs with minimal resource consumption. The potentially sub-optimal designs may serve as stopgap measures to buy the organization time to look for better solutions. The deliverable may be an action plan, a set of manual procedures, a series of change requests for automated systems, or any combination of the above.
|
|
| |
|
|
| |
|
Business analysts gather, evaluate, and prioritize the business requirements that are the basis of an automated system and serve to validate any solution. Business specialists at all levels of authority contribute expertise and guidance. The deliverable encompasses business, technological, financial, environmental, and regulatory requirements.
|
|
| |
|
|
| |
|
Technology experts and business specialists develop potential business solutions. Each solution represents a set of technological, environmental, and organizational constraints and tradeoff factors. Once they have selected the best option, the group can specify the details. Program-level specifications are the primary deliverable.
|
|
| |
|
|
| |
|
Business users, system developers, and quality assurance (testing) specialists develop a complete, consistent set of situations that pose business and technological risks. For each situation that requires pre-implementation validation, the group has to identify setup criteria, execution steps, and evaluation conditions. The deliverable is a set of clearly defined test cases.
|
|
| |
|
|
| |
|
Business specialists, systems developers and the appropriate levels of management develop risk-focused test plans to evaluate the selected solution. The test plans should be available before testing activities start.
|
|
|
|
|
|
|
| |
|
|
|
| |
Government rules required a client's company to provide
a service to customers to conform to deregulation
of the industry.
The CEO initiated this service as a new project with a stipulation
that the organization would comply with governmental regulations at
minimal cost to the organization. The service project spanned a variety
of organizational units. No one below the CEO had authority over all
of these areas. |
|
| |
|
|
|
| |
|
|
|
| |
In response to the CEO's request, we set up a one-day,
JAD-session qualifying meeting. The JAD facilitator (an H&A Consultant),
the business project manager, the lead system analyst, two information
systems managers, the data administrator, and a variety of representatives
from involved business areas attended the meeting. During this meeting,
our consultant led the group through a project evaluation. The group
identified a set of deliverables and developed an agenda for a two-week
JAD session with representation from all affected business areas. Following
the assignment of preparatory work, the group scheduled the JAD session
to begin in two weeks. |
|
| |
|
|
|
|
