Chapter 10: Project Managing and Deploying an Enterprise SBC Environment


After the project plan design is complete, the implementation begins. Project management is a key element in successful execution. This chapter, while not attempting an in-depth discussion of such a large topic, covers certain elements crucial to an SBC implementation, including preparing for organizational change, executive sponsorship, project manager authority, stakeholder buy-in, project reporting and tracking, task assignment, project change control, scope creep, and timeline management. We show examples of how tools such as service-level agreements and help desk software help manage changes to the environment to enhance benefits to management and end users. We also talk about the needs for the support environment both during and after the implementation.

This chapter also covers the methodologies for migrating from a PC-based to a server-based computing environment. First, we'll review the process of setting up a proof-of-concept pilot program. We next talk about expanding the pilot to a beta in order to identify and resolve any issues that arise in a small-scale production environment. We then cover expanding the beta to an enterprisewide rollout of Terminal Services. Finally, we discuss postproduction processes of ongoing measurement and reporting, change control, upgrades, and changes to the environment.

Preparing for Organizational Change

When word of the [server-based computing] project started to spread across the company, a flood of requests for new PCs came in. The requests for new systems were threefold higher than the previous year. Some folks figured we wouldn't ask them to discard a brand new system. A letter from our CFO to all controllers in all divisions reminded them that this project was not optional and that all PC purchases would be subject to heightened scrutiny.

—Anthony Lackey, Vice President of MIS,
Chief Technology Officer, ABM Industries

In most organizations, it is difficult to successfully migrate to a server-based computing environment through mandate alone. An edict from top management is essential, but the planning team needs to supplement it with a strategy for internally selling the project as part of their overall change management plan. IT will probably have ultimate project ownership, and an IT member will probably have to take the initiative in promoting server-based computing throughout the organization. For purposes of this chapter, we will assume that the IT person leading the initiative is the CIO.

Tip

IT people often underestimate the resistance that a paradigm shift to an enterprise SBC nearly always generates.

Implementing an enterprise SBC environment does not involve a major alteration in an organization's mission statement or culture. It does, however, change to some extent the way in which employees accomplish their daily work. Planning for organizational change can address these concerns and help minimize project roadblocks. The steps for managing the change process are

  1. Establish a need and sense of urgency for implementing SBC.

  2. Create a compelling vision of the SBC environment.

  3. Recruit executive support.

  4. Carefully plan the process.

  5. Communicate to all stakeholders.

  6. Build SBC momentum and remove obstacles.

  7. Monitor the progress.

  8. Publicize early successes.

  9. Expand the SBC environment.

  10. Prepare for future SBC-enabled capabilities.

Establishing a Need for Implementing SBC

The Project Definition Document discussed in Chapter 4 should include the justifications for SBC. A sense of urgency should now be included in order to generate support. A letter from the CEO, for example, can explain the financial benefits that will accrue from SBC and consequently make it clear that this is a course of action the organization is undertaking.

Creating a Compelling Vision of the SBC Environment

While the CIO may have a vision for an organizational-wide SBC deployment, the actual implementation often unfolds over various stages. It is important to develop a vision that can be shared with management and users alike in an on-demand enterprise. The pilot and beta can be very useful in this regard. A particularly attractive advantage that can be demonstrated to both users and management is the ability to work seamlessly from home through the Internet. Users tend to get very excited by this capability because of the vastly increased flexibility it affords them. They no longer need to be constrained by physical location. Management is naturally enthusiastic as well because the productivity of their employees can significantly rise since they are no longer unable to work due to a cold or car troubles.

Recruiting Executive Support

In Chapter 4, we discussed the importance of obtaining executive sponsorship for the project. Inevitably, conflicts will arise in terms of resource availability, and even outright opposition to the project can surface. The executive sponsor must be able to step in and resolve these issues in order to keep the project on track.

In order to better facilitate organizational change, promotion of the project should be expanded to enlist the support of other top managers. The CIO should meet with the appropriate executives either in a group or individually. She should take the time to explain the server-based computing philosophy to them along with the financial and other benefits that they can expect. She should also be realistic about the challenges they can expect to face during the project implementation and the results they will see upon its completion. Her team should customize an appropriate excerpt from the project plan to hand out to these executives.

If a subscription model for SBC billing will be adopted, the CIO should explain to the executives how the program works and how it will impact their departmental budgets. She can emphasize that the IT department will utilize this model to break even but do so in a manner that enables departments to operate far more efficiently and with greater accountability than under a PC-based computing environment. The subscription-billing model for an enterprise SBC environment is discussed in Appendix D.

click to expand

Carefully Planning the Process

Chapter 4 explores the intricate technical planning recommended for an enterprise SBC deployment. It is also important to plan for handling the organizational issues identified by the feasibility committee during the organizational assessment.

