eileen modern is a product owner at our organization and she's going to do the scrum program planning she's first going to look at the jira board she's going to go to the hr delivery project go into the backlog in the jira backlog eileen can see how the sprints and stories have been configured she sees that the new higher 90 day survey story is currently in sprint 18 and that the performance bonus plan story is currently in sprint 20. she also notices what is currently in her backlog next she's going to move over to servicenow eileen will now open the servicenow scrum program planning this allows the product owner to work collaboratively across agile teams with a central single view that allows for planning all the work of multiple scrum teams including showing dependencies so she'll click on the agile board and she's chosen program and the hr employee engagement program the rows in this view show the teams that are working together on an outcome or the program and within each row are the sprints for each team displayed chronologically within each sprint the stories assigned to each team along with effort and points is shown above each sprint a capacity bar is shown allowing the program manager to see if any sprint is over committed and hovering over the sprint name shows the capacity and points and clicking in would allow for editing and we can see the dependencies between stories even across teams shown by the lines you notice the teams can have different schedules for their sprints and still be part of a consolidated program view now looking at this view we see that there are a couple of issues first the hr dev sprint 18 is over capacity for story points and also the new higher 90s survey story is dependent on the new hire survey page story but is scheduled to be in the previous sprint by moving these stories we can first resolve the dependency issue so let's move new higher 90 day survey over to sprint 20. that's fixed our dependency issue but now we see that hr dev sprint 20 is over capacity then if we move the performance bonus plan over to hrdev sprint 21 that resolves our capacity issue eileen now needs to go back to jira to confirm that the changes have been reflected there so we go back over into jira into our backlog refresh the screen and we can see that the new hire 90 day survey story is now in hr dev sprint 20. and the performance bonus plan is now in hr dev sprint 21. an incident impacting the hr employee service management product has come in and has been assigned eileen she needs to create a story so that a dev team can work on this particular incident so she's going to go back into her program board she's going to move over to the team tab and she has the hr delivery team backlog selected she then will go to the triage board selection selecting the all incidence triads definition presents a user with a list of draft incidents that are candidates to be added to the backlog from here the user can select the incidents and add them to the backlog so first filter the list to see only items that are assigned to her then she will select that incident and add it to the backlog if we return to the backlog selected incident is now visible we can work the incident or any task record in servicenow in the exact same place where we do our agile development these processes are commonly in disparate systems of record but in servicenow they can be harmonized in one place next eileen is going to update the story information for the story that was newly created from the incident on clicking the newly added incident on the backlog a pop-up presents the actual incident record clicking on the story information link enables eileen to create a story directly linked to the incident we're going to add information to the story such as epics points and assign team we see this is already assigned to the hr delivery team we're going to assign it to the hr portal epic and estimate two points click on update then we'll click on this x to go back to our backlog list eileen now needs to confirm that the story that was added to the backlog for the hr delivery team is reflected in jira so she's going to go back over to jira refresh the screen when adding stories to the backlog and servicenow for a team they will also show up in the backlog for that team in jira and there's our story moving stories from a backlog to a sprint could be done in either product however using the servicenow agile board allows planning based on capacity and dependencies next troy mccoy our one of our developers is going to mark one of the stories as complete in jira so he's logged into jira it's going to go to active sprints he's going to move the survey questionnaire story from to do over to done developers can use jira to update their stories and move them to completed via the jira board if we go back to servicenow eileen can see that the story is complete so we'll go back to servicenow go back to our program board we can see a check mark next to survey questionnaire 1 which means the story is complete if we click in and look at the state we see that it is also set to complete this concludes our narrative on the servicenow scrum agile to jira integration thanks for your time