Presented at 3|SHARE's EVOLVE'14 - The Adobe Experience Manager Community Summit on Tuesday November 18th, 2014 at the Hard Rock Hotel in San Diego, CA. evolve14.com

1. Accelerate Your Next AEM Project
MAXIMIZING YOUR TIME & INVESTMENT WHEN ADDING A SECOND DOMAIN
JOHN JONES, SAS • MARK KELLEY, ICI DIGITAL

2. ACCELERATE YOUR
NEXT AEM PROJECT SAS & JMP Landscape
• SAS: $3B business analytics software firm
• SAS has adopted AEM as enterprise WCM
• SAS.com implemented AEM (Launch January 2014)
• JMP is a product and brand within SAS
• JMP is a customer of SAS IT team
• JMP.com needs to implement AEM

3. ACCELERATE YOUR
NEXT AEM PROJECT SAS & JMP Goals / Requirements
• Maximize investment in AEM
• Leverage existing AEM infrastructure and work product
• Re-use as much of existing design as possible
• Not interrupt SAS.com team velocity
• Meet budget, time, and resource constraints of JMP
• Launch JMP.com ahead of JMP 12 product launch

4. ACCELERATE YOUR
NEXT AEM PROJECT Eight Key Accelerators for JMP.com AEM Implementation
1. Clearly define your strategy for another domain
2. Reuse, refactor, then build new
3. Develop appropriate team structure between old and new
4. Maximize knowledge share
5. Change your business processes
6. Think creatively about business needs
7. Don’t skimp on quality
8. Enroll authors early in the process

5. ACCELERATOR 1 Clearly Define Your Strategy
• Inventory applications, integrations, processes
• Three-week strategy phase critical to JMP success
• Technical, functional, and process perspectives
• Assessed current state, defined requirements,
mitigated risk, and created the reuse and
implementation strategy
Teams Involved
JMP Marketing
JMP Online Team
SAS Digital Marketing
SAS IT / AEM SMEs
iCiDIGITAL AEM Consultants

6. ACCELERATOR 2 Reuse, Refactor, Then Build New
• Reduce development time and energy by
eliminating redundancy
• Reduce overall development costs through
reuse and refactoring
• Spend budget on new functionality

7. ACCELERATOR 3 Create Appropriate Team Structure Between Old and New
• SAS.com team already had velocity with AEM
• JMP.com considered a parallel vs. combined team
approach with SAS.com development team
• Chose a combined teams approach
• This is the approach that worked for us; your
mileage may vary

8. ACCELERATOR 3 Create Appropriate Team Structure – Combined Teams
Pros of Combined Team
JMP Development will benefit SAS.com and
support.sas.com
Refactoring existing components will have
reusability benefits
Combining SAS and iCi developers will
leverage SAS.com and CQ expertise
Velocity can be shared or pooled
IT Developers will be cross-trained prior iCi
resources disengage
Overall efficiencies in collaborative
development and planning
Cons of Combined Team
Backlog prioritization is a new process
Onboarding new contractors can impact
velocity
Daily scrum and sprint planning may lengthen
due to larger audience
Onboarding current developers to JMP can
impact velocity
Scaling beyond SAS.com, JMP, Support is
difficult** (Turned out not to be the case)

9. ACCELERATOR 4 Maximize Knowledge Share
• SAS.com team already had AEM knowledge
• iCiDIGITAL team brought external AEM
expertise and experience from other projects
• Make sure functionality can be maintained after
the contractors leave
• AEM author training for JMP team

10. ACCELERATOR 5 Be Willing to Change Your Business Processes
• Adopt and modernize business processes to AEM
• AEM can improve operational efficiency and user experience
• Example: JMP 30-day trial

11. ACCELERATOR 6 Think Creatively to Satisfy Business Needs
• Think creatively about how existing templates and component can
be modified to suit your needs
• Collaborate with other AEM site owners and development about
needs and requirements that could be shared

12. ACCELERATOR 7 Don’t Skimp on Quality
• QA is critical to success
• For SAS & JMP, QA became a bottleneck that slowed
project velocity
• Invested in QA resource to increase QA capacity

13. ACCELERATOR 8 Enroll Authors Early in the Process
• Fosters adoption of AEM
• Authors provide insights about how AEM and
existing processes can be blended, modified, or
created to improve publishing
• Utilize authors during migration
• Better trained authoring team at launch

14. ACCELERATE AEM
IMPLEMENTATIONS Eight Accelerators
1. Clearly define your strategy
2. Reuse, refactor, then build new
3. Develop appropriate team structure between old and new
4. Maximize knowledge share
5. Change your business processes
6. Think creatively about business needs
7. Don’t skimp on quality
8. Enroll authors early in the process

15. Accelerate Your Next AEM Project
MAXIMIZING YOUR TIME & INVESTMENT WHEN ADDING A SECOND DOMAIN
JOHN JONES, SAS • MARK KELLEY, ICI DIGITAL

17. ACCELERATOR 8 Enroll authors early in the process
Q&A

18. ACCELERATE AEM
IMPLEMENTATIONS Eight Accelerators
Company Confidential - For Internal Use Only
Copyright © 2013, SAS Institute Inc. All rights reserved.
• John Jones
JMP Sr. Online Marketing
Manager, SAS
• Devang Shah
Director of Technical Services,
iCiDigital

19. SPEEDING TO
EVOLVE SAS AND JMP – PROJECT BACKGROUND
• SAS.com - existing AEM (CQ5) site – January ‘14
• JMP.com – manually managed site with growing
pains; carbon-based CMS
• JMP – unique identity and brand
• Project goals
• Speed up delivery of marketing web content
• Leverage existing AEM investment on JMP.com
• Implement quickly and minimize costs
• Allow for continued development on SAS.com
• Lay groundwork for addition of SAS customer support site

20. SPEEDING TO
EVOLVE ASSESSMENT
• ICI-Digital – 4 week assessment
• Interviews with marketing team, web team
• Review of existing JMP.com content and functionality
• Evaluation of current SAS.com AEM functionality
• Identify the similarities and differences
• Re-use, re-factor or build new?

21. SPEEDING TO
EVOLVE KEY TAKEAWAY
Involve authors and key stakeholders early

22. SPEEDING TO
EVOLVE ASSESSMENT OUTCOMES
Templates Components
Re-use 1 12
Refactor 0 9
Create New 2 27
Total 3 48

23. SPEEDING TO
EVOLVE KEY TAKEAWAYS
• Maximize efficiency through re-use
• Think creatively

24. SPEEDING TO
EVOLVE THE IMPLEMENTATION
• Augment existing development team with 3 iCiDigital developers + .25
architect
• Challenge: QA bottleneck
• Maximize knowledge sharing
• Agile approach
• Parallel teams vs. combined

25. CQ5 CROSS DOMAIN
RECOMMENDATION PARALLEL APPROACH
Company Confidential - For Internal Use Only
Copyright © 2013, SAS Institute Inc. All rights reserved.
Pros
Keep backlogs simple, minimal change
Low complexity in developer setup
Developers focus on each specific site needs
We can scale beyond SASCOM, JMP,
Support.sas.com
Cons
Duplicate components, templates
SASCOM, JMP, Support work in silos
No cross learning
Components developed by contractors will
need comprehensive transition to IT
Spreading the architect and QA thin
Harder to re-use components across teams
Difficult to de-tangle code (back-out), if one
team is a ‘Go’ and the other is a ‘NoGo’

26. SPEEDING TO
EVOLVE KEY TAKEAWAYS
• Look for gained efficiencies
• In it for the “long haul”