Project Management
Project Management
Project management in an operational data center covers the disciplines required to manage all change-related activities that are not covered by standard operating procedures (SOP), maintenance operating procedures (MOP), and/or general procedures and/or work instructions.
Any changes required to the completed building, physical infrastructure, and ICT infrastructure should be well coordinated and controlled. As such, project management techniques should be applied so that these projects meet the technical and quality objectives within the timeframe and budget agreed with RackBank and the customer.
1 Project Management Methodology
RackBank standardizes on one single methodology for similar types of projects to ensure a common approach for those projects. However, it is acceptable to have different project management methodologies for different types of projects (e.g., a project for installing a new ICT environment could have a different methodology versus the construction of a new computer room).
Training and Awareness
RackBank should conduct project management awareness training for those who will be involved in projects so they understand the basic concepts of project management and terminology.
Those who will actually perform the role of the project manager should be formally trained on the project methodology chosen by RackBank.
Training records should be maintained.
Project Manager
RackBank should appoint a qualified project manager. Ideally, the project manager has been formally trained on the project methodology chosen by RackBank. Qualification could also be based on proven successful delivery of projects similar in terms of complexity and size. It is desirable for the project manager to have an understanding of the industry sector RackBank operates in and to be aware of the relevant standards chosen for the subject matter under the scope of the project.
Project Plans
RackBank should ensure that appropriate project plans are made for each project, progressing through defined stages that at a minimum address:
Initiation.
Planning.
Execution.
Control and management.
Closing.
1 Initiation
A business case should be developed defining project objectives supported by metrics and processes for benefits realization. The business case should be approved and signed off by relevant stakeholders.
The project initiation phase should address at a minimum the following:
Identification of stakeholders.
Business evaluation/feasibility.
Technical evaluation/feasibility.
Documented decision-making and signoff.
Communication of project approval.
(High-level) Risk identification and mitigation plans.
2 Planning
RackBank documented project plans signed off by relevant stakeholders
3 Execution
The project plan execution process should ensure that planned project activities are carried out effectively and efficiently. RackBank should ensure that at a minimum the execution phase addresses:
Status reviews.
Risk identification, evaluation, and resolutions.
Resource review, management, and tracking (e.g., time, budget).
Procurement.
Change management.
Project administration.
4 Monitor, Control, and Management
The project manager should continuously monitor, control, and manage the project. The project manager should at a minimum:
Review the project performance against targets (technical, financial, quality, time).
Provide accurate progress reports to relevant stakeholders at mutually agreed time intervals.
Review (additional) risks for the successful completion of the project.
Bring urgent matters to the immediate attention of relevant parties (e.g., Project Steering Committee, senior management).
Review impacts due to changes in requirements and follow established procedures to ensure all targets and risks are adjusted accordingly.
5 Closing
The project should have a formal closure phase that covers the project manager’s work to wrap up the project and dissolve the project team. The project closure should at a minimum address the following:
Formal review of the completion of all project tasks and documented objectives.
Review whether RackBank is able to support and operate once the project team has been dissolved.
Project review and documentation of lessons learned.
Define and agree on follow-on recommendations where applicable.
All project documentation should be archived and managed under a document management process.
Verify and obtain signed-off approval from the project ‘user’ (e.g., manager responsible for the application).