Adobe Roadmap Example

[nsvsrk]

Hi all,

Generally consultants offer Roadmap to the client, in their implementation

Is there an example of an Adobe Roadmap (sequence of different projects) with some reasonable justification?

Ex: One brand going live and all others follow, and Cloud Migration.

For example, how could we justify the sequence?

"One brand going live and all others follow" is fully justifiable.

What about Cloud Migration?

Appreciate all your replies.

Thanks,

RK.

[narendragandhi]

Hi @nsvsrk 

You can refer this skill exchange video for some of the tips on how to approach an incremental cloud migration - https://experienceleague.adobe.com/en/docs/events/the-skill-exchange-recordings/aem/aug2023/develope...

Feel free to reach out to community for any specific questions regarding the cloud migration.

Thanks

Narendra

[nsvsrk]

Thanks Narendra.

Is there any example of an on premise implementation roadmap that you could guide me as well? Of course with sufficient justification.

Thanks,

RK.

[ManviSharma]

Hi RK,

Yes, below documentation should help:

https://experienceleague.adobe.com/en/docs/events/the-skill-exchange-recordings/aem/aug2023/develope...

- The choice to start with a single brand allows for a controlled environment to test assumptions and gather valuable insights. It reduces the risk of widespread issues and ensures lessons learned can be applied to subsequent rollouts.
- This approach provides a structured path for scaling up, allowing for adjustments and improvements at each step. It ensures that the project remains aligned with business objectives and adapts to any changes in the market or organization.
- Placing cloud migration after initial rollouts ensures that the organization has a solid foundation and understanding of Adobe solutions. This timing leverages cloud benefits for scalability and performance as the organization expands its use of Adobe tools.

[daniel-strmecki]

Hi @nsvsrk,

I think every AEM consultancy has (or should have) a roadmap for topics like "Cloud migration" or "Move to EDS", but I doubt anyone would share it here publicly as this is considered intellectual property. I suggest using the available Adobe documentation and creating your own based on previous experience and what makes sense.

Good luck,

Daniel

[kautuk_sahni]

@nsvsrk Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

[giuseppebag]

You can justify the sequence in an Adobe roadmap as follows:

Phased Brand Rollout (One brand going live and all others follow) - It is justifiable for several reasons:

• Risk Mitigation: By starting with a single brand, you minimize the risk of widespread issues. If problems arise, they can be contained and resolved before scaling up.
• Learning and Optimization: The initial rollout serves as a pilot project, allowing you to gather insights, refine processes, and optimize the implementation strategy before applying it to other brands.
• Resource Allocation: Focusing on one brand at a time ensures that resources are not spread too thin, allowing for a more concentrated effort and better results.

Cloud migration is a critical step and its placement in the sequence can be justified as follows:

• Infrastructure Stability: Before migrating to the cloud, it's crucial to ensure that the current infrastructure is stable and that any on-premises systems are fully functional. This stability provides a solid foundation for a successful cloud migration.
• Scalability and Performance: Cloud migration should follow initial rollouts to leverage the scalability and performance benefits of the cloud. As the organization expands its use of Adobe tools, the cloud can provide the necessary flexibility and resources to support growth.
• Cost Efficiency: Migrating to the cloud after initial rollouts allows for a better assessment of resource needs, leading to more cost-effective cloud solutions tailored to the organization's requirements.

Take into account a few other additional considerations:

• Ensure that all systems and applications are compatible with the cloud environment before migration. This includes testing and validating integrations to avoid disruptions.
• Address security and compliance requirements early in the roadmap to ensure that the cloud environment meets all regulatory standards.

Creating a structured approach and a tailored roadmap for the client is a challenging task. However, with careful attention, you can develop a roadmap that not only outlines the sequence of projects but also aligns with the organization's goals and facilitates a smooth transition.