TRANSLATE THIS PAGE TO... Chinese (simple)   Japanese       Dutch   French     German     Italian     Free Translation courtesy of ALS      Chinese (traditional)   Korean       Portuguese       Russian       Spanish

BUSINESS PURPOSE The purpose of this section is to provide guidance in the implementation of "PRIDE" in a company. INTRODUCTION Never underestimate the implementation of "PRIDE" since it represents a change of attitude and perspective that is uncommon in the typical programming shop. This is why we refer to it as "Software for the finest computer - the Mind." Because "PRIDE" is first and foremost a unique management philosophy, it is not installed in the same manner as hardware or computer software. We have seen many approaches to the implementation of "PRIDE" over the years; some successful, some disastrous. The disastrous implementations are those where a "Dictator" approach is taken and "PRIDE" is jammed down everyone's throat. This will only work as long as the dictator remains in power. It is typically abandoned shortly thereafter. The more successful implementations have been those where the responsibility for "PRIDE" is placed on several key people in the organization, thereby giving the appearance that "PRIDE" is the will of the company and not just one individual. STEP 1 - ESTABLISH A PROJECT The first step in installing "PRIDE" is to first establish a project for this purpose. This can either be done using an automated Project Management system or using the manual forms as included in "PRIDE"-PM. Use of a Project Management system is extremely useful for keeping the project on schedule and within costs. Key to the startup of the project is the appointment of a "PRIDE" Coordinator who will act as the Project Manager for the implementation of "PRIDE". Considerable thought should go into the selection of this person. The "PRIDE" Coordinator should be respected by the development staff as well as management; should work well with people, but more importantly; must be results oriented. STEP 2 - ESTABLISH SUPPORT TEAM A Support Team is assembled who will be assigned tasks in this project. One of the principal reasons for forming a Support Team is to share the responsibility for implementing "PRIDE" throughout the company. Again, this conveys the image that "PRIDE" is the will of the company, not just a single person. Selecting members for the Support Team is critical. During the implementation process, they will have high visibility and will become the in-house experts in the use of "PRIDE" products. As such, the persons selected must be able to speak with authority and command respect. The people typically involved in the implementation of "PRIDE" include: "PRIDE" Coordinator - the person selected for this key assignment must have a management background. Enterprise Resource Manager - this will be the person primarily concerned with "PRIDE"-EEM related matters. Systems Resource Manager - this will be the person primarily concerned with "PRIDE"-ISEM related matters. Data Resource Manager - this will be the person primarily concerned with "PRIDE"-DBEM related matters. Quality Assurance Manager - the person who will be concerned with the development and enforcement of all IRM related standards. Training Coordinator - the person who will be concerned with providing educational services for the company. Project Administrator - the person primarily responsible for installing and administering the Project Management system. Technical Librarian - the person responsible for maintaining all "PRIDE" related documentation, e.g., phase deliverables, and project documentation. This does not mean implementing "PRIDE" requires enormous resources. Depending on the "PRIDE" methodologies to be installed, certain people may not be involved. Also, some members of the team may share responsibilities (such as Project Administration/Technical Librarian). Participation in the support team is not necessarily a full time job especially if the work is evenly distributed between members of the team. It is important that a unique mix of both managers and staff from various areas participate in the Support Team in order to give the project effectiveness, credibility, and balance. Junior people may be useful for establishing the mechanics of the product, but it will require managers to set standards, promote the use of the methodologies, and handle political issues. One of the first steps by the Support Team is to become conversant in "PRIDE" themselves. This can be accomplished by reviewing the "PRIDE" documentation and by attending a "PRIDE" training course. STEP 3 - DEVISE STRATEGY In essence, the Support Team will be fulfilling the role of "Industrial Engineering" as found in a manufacturing facility. Under this scenario, they will be studying the "PRIDE" methodologies and determine: Supplemental tools and techniques to be used throughout the methodologies. From this, standards are devised. How to implement an IRM Repository, either manually or with automated assistance. How to implement a Project Management system either manually or with computer software. This includes defining standard "Indirect" and "Unavailable" assignments for posting such time. Also, the reporting cycle and the mechanisms of Project Management are defined. The necessary management infrastructure to support "PRIDE." This specifically includes the development of a Quality Assurance organization which includes the Technical Library and Project Administration functions. Training requirements - for developers, support functions, as well as management and end-users. Perhaps the biggest decision to be made at this point is an implementation strategy whereby the company either installs "PRIDE" all at once or takes an evolutionary approach where key projects are selected for the initial use of "PRIDE" (a sort of "snowball" effect). The latter approach is probably the most effective for getting started. STEP 4 - INITIATE PLAN During this stage, the Support Team will initiate the IRM Repository and Project Management system, implement the necessary support infrastructure, execute their training plan, and begin to use "PRIDE." During the first few projects, pay particular attention to how "PRIDE" is used and look for problem areas. Here, the Support Team becomes a SWAT team to correct problem areas as quickly as possible. The intent is to gain momentum and perfect the use of the product (which will become an on-going goal). After "PRIDE" is installed, encourage forums (perhaps after normal working hours) where the mechanics of "PRIDE" are discussed with the staff. Such forums promote self-improvement. Whenever you have any questions about "PRIDE" or require training, please do not hesitate to contact MBA.