Timebox Planning Widget @IBM InterConnect 2015 - Las Vegas

Editor's Notes

• #2: Welcome and Introduction:“Grüetzi mitenand”Good afternoon ladies and gentlemenThis was Swiss German and means “hello everybody”My name is Markus Giacomuzzi and I am from Siemens Building Technologies Headquarters in Zug, SwitzerlandI am a Scrum Master of a Java Application Software TeamIn this team we are building Software for Fire Safety Systems Purpose:I‘m going to talk about how we plan our project portfolio agile with the „Timebox Planning View„ in RTCThe “Timebox Planning View” is what you see in the background of this slideWhy am I here?I am here because I’m the Product Owner of this “Timebox Planning View” which we implemented as a native RTC widget and rolled it out in the Project Portfolio
• #3: Structure:In the first part of my presentation I will give you a few basic definitions and an example. In the second part I will explain the features and show you a demo.
• #4: Good practice: repeat the questionI would like to give you the possibility to ask questions if something is not clear.So please feel free to ask questions anytime
• #5: Attention grabbing Question:I’m sure all of you are familiar with TETRIS So the question is what level do you think this TETRIS might be?Do we all agree it’s a very basic level? YES or NO?Can we agree to Level Preschool?So next, let’s decorate this TETRIS
• #6: We call the colorful boxes stories The height corresponds to the number of Story Points At the bottom we add the Sprints A stable SCRUM team knows its velocity, so let‘s add a horizontal dashed line  What we now see is what we call the Timebox Planning View
• #7: Who does not agree with this statement?
• #8: How can we transform the Team Backlog into the Timebox Planning View? On the left hand side we have a typical ranked team backlog In addition to the ranking, we visualize also the story points as height of the Story If we use the team‘s velocity we get a glue where we will end up
• #9: Solution:The „Timebox Planning View“ helps Project Leaders to master plans even if they are quite complex with lots of dependencies.But before we go to this widget let’s have a look at another example
• #10: This example tells the story of our product portfolio Field issues  Service Release Introduce a new project > 1 team: it makes it much easier if all teams sprint synchronized
• #11: These stories make up the System Feature Mind: These stories belong to different teams and have been realized in different sprints
• #12: How does this look like in the real Timebox Planning WidgetAll the highlighted stories are parent-child-linked to the System Feature This is now a good point to make the transition to show you the Timebox Planning Widget Features
• #13: Here we are in RTCIf we maximize this widget we get to the detailed view
• #14: We see the Sprints at the bottom
• #20: Add widget, choose query, set „team“ view, then SAVE dashboard set color for team and project, then SAVE dashboard Clone Search for „clone“ Pop-up editor: change # of story points 2->5 and change Summary to „Implementation“ Drag & drop Presentation mode Show siblings (double click or in the Menu)
• #21: Who does not agree with this statement?
• #22: Good practice: repeat the questionI would like to give you the possibility to ask questions if something is not clear.So please feel free to ask questions anytime
• #23: Who does not agree with this statement?