 Stage SPA00 - Plan and Activate
Stage SRP00 - Release Planning
Stage SRQ00 - Requirements Definition
Stage SFA00 - Functional Analysis & Design
Stage STA00 - Technical Analysis & Design
Stage SCF00 - Configuration
Stage SDM00 - Data Migration
Stage STS00 - Testing
Stage SDP00 - Deployment
Stage SUT00 - User Training
Stage SCE00 - Control and End
Description
The management of report/ratio of customer (CRM) is an approach with multiple facets to improve a of the 'businesses of S by the successful acquisition and the conservation of a selected user base. CRM surrounds more than one technical solution. Before applying any kind of request to automate and improve the report/ratio of handling customer, an organization must comprise its tender of customer and define a strategy to change the manner that it leads businesses so that it becomes customer-centered. It must also prepare its personnel for the cultural change while resulting from their approaches to treat the exits related to the customer (for example, the center of telephone attention and the representatives of sales must learn from new manners of the interaction with customers). In other words, a strategy of CRM and an initiative of promptitude (C. - with-D., evaluation of CRM) must initially take place if the execution of a technical solution of CRM is to be succeeded.
This process introduces James Martin + Co 'approach recommended by S to apply the application of company of Siebel in an organization. It is a directive of project to adapt to the customer requirements and to apply the package of Siebel to address the organization 'conditions of S CRM. The range of the process does not include to evaluate an organization the 'promptitude of S for CRM. A complete evaluation of CRM should be already led to determine the organization 'reasons of S to put in application CRM and which kinds of functionality of application the best service the organization by achieving its goals to improve of the relations of customer. The strategic decision to apply CRM using Siebel as technical solution should be made before launching a project based on this process.
In order to include/understand and exploit the many devices of the application of company of Siebel and to control complexities to apply a technical software package, all the members of the team of project of execution (organization including customer 'of the members of the team of project of S) should undergo the formation of applications of company of Siebel. This process supposes that all the members of the team of project have an arrangement of work of the glance, feels, and functionality of the application of Siebel and is with the current of the terminology of Siebel. The suitable matters of class include using the applications of company of Siebel, the administration of administration of application, of marketing, the administration of service, the administration of synchronization, and the configuration and personalization.
The following stages of development comprise this process:
Release planning
Definition of conditions
Analyzes functional and design
Analyzes and design techniques
Configuration
Transfer of information
Test
Deployment
Training of the users
Moreover, there are two stages of management of the projects which can be employed like guides institute, monitor and conclude the project:
Envisage and activate
Order and end
The stages of development are described below.
Release planning
In this stage the project managers confer with the organization the 'management of S to determine what a little the functionality with elevated level should be application in the application of Siebel to fulfill the preset requirements of businesses of CRM. The conditions are used as means of determining which low modules and of expansion of the application of company of Siebel will be applied, and the range of the project is placed. The modules of Siebel and the software third of support are bought. Moreover, the development. production, formation, and of the environments of test are specified for the calculation of the costs, and the waiters and the work stations necessary orders for the development and the test environments.
At the end of this stage, the project managers should have an arrangement with elevated level of the functionality envisaged of the system, its architectural complexities, and its interfaces to other systems and projects, benefitting from the overlapping with other projects of as of the perspective MAJORITY from components administrative, operational, social, and techniques of integration of project. This arrangement is formulated in terms of solution suggested of Siebel which specifies the critical components of application and considers architecture technical required for its execution. The corresponding strategy of release is then defined, that the details envisaged releases, functionality to be included, of the iterations, the chronologies, the important service provideds and the dependences on other projects.
The strategy of release should be logical roadmaps for the delivery by increase in the functionality to the organization with the 'users of S. It should take into account how the system of Siebel will be connected by interface to the existing databases and the systems as how it can advantageously carry out or be carried out by other projects being led within the company. A strategy of release should define a delivery by increase such as the hasty releases constitute prototypes of user interface and functionality of application, whereas the posterior releases successively incorporate more of the real data of company and connect more with current systems (C. - with-D., evolve to entirely - the release of the functional and final production).
The goal of any strategy of release should be to provide the news or additional functionality of application to the users within four to six weeks of starting of project or as of the delivery of the preceding release. Part of the effort of planning of release should thus be to prescribe a minimum level of the functionality which can normally be provided in this calendar, and the additional following releases necessary of the full functionality of the delivery, including integration with other systems and points of emission of data of external on a graduated program. The strategy of release should also consider the number of geographical places and User groups to which the application of Siebel will be finally deployed. A release of the final production is typically unrolled with a specific group of users initially, then unrolled with the following groups of users on a program envisaged.
The strategy of release will be incorporated in the plan of management of projects (PMP). The PMP, by need, change while the arrangement of the particular conditions of businesses is refined, and as an element of the evaluation of follow-up after each segment by increase is unrolled with the users and feedback was captured. It is an important tool of communication which should be used for councils of team responsible for the project and to address hopes of user.
The formation of Siebel for the team responsible for the project should normally be led to coincide with the beginning of this stage (see the plan and activate the stage).
Definition of conditions
During the stage of planning of release, a strategy with elevated level of release specified which components of application of Siebel would be applied to reach the company 'goals of S CRM. The goal of the stage of definition of conditions is to make sure of the users with which functionality they expect and would like application of Siebel in order to employ it to complete their respective work and to achieve these goals of company. By analyzing the current systems and the documentation of businesses and by leading interviews with directors, users and engineering teams of infrastructure, the team responsible for the project develops an arrangement in the way in which the businesses function and her infrastructure of support.
The principal tool here are businesses of Siebel and conditions of report which must be solicited various types of users. The businesses and the conditions of report (which are requests for functionality) are analyzed the feasibility, the cost, and execution favours it, and the conditions are given the priority in the definition of conditions, a complete checklist against which the design and the configuration of application can be evaluated. Principal information on the basis of user and the structure of organization is as well factorized under the conditions; this information is instrumental in the functional design and the following configuration of the application.
The part of strategy of release of the plan of management of the projects is updated according to the definition of conditions.
Analyzes functional and design
This stage is concentrated on analyzing the functional data and conditions and downwards dividing them into components to create stable functional specifications of which to lead the configuration work. Personalization to exist vanilla given of Siebel and objects of presentation is conceived, including identifying prolongations with the elements of standard data of Siebel and changes with the basic tables of data of Siebel of target to apply the specific functionality.
In this stage you identify the logical elements of data of the businesses and the actions of user on these objects which must lead the application of Siebel so that the user interface can be conceived consequently. The objects of layer of presentation which make it possible users to reach the fundamental data and the possibilities for the access are identified. The functional specifications produced by this stage specify what follows:
- Business Objects to be used and so modified vanilla or new created
- Components of businesses to be used and so modified vanilla or new created
- The transactions carried out on Business Objects
- Seen to reach each screen (an object of businesses is represented by a screen)
- Applet and reports/ratios which constitute each sight
- Drill-towards bottom bonds between the sights
- Classes of visibility for each sight
It is imperative to confer with the users representative in the development of all the components of user interface, to make sure that the final request will be accepted by the base of users. The users are the principal people with which the needs for businesses must be satisfied by the new system, thus the system must provide the functionality which they owe and are easy and comfortable so that they learn and employ. More users are implied in the analysis and the systems design, more they will come from there to once accept the system it is configured and deployed, and less must remake headaches for the teams of design and development at the end. The user's needs lead the design of the flows of screen, the provisions of screen, and other principal elements of user interface of the application of Siebel to apply the functionality suggested.
Analyzes and design techniques
The goal of this stage is to identify the components and the conditions of configuration of the technical of material/software architecture of supporting the users of the application of Siebel, with the attention with the planning of capacity for increasing volumes of user and transaction. The technical architecture which is necessary specifically to run the application of Siebel and the total technical architecture to which the application of Siebel is connected must be detailed. After specific architecture completely reviewed, the components of software material/are obtained.
Configuration
During the stage of configuration, the application made on ordering of company of Siebel is configured based on the functional specifications (of design). Although the characteristics of design already received the approval of user, it is important to make as well take part users in the real activities of configuration, to ensure their satisfaction with the glance and feeling of the application because it is transformed specifications of design to a real and functional system. The temporary configurations will be prototypes of the functional application. The finished product of the iterative cycle of configuration is the configured application which is quality reviewed and prepared for the deployment.
In the stage of configuration the data and objects of layer of presentation are configured, the basic prolongations of data are applied, and of the manuscripts of Siebel VB are developed to carry out any special functionality necessary, the release reviewed for stability and quality before being examined by users (the test of acceptance by the users is covered in another stage). After the users examined the release, of the requests for change are evaluated and retroacted in the iterative cycle of release consequently.
Once the final release was configured, the system reviewed for the promptitude of production, for deployment. Moreover, of the materials of support are developed to be exerted and of the operations of guide and to support the personnel and to orchestrate the deployment.
The configuration uses a fast approach of the development of applications (rad) to provide the multiple successive prototypes of the application of Siebel, based on the received written characteristics of the conditions of businesses collected at the meetings of hearth of user carried out in the first weeks of the project and the practices renowned by industry. The representatives of user want the test of test each prototype and in their turn will provide immediate feedback on the suggested changes. These requests for change will be given the priority by range, importance, the establishment of the program and budget, and will be evaluated by the team responsible for the project and the organization of customer for incorporation in the following releases.
Transfer of information
The transfer of information is the whole of procedures to enter of the data of the systems of source Siebel. It is made for the systems that Siebel replaces and for the systems to which Siebel will be connected by interface on a continuous basis. It is an iterative activity which occurs at the same time as the configuration.
This stage implies to acquire the discs of source data external and to make sure that the data are clean and format-compatible with the low format of table of Siebel. The procedures automated required to charge information with the systems of source in the database of Siebel are established. The data are then extracted starting from the systems of source, are cleaned, charged in the Tables of interface, and then charged by EIM in the coffee tables. The routines of transfer of information should be completely examined. The activity of load of data can function via the batch processings and can be carried out repeatedly until all the data are charged successfully. The routines for data entering Siebel manually should be conceived and be led where necessary as well.
Test
The goal of this stage is to carry out the test of acceptance by the users (UAT) and the test of execution of system on the configured application of Siebel.
Develop a plan of UAT and the scenarios of case of test to guide a selected group of principal users by examining the user interface and the functionality of the application of Siebel. It can be useful to specify what a little the data to be introduced into the cases of test (for example, certain ranges of the values). The scenarios of case of test should be defined for all the conditions of test and include the entry, the required actions of user, and the results envisaged. The test of acceptance by the users should be addressed to all the user profiles (for example, support of sales, with sales representing, with business manager, director of sales). The various roles of user should have various rights of access and see various sights, and these differentials should be checked by the test. The plan should specify by branch of industry the users who will examine the application and the program for the test, fascinating in consideration of the constraints of establishment of the program.
Develop a plan and the manuscripts of SystemTest to examine the total handling of execution, functionality, speed and capacity of the application of Siebel in the states of user multiple, connected and outside. (An automated tool can be used for this type of test.) The manuscripts of test should make it possible testers to check:
- acceptable speed by carrying out transactions
- production of the results envisaged of transaction
- remote users 'synchronization and initialization
- remote users 'visibility
- execution of work station of office
Install and configure the environment of test and carry out the tests according to the plans of test. Note: The environment of test can also be employed for the training of user, although a separate environment of formation can be installed so feasible according to the needs and the characteristics of project.
Deployment
In this stage the application of Siebel is unrolled to the base of users. Unfolding should at the same time surround a user group, according to the strategy of release. The waiter of production is charged with the parameters, the systems of interface are supported, the configured application is deployed, and the functions of support are installed to support the system lately deployed,
The final stage in unfolding is to lead sessions of follow-up to obtain the feedback of the users on their reactions to the system lately deployed of Siebel. Evaluate the release up to what point answered hopes of user and measured until the promises of delivery made in the strategy of release and documents the feedback of user. Re-examine the results of unfolding and compare them with the original strategy of release and modify the strategy of release consequently. In conclusion, obtain the end of formal connection of the executive silent partner to carry out the next release of the application.
Training of the users
It is essential with the success of the new system of Siebel to train users of businesses in his operation and to train the personnel of support of system (such as the personnel of service PLEASE) in the exploitation and of the activities of the system related to its installation, displacement, adjustment and interaction with other systems. Moreover, it can be necessary to develop new procedures, policies, descriptions of the functions, competences, incentives, etc to facilitate the necessary cultural change to apply and to employ the application of Siebel. The principal activities in this stage include:
- You with the cultural changes Prepare
- Create the training program
- Learn the businesses and the application
- Develop the equipment for the formation
- Training of the users of control
- Evaluate the study
Maintain in the spirit that the changes inherent in the exits above can be met resistance. Consequently, the introduction of the application of Siebel must be made in a significant way. Providing incentives, the encouragement, and the support is principal to the people of assistance making the modifications necessary in the manner that they complete their work.
|
|
