Desktop Transformation - high-level project plan

10:17 PM
Desktop Transformation - high-level project plan -

Evaluation of Desktop Transformation (DTA) is part of the overall desktop transformation model (DTM) providing clear guidance on how to turn "Wow" in "How." during this series of blog posts, I discussed the seven key phases that make up the DTA. And in the last blog post in this series, it's time to discuss the final stage of the DTA:

  1. Define business priorities
  2. Application Evaluation
  3. user Segmentation
  4. capacity assessment
  5. high-level design
  6. transformation office Roadmap
  7. project plan senior

now that you're almost ready to present your key results for the project developer, you should develop a high-level project plan so that you are ready to discuss time and resources. Make sure you keep things in perspective. - Want to have a good overview in place, but I would not spend too much time mapping out your plan that you will not have enough details at this stage to be super accurate

so what should you include? The high-level project plan should bring the previous six phases together in a clear strategy office processing. Treat each user group as a separate project and order according to priorities established during the stage of the project roadmap. This will help ensure that the company receives the maximum value for their investment as soon as possible.

I like to create two different graphs to describe the high level of the proposed plan. The first provides a high level overview that is useful for presentations and high-level discussions. The second is a standard table glove provides an additional level of detail that I find useful in justifying resource requirements. If you do not want to reinvent the wheel, and why should you, see Justin Zacks blog on how you can use the desktop processing accelerator to create the project plan for you. There are no hard and fast rule to estimate the duration of each phase will be all down to the complexity of the environment, skills involved and the scale of the environment. I've provided samples of each table below.

Once I created my maps and feel happy with the estimates, I'll run through them again and make a list of requirements that must be in place for each key date. This is particularly important in a large corporate environment where the implementation of these activities can take a very long time. You'd be surprised at the frequency of delayed projects because this milestone has been missed. Beware of the following five prerequisites:

  1. address key risks identified in the capacity assessment prior to the construction phase
  2. Make sure your hardware , network, server. Virtualization, Active Directory (services, policy statements, OU structure), the basic requirements and data storage are in place before the start of the construction phase.
  3. licenses should ideally be purchased before the start of the construction phase.
  4. training Schedule for the support staff before the start of the implementation phase.
  5. Many people underestimate the time required to package applications. Make sure you start this process early enough so that applications can be fully verified during the test phase.

My first post on the DTA, I mentioned that there were four key issues that always get asked at the beginning of any transformation project. By following the guidelines in this blog series, you should now have a good understanding of what is required to respond. Here is a summary:?

  1. What should I do first The high-level project plan prioritizes the rehabilitation of the main risks identified in the capacity assessment. It also uses the results of the Roadmap Desktop Transformation to prioritize the design, construction and testing phases for each group of identified users.
  2. Will it work in my environment? The capacity assessment examines the existing environment to identify gaps and risks, such as the lack of data center space, insufficient bandwidth or sets of missing skills within the team Support.
  3. How much it cost? overall costs can be calculated on the basis of corrective actions identified during the assessment of capacity, infrastructure identified in the high-level design and the resources requested in the high-level project plan.
  4. How long will it take? The high-level project plan will provide a time estimate for each user group by project phase.

I hope you have found this series of informative blog posts. If you have any questions or suggested topics for future blog posts, leave please comment below.

If you want to know more about the desktop transformation model, why not check out the five parts in small desktop transformation on groups at Citrix Synergy San Francisco May 10 e

Here are the details:

SYN131 - Start your desktop transformation journey with Citrix Consulting best practices

10 May 11:30 to 12:15

  • Overview of desktop transformation methodology
  • best practices and advice on proces user segmentation
  • How to succeed by using tools of Citrix Consulting

SYN139 - successful design office processing with Citrix Consulting best practices

May 10, 2:00 p.m. to 14: 45

  • A modular architecture that will accommodate growth
  • Best practices for the delivery of the image and office design
  • development of a "basket" for the necessary equipment

SYN133 - Design office processing user experience with Citrix best practices Council

May 10, 15: 00-15h45

  • Provide personalized environment through the use of profiles and personal vDisk
  • Alignment of the safety functions with the requirements of the user segment
  • Optimizing Citrix HDX technology for fast or difficult networks

SYN135 - Go live with your desktop transformation project with Citrix Consulting best practices

May 10th, 16: 00- 4:45 p.m.

  • validation of the solution with test cases
  • Recommendations for the development of a pilot program
  • integration Guidelines additional user segments

SYN137 - Keep your office processing environment works well with Citrix Consulting best practices

May 10, 17: 00-to-17: 45

  • operating Guidelines for an office environment transformed
  • tools to help automate and simplify ongoing maintenance
  • basic troubleshooting tips to track down the root cause of a problem

I hope to see you there

Andy Baker - Architect
Worldwide Consulting
Desktop Team & Applications
Manual Virtual Desktop
Accelerator Project
Follow @CTXConsulting

Previous
Next Post »
0 Komentar