Release planning or PI planning is common place practice for scaled scrum teams. Typically this planning is done for a duration (quarter) or for specific number of sprints (5 sprints). Available work in the product backlog is distributed within teams and tagged to specific sprints. Work is priorities according to target release (fix version). Typically before this release planning the available work is already prioritized in the product backlog. The premise of this article is to discuss how to track the success of release planning after the actual planning meeting. What are the appropriate metrics and reports to be used to justify plan versus actual and the ROI for management for investing in release planning meetings. (Release planning meeting could be huge investment, e.g. 100 members team in planning meeting for two days is 1600 hours; plan logistics etc.).