IT Staff Assessment

Is the IT staff ready for server-based computing? They should be early users of the technology during the pilot phase and be convinced enough about the benefits that they are advocates themselves.

If the IT staff is used to operate in the ad hoc manner normally associated with network administration, they need to understand that server-based computing requires the rigors of mainframe shop methodology, including limited access, change control, and planning and procedures. Controls must be put into place to ensure that the IT staff will help, not hinder, the SBC implementation. If certain staff members are unwilling or unable to support the project, they should be reassigned to another support area.

Skill Levels Does the IT staff have the necessary skills to install and manage an enterprise SBC environment? They must have Windows 2003 Server expertise and experience, including the ability to do registry edits. Scripting capabilities are also a requirement for large implementations. A router expert must be available to manage large wide area networks. A skills assessment should be part of the initial project planning, and training or additional personnel obtained in order to cover the skill areas that are lacking.

IT Training What training is appropriate for the IT staff prior to implementation? A Windows Terminal Services class and MetaFrame XP class are strongly recommended. If most of the work will eventually be done internally, an advanced MetaFrame XP course is recommended as well.

Cultural Assessment

How will server-based computing be received in the organization? The design plan should be modified, where necessary, in order to ensure that the organization's cultural norms will not be a roadblock to success.

Working Environment In an environment where users commonly run similar applications and work as part of a unit, such as a bank, SBC is likely to be very well accepted. Users will immediately appreciate the higher reliability and increased flexibility that SBC enables. An engineering firm, on the other hand, with independent users accustomed to purchasing and loading their own software, will likely run into severe resistance if they try to force employees to operate only in the thin-client mode.

Remote Users Remote users tend to be very enthusiastic toward SBC because they receive access to the corporate databases and networking services they need in order to do their jobs more productively. It is crucial to provide both adequate and redundant bandwidth to prevent problems with reliability and performance that can quickly turn remote users against server-based computing.

Managers Managers, in general, tend to resist the idea of SBC until they actually use one; then they quickly become converts. They are usually impressed by the increased productivity they witness among their employees, as well as the capability for their employees to work from home. The project management team can help foster enthusiasm among the managers for SBC by showing them when the reduced corporate IT costs should be reflected on departmental bottom lines.

Political Assessment

Politics usually comes down to allocation of resources, money, power, or all three. How will the SBC project impact the profit-and-loss statements of the different departments involved? What happens to a regional IT division when the computing model switches to a centralized SBC architecture? It is important to be aware of these issues in order to take actions to minimize potential disruption to the project. Some scenarios and resolutions are described in the next section in this chapter, "Communicating to All Stakeholders."

Communicating to All Stakeholders

Communication is perhaps the biggest key to successfully managing organizational change. In addition to the executive communications mentioned previously, it is also important to educate and inform both internal IT staff and middle management as well as PC users.

IT Staff

Migrating to SBC invokes a fear on the part of IT that often significantly supersedes that of end users. PC fix-it technicians, for example, will likely see SBC as a threat to their job security. Regional IT staff will also be wary since the need for remote office support personnel usually is eliminated. The CIO must come up with a strategy that presents the project's advantages, including fewer user complaints, elimination of the majority of help desk calls, much more efficient troubleshooting, and more time for IT staff to learn new and challenging technologies to help the organization move forward.

Middle Management and PC Users

Videos can be more effective internal marketing tools than white papers. A video that presents the technology from the user's perspective can be prepared for all PC users in the company. The CEO can add legitimacy by starting the video off with a supportive introduction. The video can help with the orientation process by including footage of the Windows terminal that will be utilized and how the new desktops will look, the applications that will be available via SBC, and the process for migrating users' existing data.

Large companies may wish to create a separate video targeted specifically toward middle management. This video can focus on the high-level benefits of server-based computing. It should emphasize how removing the frustrations of PC-based computing leaves employees with more time to concentrate on their business.

Other techniques to help market the concept can include rainbow packets, at-a-glance documents for frequently asked questions, e-mail messages, and phone calls.

Caution

Do not oversell the enterprise SBC environment. Set realistic expectations. Make sure users know the benefits, but also let them know about any problems or limitations they can expect to encounter, particularly in terms of performance and reliability, during the implementation period. Remember the rule of effective selling: underpromise and over deliver.

Building SBC Momentum and Removing Obstacles

The ultimate goal of IT should be to create a buzz about the project. This can be accomplished by keeping the pilot program small and controlled, and by making sure the beta is a resounding success. Including capabilities that are either not possible, or much more difficult to accomplish, in the fat-client environment (such as effective logon from home, document collaboration, and single sign-on) helps make server-based computing particularly attractive. Improved help desk support is another SBC attribute often highly valued by users. It is important to limit the size and scope of the beta not only to ensure control, but also to help create an atmosphere of scarcity and exclusivity. The objective is to have users clamoring to be included as part of the SBC project. Limiting PC purchases before an enterprise rollout also makes users more eager to get on the server-based computing bandwagon.

