3.4 How to Determine If it is Going to Work

 < Day Day Up > 



3.4 How to Determine If it is Going to Work

Having a sixth sense about such things would be great, but prescience is in short supply in this world. On the plus side, you can and must take a couple of steps to ensure that the technologists have a sound game plan. These steps are listed in Exhibit 5.

Exhibit 5: Vetting the Technology Plan

start example

  1. List target state elements.

  2. Map proposed technologies to each target state element.

  3. Familiarize yourself with proposed technologies.

  4. Review validation plan.

  5. Review risk and establish Plan Bs as required.

  6. Review potential integration issues and mitigate as required.

  7. Plan postimplementation support requirements.

  8. Review with customer and beneficiary.

  9. Submit to technology review board if required.

  10. Commence validation process; review and adjust as necessary.

end example

3.4.1 Listing Target State Elements

As the design emerges from scope analysis and the requirements definition processes, you must generate and maintain a target state document. It should list each major deliverable and, at least, the key requirements of each deliverable. You should not get too detailed; I prefer simplicity. Your target state chart is not intended to replace in-depth design documentation, but should be similar to a project billboard you use to keep people focused on the main goals. Take a moment to review Exhibit 6, which is a diluted version of one we created for a project during which we installed many technologies in a new building before moving in thousands of users.

Exhibit 6: Sample Target State Chart

start example

Deliverable

Description/Functionality

Telephony

IP Telephone

Applications

Desktop build v. 2.9, both "fat" and "thin"

Home and shared directories

Storage area network (SAN)

Application backup/archive

Daily backup of SAN using robotic tape unit

Disaster recovery

Data replicated to off-site SAN

LAN printing

IP-based, multiple LAN printers per floor

Video conferencing

IP-based, to the desktop

Mainframe printing

Print jobs rerouted to IP-LAN printers

Mainframe access

Client emulation via off-site gateways

Wireless LAN

Available Day Two[a]

[a]Day Two designates any deliverable that may be delayed.

end example



 < Day Day Up > 



Complex IT project management(c) 16 steps to success
Complex IT Project Management: 16 Steps to Success
ISBN: 0849319323
EAN: 2147483647
Year: 2004
Pages: 231
Authors: Peter Schulte

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