Let us see how a project manager should think before he starts with a site migration to AEM. What things does he need to consider? The history of AEM has seen thousands of migrations to AEM. But how many were successful? How many of them were cost-effective? Let us do an analysis.
Planning before he starts.
There are multiple planning sessions to be done before the actual migration starts.
Cost/ Budget Planning
The PM should think of the total cost estimated for the complete implementation. This includes initial setup, UI development/ UI changes, developing new feature additions, QA tools, platforms, integration costs, licensing costs, etc.
Technical Planning
PM should get clarity on the total number of sites, UX changes, data conversions, system integration, and any analytical and personalization items.
Team Planning
The right mix of the technology team is necessary for any development. For an AEM, the considerations should be the back-end, and front-end capabilities of a developer including various integration through the web-service layer, analytics, search, etc.
Implementation Planning
Define the correct time frame with proper sprint planning. Include the team in discussions is necessary for this.
Integration planning
Third-party integration can be a complex task when the developers are not aware of it. Always try to add a developer who knows the various integration like search, analytics, web-service, etc.
QA Planning
Define a QA Strategy and ensure the test cases are prepared well before the actual development.
Deployment Planning
Ensure the DEV and QA work together to make the deployment process successful. Define a deployment strategy considering the latest tools and technologies available.
Set a well-defined communication channel for the deployment process which makes the deployment smooth and successful. Ensure the rollback and disaster recovery are considered in planning.
Post-deployment planning
Regular Monitoring of performance and any backups are to be planned as part of this.
He or she should also consider the partnerships for AEM implementation, Adobe cloud solutions, and infrastructure in the course of time. Let me know your migration experiences through the comments section.
How do we estimate an AEM Migration project?
There are scenarios where we need to migrate any existing CMS content to AEM.
Let us see how we estimate the migration activities.
Below given the activities for doing a proper estimation. The assumption is that the entire site is re-created in AEM as is.
- List down the templates: Identify all the templates on the site.
- Estimate the templates: Estimate the time for creating each template. (Skip the same types, consider only unique ones)
- List components: Identify all the identical components to be created.
- Estimate the components: Define the time for each unique component creation.
- Analyze the current CMS content ( XML/JSON Data) : Analyse the content. It may have textual content, metadata, tags, etc.
- Estimate the scripts for each component (XML/JSON Data to AEM Component): Now estimate the time required to migrate the content using any of the content migration approaches/ scripts.
- Analyze asset migration: Find out how the assets are organized in the current system. Find out the ways to move them to AEM.
- Estimate asset migration and categorization(Extract and update metadata for digital assets on AEM): Here we need to calculate the time required to move the entire asset(no duplicates) to AEM.
- Estimate the Analytics part: Calculate the analytics implementation
- Analyze the integrations: Find out all integration points and ways to replicate it in AEM.
- Estimate Integration (Login, Authorization, Search): List out the time for integration implementation
- Analyze the workflows: Find all the workflows to be created in AEM
- Estimate Workflow creation: Estimate the time for creating workflows based on the complexity.
Environment setup(dev,qa,prod,dr)
Testing
Release configurations & activities
Additional authoring after the content migration.
The above activities help to provide a valid estimation for any migration project.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.