hello i'm deborah mcgrath senior technical product marketing manager at servicenow over the next five minutes i'll be demonstrating servicenow scrum programs for centralized planning across multiple agile teams often organizations have multiple agile teams working collaboratively to achieve common outcomes but using the scaled agile framework is not yet an option scrum programs provides a solution for this by enabling organizations to see multiple agile teams in a single view to understand which teams are contributing and when it lets them view and manage dependencies across teams and it gives them visibility into the load on each team compared to its capacity we'll see how this works while logged into the agile development 2.0 application as a program manager eileen motern agile 2.0 now provides two tabs program and team the team tab enables program managers like eileen and their teams to manage their individual backlog of stories and do sprint planning and sprint tracking the program level is where work is then organized and prepared across teams from the scrum program's backlog tab eileen is now viewing her backlog of epics taking note that these are indeed epics not stories from here she can choose from existing epic backlogs create new epic backlogs or edit them epic backlogs or simply filters on epex constructed with the standard servicenow condition builder eileen can also configure the display list as needed filter by product or search term add and update epics decompose epics into stories and stack rank epics in order of importance she'll now look at the scrum program's planning board to get a full visualization of the plans for all the teams involved in their hr employee engagement program each of the teams in the program has a row on the board and along the timeline shown across the top we see the sprints for each of the teams eileen can switch to look at the planning board for another program she can zoom in and out to see more or less of the picture and she can go forward on the timeline as well as back in time to view her team's plans synchronized sprints are not required for servicenow scrum programs they can start and end at different times have different lengths and have different names the planned work is shown on story cards 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 shows that the work is still in progress while a check mark indicates that the story is done each card also shows the name of the story and its estimate in story points a red or green gauge on each sprint shows 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 one hundred percent of the capacity and the amount filled in along the bar gives a visual cue to the amount of capacity remaining the red gauge alerts eileen that the load exceeds the team's capacity to do all the work currently in this sprint and as she hovers over the sprint name she can see more specifically that the team is 105 of capacity and that's not the only issue by toggling the show dependencies icon eileen can view the dependencies between stories and between teams a red arrow indicates a dependency that is out of sequence as shown here to attempt to fix the problems eileen will drag the new hire 90-day survey story from sprint 18 and drop it in sprint 20. unfortunately this pushes sprint 20 to 106 of group capacity so eileen decides to move the story to sprint 21 which appears to have a lesser load as she continues planning eileen can bring the epic backlog interview choose from the epics displayed and drag stories from the backlog to the appropriate teams and sprints on the planning board as stories are planned the gauges continue to update in real time to show how it impacts the team's load we just demonstrated how servicenow scrum programs gives organizations greater visibility into teams which helps them keep an eye on the plans for all the teams involved in a program scrum programs provides a single centralized view for realistic planning across multiple agile teams that enables program managers to keep dependencies properly sequenced and prevents them from overloading their teams for additional information visit servicenow.com itbm you