Don’t plan activities for your Iteration & Planning (IP) iteration, it’s meant for other activities.
Let me explain:
In Scaled agile, sprints / iterations are clubbed into ‘Program Increments’ (PIs), typically span over 6 sprints.
Priorities, dependencies for the whole PI are planned in what is called PI planning
In a PI, the last sprint is usually called an IP sprint
Typical activities in an IP sprint are to:
– prepare for system demo,
– Inspect & adapt workshop (Retro for the PI),
– Continuous education & learning,
– Pre-PI planning activities
Therefore it’s not a good practice to plan work in the IP sprint and you might want to reserve that capacity for above mentioned activities.