For IT infrastructure projects, our methodology typically follows a set of phases to develop a functional specification or infrastructure architecture design that outlines the requirements or desired functionality of the environment. Subsequent project phases involve building out the environment, installing the required pieces, configuring the necessary components, migrating any legacy data, testing the new system, and training users as required to meet the requirements of the specification or design document.
IT infrastructure projects at Wadeware typically consist of the following major project phases.
Discovery
Our infrastructure consultants collaborate with each client to develop a functional specification and/or architecture design document during this phase of the project. Baseline requirements of the customer environment are typically defined during this phase. The team then submits the initial draft of the functional specification or design document to the client for approval.
Architecture
After the initial draft is approved, the development team evaluates and refines the architecture design for the project deliverables. The team adds this information to the functional specification or design document to obtain customer approval. Researched configuration requirements are documented.
Implementation Planning
After the client approves the architecture design and software requirements, our developers start building or configuring the desired functionality into an Alpha version of the environment for review. Plans for deploying and migrating the project deliverable(s) to meet the requirements of the client are also defined and documented as needed during this project phase.
If the infrastructure project requires a specific programming language or interoperability with other programs, our consultants work with our software developers to create a solution that will meet the project objectives as described in the functional specification.
Lab / Pilot
The infrastructure team incorporates the feedback from the Alpha review cycle to release a Beta version of the project deliverable(s) for client review, This Beta version might consist of a lab or pilot version of the environment. The project then repeats the feedback-revision cycle, and tests are performed to troubleshoot the deliverable(s) and the deployment plan. All team members and the client provide input during these review phases of the project to ensure the final deliverable(s) address client requirements.
Training
Training materials may be developed during this phase of the project as required by the client to facilitate a smooth handoff of the final deliverable. An architecture information document is handed off as a requirement to transfer any necessary configurations or logins.
Deployment
After all parties approve the tested functionality of the final deliverable it is delivered to the client for deployment, which typically marks completion of the project.
