Mar 04, 2021 11:38 AM
Replying to Keith Novak
...
My input is similar to Kiron's in that if you are not well versed in the IT infrastructure, you need a system architect or systems engineer to define the technical definition. As the PM, you need to translate that architecture into an actionable plan.
A couple months is very short flow to go from planning to completion. You will likely have some parts of the system definition overlapping the construction. The system definition will dictate high level WBS categories such as server room, workstations, transport elements (wiring etc.), and software.
With the high level WBS, you can scope out how long it takes to go from design through procurement and build. That will help you figure out where you need to focus immediately vs. decisions that can be put off until later.
The detailed work will probably require a lot of technical and schedule integration that will evolve as you go. Some definition may not be ready to support your schedule so do you over-design to higher capability or can you make late changes? Rooms can't be used while you have floors or ceilings open to run wires, so you may have to accommodate both the office construction and some end-user occupancy at the same time.
That is an example of where you probably have more than enough work for a technical expert working full time to lay out the system and then adapt it to fit your schedule constraints, as well as a project manager working full time to orchestrate all the moving pieces.
