Fast Tracking Adobe Experience Manager - AEM Projects – Code Level Approach – Under No Code-Low Code Syndrome...
SENTHIL PICHAI,Adobe GenerativeAI-ExpDriven Digital Marketing Architect
Global Head - Adobe Tech Practice - Services, Solutions, Consulting at Tata Consultancy Services
Fast-tracking enabled with a Code to Code an AEM-Adobe Experience Manager Project is very important from GTM and Time to Market perspective. Additional benefits include better governance, optimized cost of implementation and quick ROI.
Information Architecture, Templates, Components, Workflows, Back-End Integrations and Performance are integral parts of the Chassis of any AEM project implementation along with well-crafted UI, UX and Intuitive Style Guides backed with your Design language and thinking.?
Apart from our pre-built approaches and frameworks for executing the AEM projects, we may use multiple languages and scripts - Java, Sightly, JavaScript, HTML5, CSS3, Styles, React/Angular, REST… along with AEM. SPA/PWA/Headless/Headful/Hybrid are additional forms of our approaches.
The nostalgic factor here is, how to prevent the discovering of the wheel again and again. How about creating a set of structured elements as part of the building blocks, which are having pivotal positioning of your Blueprint and are deployed as accelerators during our project execution.
Optimized Development cycle based on our value stream mapping across project timelines and activities, is key here with the tenets covering scalable, reversible, non-dependable, flexible, and ready to implementable.
Resource utilization is very important… starting from user stories to grooming, then development and integration. We may not have always our purple squirrels considering the various factors. The theme for us is optimizing the productivity with code level transformation approach.
领英推荐
Here, we are examining some of the quick and low-hanging fruits, that we can use in our approach towards fast-tracking the AEM Projects.?
An important advantage here is that you are standardizing your codebases.?While you are working continuously, you can optimize these standards to a greater level of maturity as part of your documented standard procedures as guardrails to prevent the conundrum across the projects and deliveries.
How much we are capitalizing on these, are very important in optimizing our CAPEX, OPEX and TCO/Project cost. Upgradations/Migrations would be catwalks, post the implementation of the current projects and in new projects with proven referenceable approaches, project & solution accelerators and guidelines. These would be greater addition to your Agile processes, Project Development tools, CICD, Infra and Release approaches in your Project Implementation.
We are always trying to connect the dots… Why not the clusters also, for our project efficiency and greater deliverables… the Awesome Products quickly that result in excellent Content Experience.