Inspiring Change - Keynote Tridion Developer Summit 2015

Editor's Notes

• #26: A
• #28: Hello and thanks for joining us today, my name is Dennis.. I am very excited to be speaking to you …… first dev day, technical deep dive, we listened to you….
• #29: {this is the SDL Journey} Predictive/proactive – should be predictive Top=technology Bottom=experience I would like to share a bit about the journey we are on here at SDL. From my standpoint we spent 2014 Aggregating all our solutions to help you to deliver seamless customer experiences to your customers, now that we have done that its now about helping you to accelerate your path to CX enabling proactive experiences for both your LOB teams and your customers, and as we move forward its about how we provide capabilities as Mark just talked about to Automate and provide intelligent capabilities for faster delivery of more engaging experiences for your customers. Today I am going to 2014 Product integrations Service catalog Move to cloud Common UX 2015 Proactive Experiences --- Should it be predictive? Prescriptive experiences Integrated workflow UX CX analytics Language ecosystem 2016 Machine learning & algorithmic decisions Automated classification and mashups Cloud API solution sets
• #30: Rephrase! Notes: We are delivering on the SDL Customer Experience Cloud promise – focused on these 4 pillars We are investing heavily for the future – to ensure we accelerate and automate the your ability to deliver phenomenal customer experiences. We are listening intently to your feedback – We are partners with you, our customers, and our technology & implementation partners, to help ensure your success.
• #31: Optional slide if you need to get into more detail Talk Track Taking a deeper look at SDL’s solutions. All solutions are seamlessly connected Available in the cloud, on premise or a mix of the both, which means that you are secure in the knowledge that SDL can grow and evolve as your business evolves and grows Objective of the slide: Ability to go into more detail on the SDL stack What is the key point: SDL is connected, agile and flexible and “real” (not slideware)
• #32: So what is our Development Strategy? Actually this is a journey that we started in R&D many years ago. I am happy to share this with you. It has not been an easy journey, but it has been a very exciting one. As you can see, the way we look at our IP/software has changed dramatically. You do not see any product names anymore! We have made the mental shift from Products to Capabilities. What does that mean? Speed up development – move to microservices, more frequent releases, Unlock our IP - Combine to deliver more OOTB solutions – accelerate YOUR development so you get to the cool stuff! Higher level API Expose endpoints to the capabilities to YOU so you can build useful and cool apps on top of these capabilities Examples Web Delivery Platform/Content Services SDL ID Language Cloud which Erik will talk about later DXA which Bart will deep dive on
• #33: In order for us to deliver and run our CXC,…. Release our software as Service – hook in to earlier slide. This requires a Mental shift – Ops reports into me Close collaboration between Dev and Ops Continuous delivery, infrastructure development ETC
• #34: We cannot do it without you (and vice versa ) I am very proud of my development team. Our DevOps culture can best be described; what I ask of my team can be best summarised as Commitment and ownership Appreciate and give credit each other Transparency Expand a bit on this for devops, some examples? Scrum, etc etc So for us, these are the principles behind how we want to engage with our ecosystem. For a long time, we have not done a great job at supporting and being open with our community. While we cannot exist without you building on and doing great stuff with our technology! Therefore, we have committed ourselves to improving that majorly. We are doing that not by talking about it, but by our actions.
• #35: No difference between “internal” vs “external”
• #36: One SDL Learn from what works in different parts and extrapolate Listen! Take action. This is across the board, our end users, cx strategists, developers, architects and administrators.
• #37: Program: We are shaping this step by step and we would very much like to do this together with you. Your input is very much appreciated.
• #38: Improved Developer Experience – our goal is to make it easier. DXA + Open conversations API/Endpoints for easy implementation and integration (Dennis) Enabling conversation and assured learning (Wilfried) Next to this we will also be improving technical content Whitepapers, best practices, methodology – and also created by you sandboxes – we will create content but we cannot do it alone Finally, we want to improve the communication channels to and from R&D. Open up the conversation. We will promise to listen and to respond; we cannot promise that it will go perfectly all the time, as this is a change in the organisation. But we are very committed to this.
• #39: A bit cheesy, since you all probably saw the MS <3 Linux slide. However, this is exactly why I put it up there! The transformation we are currently going through is not unlike MS. We come from a place, as some of our veterans in the audience can attest, where we used to be a quite closed organisation. We showed you the steps that we took to open up but this does not go far enough! We want to truly embrace the Open Source philosophy inside and outside. So why is this important for us? Our Mission: Building and facilitating our developer network/ecosystem as mentioned before Establishing ourselves as an open, modern development organisation Part of broader dev community - Participating and feeling part of the broader development community – fast paced technology development, no development can or should happen in isolation (anymore) Expose and get feedback - on the awesome stuff our developers are working on – Share – re-usable components and services model Recruitment I have created a workgroup of champions and we are rolling this out is along three pillars.
• #40: In fact, we already started! Lots of open source projects for Language platform, both LanguageCloud and Studio. But also, DXA (TRI), which Bart will be talking about today, and check out Renze’s presentation for some exciting announcements.
• #41: We are committed to you - join us on our journey and have fun!