Since my posts about the role of the CIO (http://leadershipinit.blogspot.com/2007/12/what-should-ceo-look-for-in-cio.html) there is an increasing body of information that points to my suggestions as being correct. While I'm generally not one to gloat, I do believe that if you're on the fence relative to the CIO question, this new information might help sway you.
Video Interview done by the WSJ "Role of the CIO"
http://link.brightcove.com/services/link/bcpid1127798163/bclid572028407/bctid1448130649
Blog entry regarding "Role of the CIO"
http://www.greenm3.com/2008/03/wsj-article-how.html
There are a large number of stories and articles about why the role of the CIO is critical, but I liked both of these because they point to combination of IT being critical and to the key qualities of a CIO.
Enjoy the reads.
Wednesday, March 19, 2008
Friday, March 7, 2008
Building a New Data Center (continued)
If you read my last post on this subject you know that we're building a fairly large new facility and we're trying to do it in a hurry.
Some of what have we done so far:
Defined the appropriate Org model with roles and responsibilities
Created a BOD & PRD (Basis of Design doc & Program Requirements Doc)
We're making excellent progress on internal project plans and contruction plans. My recommendation on Project plans is you definitely need them, just don't make them too long. For a project like this there will be an enourmous number of line items, so it's best to consolidate and or split the project so that each plan can be as focused and easy to follow as possible.
We have begun working with the Executive team to determine their requirements relative to public messaging on this new Data Center, along with any expectations they might have for Showcase or Green options.
We have our partners for construction & MEP all selected, and we've got the basics of building layout and electrical design done.
We've established our unique Tier strategy (we aren't using a standard industry Tier model it's a hybrid)
Lastly we've established what all our critical path (long lead time) items are and have factored them into the project timeline. In some cases we made pragmatic (read: less than the best) decisions in order to ensure we stay close to our original delivery schedule.
Some additional keys to consider in a project startup as big as this;
Team design; who should be on the team is more than just skill and availability, where possible you should also consider team dynamics.
Roles & Responsibilities; each of the roles in a project org should be very clearly defined and communicated to the entire team.
Budgeting; the project team must have access to the budget in order to make the appropriate decisions relative to changes in design or facility use requirements. Things can change fast with technology and when opportunity presents itself you need to be able to act fast.
Some of what have we done so far:
Defined the appropriate Org model with roles and responsibilities
Created a BOD & PRD (Basis of Design doc & Program Requirements Doc)
We're making excellent progress on internal project plans and contruction plans. My recommendation on Project plans is you definitely need them, just don't make them too long. For a project like this there will be an enourmous number of line items, so it's best to consolidate and or split the project so that each plan can be as focused and easy to follow as possible.
We have begun working with the Executive team to determine their requirements relative to public messaging on this new Data Center, along with any expectations they might have for Showcase or Green options.
We have our partners for construction & MEP all selected, and we've got the basics of building layout and electrical design done.
We've established our unique Tier strategy (we aren't using a standard industry Tier model it's a hybrid)
Lastly we've established what all our critical path (long lead time) items are and have factored them into the project timeline. In some cases we made pragmatic (read: less than the best) decisions in order to ensure we stay close to our original delivery schedule.
Some additional keys to consider in a project startup as big as this;
Team design; who should be on the team is more than just skill and availability, where possible you should also consider team dynamics.
Roles & Responsibilities; each of the roles in a project org should be very clearly defined and communicated to the entire team.
Budgeting; the project team must have access to the budget in order to make the appropriate decisions relative to changes in design or facility use requirements. Things can change fast with technology and when opportunity presents itself you need to be able to act fast.
Subscribe to:
Posts (Atom)
Posts
