Discovery / Assessment phase is the most critical and defining phase of any AEM upgrade. This phase is going to define the plan, efforts, and complexity of the upgrade.
- One of the important steps in discovery phase is to do the dry run of the current production system. Other than this, this phase is also going the drive the changes that are required to make earlier version code compatible with latest one.
- Estimating upgrade project without complete analysis of the current system makes project cost overrun like anything. Hence, its important that a formal assessment of the current system should be done before estimating and same should be put into the discovery (assessment) report.
- This assessment report becomes the key asset for upgrade. Depending on the complexity of the system, upgrade project may take 1 to 4 weeks of assessment.
- The Discovery Workshops are the Adobe team’s opportunity to dive deep into the customer’s use cases to understand what it is that they are looking for. From the information learned in these workshops and any follow-up conversations, the Product Backlog and Solution Design document will be created. While the actual workshops performed should be tailored to your customer’s needs, some of the common workshops that are held include:
- Review of the customer’s business – who are the users?
- Current site review
- User experience design for the new site
- Business processes used to create content
- Future plans for the site
- Technical requirements to do the upgrade
- Non-functional requirements such as user-load (author and publish), SLAs around up-time and response time, etc.
- Content that will need to be migrated to the new site
- Current and future architecture (logical as well as physical)
- Infrastructure sizing details/Network and system architecture (current and future)
- Post upgrade maintenance details (current and future)
- Product customizations required
- Application related customizations required
- Deprecated components list and its mitigations
- Integrations with any third party platforms or tag libraries
- Integrations with other Adobe Marketing Cloud products
- Any SEO requirements
- Localization requirements and processes
- Mobile/responsive requirements
- Personalization requirements
- Network and system architecture
- Build and deployment management
- Test plan
Here is a sample table of contents of an assessment report -
- CQ Environment
- Logical Architecture
- Physical Architecture
- NFRs
- Environments Deployed
- Runmodes
- Repository Configuration
- Dispatcher Version
- System Load and Scalability
- Code and Content Flow
- Components and Templates
- Queries
- Security
- Redundancy and Availability
- Systems Integration
- Development Processes
- Development Team
- Agile Practice
- Code Management Practices
- Upgrade Impact Assessment
- Product customisation
- Deprecated components
- Current and future architecture state
- Authoring & Business Processes
- HTTP configuration review
- Virtual host configurations
- Dispatcher configurations
- Code review
- Java Version
- Maven Architecture
- OSGi Services
- Component Package
- Workflows
- OSGi Configurations
- Components and Templates
- Queries
- Test Plan & Strategy
Comments
Post a Comment