okay I think we will make a start so welcome to another in our servicenow live on servicenow webinars this one is going to cover the devops change uh workspace so we will get straight uh into it um first slide which you may have seen a few times before if you've been to any servicenow presentations before it's just our Safe Harbor slide in case we talk about any future features which we haven't delivered yet please don't make any buying decisions on those but everything I'm going to talk about today is already available in the current version of service now uh just some notes about this is part of an interactive series and there's a schedule available for other events that you can join I think one of my team members will post a link to that in the chat so please have a look at that and register yourself for the other events if you haven't already there's some really useful stuff in there I've got a bit of a croaky voice today so Excuse me while I pause to have a sip of water I think my wife gave me her cough all right we'll move on so just in terms of excuse me how we're running this session um we will have time at the end for for Q a so you can definitely post your questions in the Q a as we go through the presentation but seeing as we're a small group I think we're okay with um people asking questions uh and and you can unmute yourself and ask questions as we go through if you like because we don't have a a large audience today and just to note that we are recording this presentation and will be shared on our servicenow community page and you will be sent and events survey at the end to to get your feedback and thoughts on on the event and how we can improve okay so a little bit about me my name is Mike I'm an outbound product manager in the itsm business unit at servicenow based in Melbourne I've been with servicenow for around 10 months and uh looking after devops and itsm okay so first I'd like to start with a poll question which is to just get an idea about um how uh and whether you are using the devops change workspace today so have a look at those questions I'm going to launch the first poll now and please respond with your answer to the poll just give it 30 seconds for people to finish responding be great if everyone can respond please okay I'm going to end the poll so it looks like um some folks on the call have have started using it and had some minor usage and some people are planning to use it soon so that's perfect these sessions are really um all about um adoption so what we're after today is to get a view of where you are in terms of adopting uh devops change and we're we're here to to help you get started that's what the session is all about so we're here to show you how you can use the devops change workspace to to kick off that work and to get started because we're very keen for customers to adopt okay so let's get straight into it so when we talk to our customers um that and and this is just to provide some context before we before we launch into the actual devops change workspace this is to give you some context on on what the product is all about and the problem areas that's that it's addressing so a lot of organizations are telling us that when they're they're trying to adopt devops um they're having some challenges and some issues so often the developers are sitting in their their own tool sets and they're obviously uh you know writing code and doing some testing and committing the code and doing lots of deployments and then the operations folks on the other side are looking at the changes that are coming through and trying to understand what is being changed and often these two sets of people the dev and the upside don't all share the same data because they don't have access to each other's tools and that creates a bit of a divide a bit of a wall between the two groups and often results in some issues so for example in the middle slide there in the middle section you can see there some customers are saying that a lot of their changes are not registered they're they're flying under the radar and they're not going through the change process and that's probably because developers have to manually switch to servicenow and create changes manually and go through that process which they see as an overhead this overall results in the slowdown in terms of the overall delivery and it's difficult to achieve what devops is promising that customers can deliver so if you look at the roles involved and you look at the people that are typically doing these roles we can see that for example as I said the developer um doesn't want to spend time on admin tasks and raising changes manually they just want to do their work in their tool and and get the code out the door the change manager is seeing a lot of changes either flying out of the radar or when they do come through having trouble understanding the increasing volume of change and what is actually changed so you know there is often not good data on the change record to help them understand that and then you've got other other roles like you know governance and compliance how do we make sure that changes are being compliant with our controls and our governance how do we measure how do we have transparency and auditability into what's being delivered and if things go wrong operations support often don't have that visibility so when we've got an issue how do we know what changed how do we know when it changed and who changed it and the engineering manager is also trying to get insights into their devops team and how they're performing and look at the data in terms of trying to understand any bottlenecks or or issues across the value stream so those are the problem areas essentially that we address with the devops change velocity product and how do we do that so essentially what we work our our strategy is let's keep developers in their own tools so we don't want to force developers to come into service now they should be able to stay in their own tools what we do instead is we integrate all those tools through our uh spoke spokes through integration Hub we have a lot of the most commonly used tools are available we have connectors for those so some of those you can see on the screen jira GitHub Jenkins Azure devops Etc so we we do the in integration up front and the devops change workspace will help you do that very easily and once we get that data into servicenow we're able to make use of that data in order to automate the change process so for example we can look at you know whether we passed all our unit testing whether our code coverage was above a specific percentage that's meaning meaningful for our organization you know do we have any security vulnerabilities do we have any incidents or change freezes that we need to adhere to all the data that's in servicenow can be used in order to create decisions in a change approval policy to automate the change process and the other thing that we get is we're able to measure performance and we'll have a look soon at the at the insights dashboard which allows us to measure the performance of what's being delivered so that should all result in a lot more efficiency for all these roles so at the end of the day we're using automation to increase visibility and to increase velocity of Change devops Change whilst maintaining compliance and auditability and providing insights into how we're delivering what we also do within the product is we we provide organizations and customers with an adoption Journey so you don't need to jump straight into Nirvana which is full change automation which is at the top of the top right of the slide you can start slowly and onboard your tools and teams first and then move through a crawl walk run process and the tools all support this in order to eventually get to full change automation uh in your organization so we're able to support that with with our tools okay so now we're going to get into the devops change workspace and go through that now instead of instead of jumping through uh these slides the rest of these slides I think what I'll do now is just skip through these and we will go and talk about all these different aspects of the workspace in the demo so I'm just going to stop my share and pause for a minute now do we have any uh any questions at this stage we are good we are good as of now I don't see any questions in chat box as well okay cool just a reminder again if you do have questions you're welcome to to come off mute um and um or you can put your your questions in in the chat all right let me share again okay so this is my uh servicenow instance uh sorry is that screen showing for everyone can you see the uh Chrome browser yes you do yep great okay so how do we get how do we get to how do we get to the devops change workspace so you can just click on workspaces here and there's a link to it or you can go into the Navigator and type in devops change and there's a link to it there so two ways to get to it okay so this is this is what it looks like now we're going to go through all the different parts of this but what I want to draw your attention to here is these three sections these cards up at the top really what we're trying to do here is make it easier for our customers to get started so previously before we had this workspace um obviously we've got documentation and implementation guides available where customers can go and do the setup and integrate all their tools and onboard their teams their applications Etc that's a fairly lengthy process and we wanted to make it much easier for our customers to get started so the way we've done that is by using these cards they guide you through what you need to do to get set up and there are playbooks that sit behind each one of these which will automate many of the steps involved in onboarding so for example setting up of system accounts will will allow you to set up the accounts that manage integration and and the system Etc I know I've already done that in this instance you can also assign roles so for example different people in your organization can have different roles they can be application owners or devops admins and you're able to assign roles to those folks there you're also able to assign tasks so for example if I need to do an excuse me do an integration with jira and I need my jira admin to provide me with some information about the jira URL and the credentials I can assign that person a task and ask them to do that work so that's that section over there and then over here we've got playbooks which actually help you to connect all those tools and to create your devops applications so let's initially have a look here at connecting a tool okay so we we categorize the different devops tools via these different categories here so planning tools these are tools that contain your work items your planning your projects your user stories your features bugs Etc will sit in one of these tools your coding tools obviously contain your code your code repositories your orchestration tools are the ones that manage your CI CD pipeline um your software artifacts so things like artifactory or ado software quality tools so tools like sonar Cube Etc that manage uh scanning and we also support uh feature flag tools like split so if we want to connect a tool I'll just give an example here I'm going to connect to my jira instance so I'll give it a name [Music] click on next and what this will do is it will go and run a Playbook so the Playbook is going to gather all the data that's required from me so it's asking me for my jira URL I'm just going to grab that and paste it in and then my username and now I need to provide my token password token or personal access token and then I click connect so this is going to go off and try and connect using those credentials to jira in this case and ensure that I have connectivity and it's also checking the permissions so obviously within jira you need different permissions to ensure that you can access your plans and fetch the stories Etc via web hooks and excuse me for a sec sorry about that and and this The Playbook is ensuring that you have the right permissions in place in order to proceed with the next step if I didn't it would tell me and it would give me some help and tell me what I needed to do in this case I do have the right permissions so I can continue now what it's going to do is going to fetch all the data that's available in that in that jira instance and I'll just quickly show you that this is the jira instance I'm connecting to so you can see I've got a whole bunch of projects with different data that's sitting endure there now I have a choice I can either use web hooks which will get set up automatically for me and that's recommended if I want to bring in data in real time so when stories are created and updated Etc the webhook will notify servicenow and update the data in servicenow if I don't want to do that I can I can enable nightly polling and that will trigger a job to go and fetch the data every night if I don't need real-time data we're going to configure the web hooks to get real-time data so I'll click on configure now that's actually going and setting up those web hooks in in jira and pulling in all the data and it's exploring discovering all that data that that exists in my jira instance and it's going to come back eventually hopefully right so it's gone and found all that data in jira and it's displaying it for me and now it's asking me uh which of these 106 plans that have been discovered do I want to track in in servicenow so I'm able to select I'll just make this bigger and let's say I want I'll just pick a few just say I want these ones I'll just pick those ones okay and then click on next and now the ones I selected are going to be tracked via webhooks automatically so this Playbook is now finished that jira tool is connected and I can now view it okay so what that's done is it's it's run and import that import request has gone and discovered all the data and it's pulled in all the plans and it's it's tracking the ones that I asked it to to track here so that's basically how how that works I'll just close that the other thing we can do is we can create a devops application so let's say I want to create a devops application we'll call it live on service now yeah two this will go and create a new sdlc component and application model in the cmdb with that name or I could have used an existing one if I if I had one already created I could use an existing one so this is created in an app for me and then over here on the right you can see recommended actions so the workspace is guiding me in terms of what I need to do next so you can see currently I don't have any plans or code repositories pipelines or artifact repositories or associated with this application but I can go and do that I can associate those items with my application so just as an example I'll say associate these plans with this application and I can now go through and say I want to import all the historical data maybe I'll go back to January and say import all that data for me and it will go and import all that data and and add it into servicenow and Associate it with this application in servicenow and a similar way I can associate my repositories my pipelines Etc so that's all there for me uh and guided and guided for me yes as part of the workspace okay the other thing I can do once I get to the stage where I've got my pipelines in place and I want to automate my change process I'm able to do that by clicking on on these links to to to do that and I can also view some guidance in terms of how it works so I've got some inbuilt in-tool help which will guide me through how to set up a change approval policy how to manage it Etc so it's all in one place it's a single place where I can go for everything okay um the other thing on here is that I've got some high level widgets which are displaying the tools that I've got connected the events that I've that have been processed Etc any open tasks changes waiting for approval Etc okay so let's jump to um the insights uh section which is over here now because this is my personal instance uh I've only it's only me working on it it's not going to be great data there so I'm going to jump to another instance where there is better sample data just to show you what that looks like once you've connected your tools and you do have developers and teams working with devops the insights dashboard is going to really help you understand where you are today look at your different processes and understand whether you have any issues or or bottlenecks or anything that you need to take care of and focus on and then you can use these different dashboards in here to to track how you're going and your your progress as you as you work through implementing devops and automated automated change so just to quickly show you excuse me flow metrics track essentially cycle time for your for your planning items your work items so the status that each item is going through and how long each item spends in a particular state the throughput and distribution is you know how how are we doing in terms of the number of bugs that we're fixing versus the number of stories that we're delivering how long are we taking to actually deliver stories features tasks Etc and how we're doing in terms of where we are with work in progress now if this is real data I can click into any of these and it'll take me into more detail the change acceleration tab will show me how I'm doing in terms of my devops changes so my change volume how long it's taking to close those changes automated versus manual anything that's waiting for approval Etc and I can even look at savings so because I'm automating my changes and the developers don't have to manually create them and manage them there's a time saving aspect and a Roi that we can track in terms of developer hours saved down here and that is configurable for each customer so you can plug in figures which meet your organization's needs and track that I'm also able to break break any of these uh dashboards down via these buttons at the top which will make more granular filtering on all the dashboards in terms of application repository service business app products date range Etc the accelerate metrics if you're familiar with devops you might have heard of the Dora the Google Dora metrics which are the four key metrics that have been used as industry standard in terms of how teams are doing with their devops so things like lead time deployment frequency mean time to restore and failure rate so those are the key Dora metrics that are shown here quality metrics are all about your quality of your your code that's been delivered in terms of the coverage testing bugs vulnerabilities Etc and this is where I can dive into my insights on my developers and see how how they are performing in terms of commit frequency active committers reverters uh Etc so all that data is there pipeline pass percentage uh commits without work items that's an important one I don't have any data for this one but that's an important one and then finally operational stability so obviously you know we want to deploy quickly but we also want to make sure we're not breaking things when we deploy and causing incidents and outages and affecting service availability so though that can be tracked as well okay so that's insights let's jump back here so the next one here is my application application tab so the application tab just gives me easy access to all my devops applications and their Associated data so just for example I'll show you this one I can see this application and I can see I've got some plans and and Repository a code repository and pipelines for for this particular application this one happens to be Azure devops so I'm able to see the data that's associated with that and and drill in so for example with this particular pipeline I can look at in more details about that pipeline I can actually view the pipeline and how it's how it's been running so I can see my pipeline execution history and that this last one passed and these are the steps and this is all the data the artifacts the commits if I had any work items Etc that are associated and even the change request that's associated with that particular pipeline so that is the applications section and then on the tools section obviously this is more detailed so again you know my planning tools so I can see in this case I've got Ado and I've got jira I can look at my coding tools and my orchestration tools Etc so that's all there and again I can I can run the Playbook from here to connect any new tools and then finally I've got an Administration section and this is really for the devops the servicenow devops admin so this gives me a wealth of data in terms of the health of my system looking at whether I've got any errors anything that's waiting my tool connectivity if I do have any issues I've got error logs inbound events Etc that I can look at I've got properties that I can manage and I can again do my onboarding via these links my user roles group roles Etc so that really allows me to do all my system Health checking my troubleshooting and configure my system properties and onboarding from from this particular section so all in all what what the workspace gives us is is a whole set of tools in one place that allows me and the people in my organization to quickly onboard and make good use of devops track how we're doing and do it in such a way that it's it's easy to get started so that that's really uh the intent here okay I'm gonna stop sharing there and jump back to my slides uh do we have any questions at this point okay so just share again okay so time for another poll now that you've had a look at the workspace and hopefully got a better idea of what it's all about I know some of you have made a start and some of you said that um you had you had a little usage so what do you think now um after having a look at it let me just launch that poll okay so please answer uh this one uh very keen to get your feedback on what you will do next now that you have the info okay we've got two responses so far please everyone make sure you respond give it another 20 seconds okay we've got a couple of people haven't responded yet please respond if you can okay let's end it there share the results okay so looks like one person needs a little bit more detail that's fine absolutely fine please make sure you send us in the chat your email address and we will get back to you uh or happy for you to come off mute and ask questions now if we can answer them we certainly will and then we've got some people saying you're not ready to use devops change so yep that's fine it's a journey and then one person saying looks great wanna make a start fantastic very happy to hear that okay thanks very much for that okay what I also have in here is um some links to resources we will send out the pack uh to everyone who's attended so if you want to get started and you're not sure where to start or you do need more information there's a lot of information that's out there on customer success Center there's some training that you can do on our learning portal we have some community links that have a wealth of information attached to them on how to get started and what you should do if you're kicking off a devops project and we have a bunch of other videos that you can look at which um go through some demos and and and dive into some more detail about about the devops products so we'll send those out so you can have a look at those so any final questions uh I can't do we have okay I see a lay pair um you just said yes I'm not sure what the yes refers to did you need did you have a question or did you need some help hey Mike thanks for the explanation no uh the yes was earlier um just answer that when you share your screen reader we can see that awesome all right great thank you sorry I couldn't see that when I was presenting fantastic okay um thank you very much for attending everyone um we will send out the link to this once it's ready and um we're very keen as I said to make sure that our customers get started with devops if you do need any help absolutely happy to help you so please reach out and let us know