Back to Tutorials
10
Videos
18min 48sec
This is Lesson 7 of piplanning.io RTE Cockpit Setup course, in which you will learn how to configure the Program Backlog Board. You'll also get some professional tips on what else to set up for an easier overview of the "taken" Features. Or what to set up so that your teams don't have to duplicate the work by copying sticky notes.
On the Program Backlog Board we can configure several sticky types as usual. Since we have already covered sticky name, color, sticky function and mirror in the previous lessons, I will only go into the exceptions and specialties of the Program Backlog Board configuration. Which in this case only concerns the second color, which is labeled "Taken". Initially all stickies on the Program Backlog have the first color. As soon as a team assigns the sticky to itself, we can define with the "Taken" color which color the sticky will take after this action. This is very helpful for the RTE to keep track of which features are already in planning and which are not. It also shows nicely if the teams first choose the features that have the highest WSJF value or if they decide to simply choose the easiest to implement features. It's a nice way to make it transparent that we're all here to deliver the most value to our customers, not to have the easiest job.
Here is also a personal tip. I always recommend our customers to set “Program & Team Boards” in addition to just “Program Board” in the Mirror setting. Why? Because this way the teams can assign the feature to themselves and also push it to their team board. There it is then also very easy to link the user stories by means of the thread and if desired to visualize super clear feature swimlanes.
After we are done here, press Next.
This 10 lessons course shows you, the RTE & STE on how to set up the RTE Cockpit for PI Planning sessions from the fundamentals to advanced tips. After watching this course you will be able to manage ARTs, invite Users, connect your ALM tool, and prepare a PI session.
Videos
10
Level
Advanced
Length
18min 48sec
Last Updated
Peter Pedross
CEO & Founder PEDCO AG, Chief Methodologist Applied SAFe
Creator of the product Applied SAFe. Started to program for money at the age of 14. Ex-professional sportsman with a passion for software and a knack in engineering. 30+ years working experience with 50+ publications. SAFe SPC since 2011, Agile (XP) since 1999. Happy father and married to a wonderful woman.
Silvio Wandfluh
Head of Product, SPC5
Silvio is a certified SAFe® Program Consultant and as Head of Product at Rentouch responsible for the innovation of piplanning.io.
Shane Harrison
Business and Agile Leadership Coach
Shane is a business focused change agent, specialising in enterprise level digital Lean/Agile transformations. More than 17 years consulting experience across a variety of industries from pharma to banking Shane is a specialist when it comes to context and culture-specific transformations.
Ian J Franks
SAFe® 5 Program Consultant & RTE
Ian has a deep knowledge of Scrum, Kanban and Scaled Agile, and 30 years’ experience in international IT Transformation Programs. He is a successful PO, SM & RTE and as a Consultant/Trainer he coaches his clients develop a strong Agile Mindset that delivers real change and measurable improvements.
We promise not to turn this into a sales pitch – it’s all about helping you and your team decide if piplanning.io is a good match.
Book a Demo