Work Breakdown Structure in Cloud Migration Projects

Work Breakdown Structure in Cloud Migration Projects

Work Breakdown Structure, also known as WBS, is a widespread project management technique that helps with project planning, execution, controlling, monitoring, and reporting.

WBS is a technique used in various projects to accomplish project objectives and create the required deliverables. The goal of WBS is to take a high-level set of categories and continually decomposes them until they reach a level of detail that allows for the identification and management of specific activities. All the work contained within the WBS is to be identified, estimated, scheduled, and budgeted.

In this article, we will explain how we use WBS in cloud migration projects. Cloud migration projects are decomposed into five phases: initiation, planning, execution, control, closing.

Initiation

The first phase of the project is an initiation; the goal is to define the project scope and objectives.

1. Evaluation & recommendations - customer's current infrastructure is evaluated and suggestions for improvements based on user requirements are given.
2. Develop project charter - the project manager is working on the project definition.
3. Submit project charter - after the project is defined, it is submitted to the project sponsor.
4. Project sponsor reviews project charter - project sponsor reviews the project charter and gives inputs and suggestions if needed.
5. Project charter signed/a approved - all parties formally agree with project definition.

Planning

The second phase of the project is planning; it is based on the project charter.

1. Create preliminary scope statement - project manager creates an initial scope statement.
2. Determine project team - project manager defines the project team and requests the resources.
3. Project team kickoff meeting - planning process officially starts with the project kickoff meeting, which includes the project manager and project team.
4. Develop project plan - project team develops the project plan.
5. Submit project plan - project manager submits the project plan for approval.
6. Project plan approved - the project plan is approved and permission is given to execute the project.

Execution

In this phase, the new solution is designed, implemented and ready for production.

1. Project kickoff meeting - project manager conducts a formal kickoff meeting with the project team, project stakeholders and project sponsor.
2. Verify & validate user requirements - the project manager and team review the original user requirements, and validate them with the users/stakeholders.
3. Solution design - technical resources design the new solution.
4. Procure hardware/software - the procurement of all infrastructure, software and facility needs for the project.
5. Install development solution - the development system is installed and configured.
6. Testing phase - the system is tested with a select set of users.
7. Setup new solution - the actual system is installed and configured.
8. User training - all users are provided with training or guides. Additionally, if needed, managers are provided with advanced training.
9. Production - system goes live with all users.

Control

Control is performed continuously during the execution of the project.

1. Project management - the project is continuously monitored and guided by the project manager.
2. Project status meetings - team status meetings are performed on a weekly/monthly basis.
3. Risk management - risks are evaluated and managed continuously.
4. Update project management plan - if needed, the project plan is changed to mitigate risk.

Closing

In the final phase of the project, the goal is to gain formal acceptance.

1. Audit procurement - an audit of all infrastructure and software procured for the project ensures that all procured products are accounted for.
2. Document lessons learned - project team performs lessons learned meeting and documents the lessons learned for the project.
3. Documentation review - all documents are updated to reflect the implemented solution design.
4. Gain formal acceptance - the project sponsor formally accepts the project by signing the acceptance document.

Conclusion

In this article, we talked about the work breakdown structure for cloud migration projects. WBS helps us guide the cloud migration project from initiation to formal acceptance. The project is broken into five main phases: initiation, planning, execution, control, closing. Each phase has a clear and well-defined set of tasks and deliverables. Cloud migration projects are very complex, and they usually affect all organization's departments. For successful project execution and delivery, it is crucial to have a well-defined and prepared project - WBS helps us achieve these goals and justify client's investment.

As AWS Advanced Consulting Partner, we help companies of every industry and size solve their infrastructure problems with cloud migration.

If you want to know more about cloud migration, cloud technology in general, AWS cloud, or you want to try AWS services:

• visit our cloud migration service page;
• give us a call at +385 1 3141 562;
• contact our sales department at sales@heptabit.com.

---