IP or QBR planning

[Clayton]

Hi

I am looking to use Plans to help business units execute their increment planning.

I was keen to know if anyone has done this before and if you could share some ideas that worked well.

So far I am thinking of using a plan and customising some fields to contain data such as confidence level, effort vs value matrix and maybe even get some of the data in a dashboard like (risks, high priority blockers etc) 

Would love to hear if anyone has done this and some ideas.

cheers 

[Alexey Pavlenko _App Developer_]

Hi @Clayton ,

If you don't mind I would like to share with you my experience from an adjacent perspective and propose the solution I developed for that.

When planning and scheduling your increment, one of the most important aspects is understanding historical data, as well as the strengths and weaknesses of teams. This helps in assessing capacity, velocity, and other key factors. To achieve this, you need to track, visualize, retrospect, and report on team performance. With my app - Multi-team Scrum Metrics & Retrospective you will be able to:

• Track standard Scrum metrics (Incomplete Scope, Completed Scope/Velocity, Added Scope, ...) or any custom metric constructed using JQL across any periods - sprints, months, quarters, half-years or years for multiple teams in a single view.
• Conduct in-place retrospectives
• Compare metrics between teams or periods
• Identify, quantify, and prioritize reasons behind mediocre performance, and easily justify budget allocation for improvements
• View dynamics between the current and previous periods
• View % of a metric relative to Initial or Final Scope. Average of metrics for the selected periods
• View average of metrics for the selected periods

• Generate retro reports for SAFe, LeSS, SoS, etc. teams to:

  • Compare groups of teams, e.g., Team 1 and Team 5 as one entity versus Team 3 and Team 4 as another.
  • Compare periods, e.g., 2024 vs 2023 for Team 1 and Team 5 combined.

Here is the standard view of it:

Here is summary of metrics:

Best regards,
Alexey