Users and department heads must buy into the goals of the SBC project and understand its powerful positive implications for the organization.

Management Meetings

Hold group meetings with managers from different departments or divisions. Give them a chance to air their concerns and perspectives. Emphasize the benefits to the entire organization of implementing server-based computing. Stress that, although they may perceive that their employees have less control over their environment within SBC, managers actually now can devote time to their business rather than to managing their computing infrastructure.

While the goal for these meetings should be to provide a forum for managers to ask questions and air concerns, it should be clear that the project is going to take place. It is important to emphasize the positive benefits and develop a spirit of cooperation and enthusiasm.

Entitlement Issues

Department staff may feel that, because the money for the new system is coming out of their budget, they are entitled to their own servers. Employees, meanwhile, may feel they are entitled to their own PCs to run in fat-client mode. These perceptions need to be changed. Users need to understand the benefits that server-based computing provides to the organization as a whole. Some former capabilities, such as the ability to operate CD-ROMs, might be limited if they run in pure thin-client mode. On the other hand, users will gain computing advantages such as the ability to see their desktop from any PC or Windows terminal. Another powerful user incentive is the potential for telecommuting. Many users discover that they prefer a server-based computing environment because they experience increased reliability and performance. They also do not have to worry about causing problems by inadvertently changing their desktop. A properly configured SBC environment will limit their ability to delete icons or INI files or create other mischief.

Problems with Perception of Central IT

If the corporate network has a history of performance or reliability problems, department managers are going to be very reluctant to put all of their eggs in the corporate data center basket. To reassure them, explain the elaborate steps that are being taken to upgrade the network infrastructure and describe the policies and procedures that will result in a far more reliable network environment. Explaining the redundancy and disaster recovery capabilities of the SBC environment can help further mitigate any fears.

It is often productive to define an SLA in cooperation with the department managers in order to clarify expectations. If IT fails to meet the SLAs, the managers should have some recourse, such as credits in a bill-back situation.

Budgetary Concerns

Server-based computing, by definition, means centralized computing. Individual computing fiefdoms will disappear. You may wish to implement a billing model that charges departments for actual system usage in order to alleviate fears of arbitrary budgetary impacts. An example of such a subscription-billing model is presented in Appendix C.

Disposition Issues

If the project design plan calls for replacing certain PCs with Windows terminals, department heads may not be happy about the impact on their budgets. During this preliminary stage, discuss disposition issues and how they will impact book value. If possible, incorporate charitable deductions in order to lower the burden.

Monitoring the Progress

Constantly solicit and measure user feedback. IT can then make any adjustments necessary in order to ensure user satisfaction. This will add a great deal to the process of building a very successful enterprise SBC environment.

Publicizing Early Successes

Internal success stories should be generated about the attributes of the on-demand enterprise. The idea is to create a buzz around the organization where people are excited about, rather than resistant to, the upcoming changes. At the VA Medical Center, for example, we had a doctor thank our implementation team for making his life better because he could now access so much more of the data he needed, and he could do it much more quickly and far more easily than he could in the previous distributed PC environment.

Expanding the SBC Environment

Most organizations choose to roll out to enterprise SBC in phases. The original scope of the project is often less than a complete enterprise deployment. As the SBC phases are successfully implemented, and the user surveys show improved satisfaction with IT, the scope of the SBC environment can be expanded. Providing feedback to management about the existing and expected financial savings can help to further promote SBC expansion.

Preparing for Future SBC-Enabled Opportunities

Once the SBC environment has been expanded throughout the enterprise, the organization's IT department should run exceptionally well. Employees will have more computing capabilities than before, at a much lower IT budget, and with fewer IT personnel. The organization will also have opportunities that go beyond those that are realistic in a distributed PC environment. We discuss some of those opportunities in this book, such as business continuance, more efficient centralized storage devices, and greatly enhanced security and virus protection. But, other possibilities are now potentially available as well. For instance, a large janitorial organization might decide to have a Windows terminal manufacturer make their terminals look like time clocks in order to enable janitors to enter data right into the ERP application. A construction company might outfit foreman and inspectors with wireless tablet devices in order to have real-time information flow back and forth from the job sites. An organization concerned about ramifications from the Sarbanes-Oxley Act might introduce third-party products such as KVS, which will enable them to track and categorize all e-mail documents for quick and simple discovery.




Citrix Metaframe Access Suite for Windows Server 2003(c) The Official Guide
Citrix Access Suite 4 for Windows Server 2003: The Official Guide, Third Edition
ISBN: 0072262893
EAN: 2147483647
Year: 2003
Pages: 158

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net