hello i'm deborah mcgrath senior technical product marketing manager at servicenow in this video i'll be demonstrating servicenow scrum programs for centralized planning across multiple agile teams we'll see how this works while logged into the agile development application as a product owner eileen motern eileen begins by selecting the agile board on the program tab scrum program's backlog elene views her backlog of epics from here she can manage existing epic backlogs create new epic backlogs edit an epic backlog or create a new epic and stack rank epics in order of importance eileen will now look at the scrum program's planning board to get a full visualization of the plans for all the development teams involved with their hr employee engagement program each of the teams working on the program has a row on the board with several sprints and based on a timeline shown across the top completed or planned stories appear as cards in each of the sprints the location of the card tells which team is doing the work and in which sprint the work is planned an open circle on the card indicates that the work is still in progress and a check mark indicates the story is done each card also shows the name of the story and its estimate in story points by selecting the configuration icon eileen can then toggle to view work dependencies between stories and across teams and checking the team backlog displays the backlog of stories for each team across all epics including stories that were automatically created in the unified backlog from incidents enhancements problems and other types of servicenow tasks eileen wants to plan and schedule the work her teams are doing for the hr employee experience so she filters the program board by that epic backlog to view just that work hr business leaders have asked her to prioritize work on hr profile enhancements and a key related story is currently in the hr delivery team's backlog first eileen will check the overall group capacity of the hr delivery team to do this work she can view existing group members update delete or filter to add other members and update overall group capacity if necessary in addition a red or green gauge on each sprint helps eileen visualize the load of the planned work compared to the team's expected capacity for that sprint a green gauge means the load is less than 100 of capacity the amount filled in along the bar will update automatically to show the capacity remaining as work is added to each sprint eileen clicks into the hr dev sprint 19 to update the hr delivery team's capacity from 45 to 50 points the amount filled in along the gauge is reduced to show this increase in team capacity a red gauge alerts eileen to an issue with sprint 18 hovering over the sprint name shows that the team is overloaded at 102 percent of capacity to fix this she drags the survey questionnaire story out to sprint 19. now in order to accommodate the hr profile prioritization requests from the hr business leaders eileen will drag the related story from the team backlog onto the planning board for consideration a red arrow indicates a cross-team dependency on an hr service portal story and that it's out of sequence so eileen decides to move the hr profile access story to sprint 19 which quickly resolves the dependency issue a red dot indicates this story is blocked and eileen simply hovers over to understand the reason eileen is confident she can plan some additional related hr employee survey work from stories that have not yet been assigned to a team or a sprint she selects the product backlog for a list of hr employee engagement program epics clicks on the hr survey management epic and drags the survey story onto the program planning board assigning it to the hr dev team in sprint 19 where the team still has enough capacity to do that work too for additional information visit servicenow.com spm