hello i'm deborah mcgrath senior technical product marketing manager at servicenow over the next few minutes i'll be demonstrating our microsoft azure devops integration for servicenow agile development which enables bi-directional synchronization between both systems if you're planning development work in servicenow itbm but your development teams are executing that work in microsoft azure devops or ado it can be challenging to keep switching back and forth between both systems to try to get a clear understanding of the overall project works status it would be preferable to have a single system of record where users don't have to swivel chair between two systems to get the full picture the servicenow agile development for ado solves this by letting teams continue to work in their product of choice while keeping data in sync it brings work from one system into another with configurable data types and it provides progress and status back to servicenow in context of the work by automatically synchronizing work status at the program or portfolio level we'll view the demo from two different perspectives logged into servicenow as eileen motern a product owner who is responsible for tracking product progress and who relies on the servicenow agile board to get visibility into her team's capacity to do work manage their backlog of stories and to do sprint planning and sprint tracking and we'll log into microsoft azure devops as a developer on one of eileen's teams the hr delivery team this team uses ado to plan build and track their work let's see how the agile development ado integration keeps the hr development team and the product owner on the same page as they make changes and updates in both systems beginning on the servicenow agile board the product owner eileen has selected the hr employee engagement program to review the stories being developed the teams working on those stories and the cross dependencies between them she wants to review the progress of the hr delivery team which is developing many important hr employee engagement product features they've been working on a total of 13 stories across five sprints including a highly anticipated new hire 90-day survey capability and four other stories in sprint 18. meanwhile the developers on the hr delivery team are viewing these stories in microsoft azure devops and they see the same 13 stories and the same story sequencing across each of the five sprints including the new higher 90 day survey and four additional stories in sprint 18. they have nothing currently planned in sprint 21. back in servicenow the timeline across the top shows eileen when each of the sprints is planned a red or green gauge on each sprint shows her the load of the planned work compared to the team's expected capacity for that sprint and the amount filled in along the bar gives a visual cue to the amount of capacity remaining eileen immediately notices a few issues that will require adjustments first the red dependency line alerts eileen to a sequencing issue the new hire 90-day survey story is dependent on the completion of the new hire survey page story but it's in the previous sprint the solid red line below hr dev sprint 18 indicates the second issue that the team is overloaded the five stories in sprint 18 exceed the hr delivery team's capacity to do the work in that sprint to fix the problems eileen will drag the new hire 90-day survey story out to sprint 20 which has a green gauge indicating that the load is less than 100 of capacity this fixes the sequencing issue and sprint 18 is now within the team's capacity but unfortunately the move causes sprint 20 to become overloaded after some consideration she'll drag the performance bonus plan story out to sprint 21 to resolve this and now all sprints are within the team's capacity to do the work the hr delivery team developers will automatically see all of these updates as well refreshing the ado backlog developers see that there are now only four stories in sprint 18. the new higher 90 day survey story is now in sprint 20 and sprint 21 which was empty now contains the performance bonus plan story next eileen clicks on the team tab to create and add a new story to the backlog based on an incident related to the existing hr employee engagement program servicenow's unified backlog allows eileen and her team to maintain a centralized backlog containing records of different task types such as defects enhancements problems incidents and stories they do this by setting up triage boards for each specific task type once set up it enables the team to add prioritize and sequence different task type records all in one location to locate the hr incident eileen selects the triage board her team defined for all software incidents she selects the incident hr site careers link missing and adds it to the backlog returning to the agile board eileen clicks on the hr incident which has been added to the bottom of the unified backlog in addition to the incident details a story has automatically been created for the incident this removes the overhead of converting records to stories which saves eileen and her team valuable time and steps she assigns the story to the hr delivery team and gives it two points as expected the ado backlog is automatically synchronized and the hr delivery team also immediately sees the news story in their backlog and of course as developers update stories in azure devops that information will also be reflected back within servicenow for example when the hr delivery team sets both of the stories in hr dev sprint 17 to closed here in ado they'll also be closed in service now eileen now sees a check mark on those stories in the servicenow program board indicating that they are complete ado integration for agile development provides eileen and her development teams with the real-time intelligence they need to track status make better business decisions do realistic planning and efficiently execute their work regardless of whether they're working in servicenow agile development or microsoft azure devops we just demonstrated how microsoft azure devops integration for servicenow agile development enables organizations to synchronously plan and work in servicenow agile development along with teams that are executing that work in ado the integration provides bi-directional synchronization that brings work from one system into another with configurable data types and automatically synchronizes work status across both systems for additional information visit servicenow.com itbm you