Don’t plan activities for your Iteration & Planning (IP) iteration, it’s meant for other activities.<\/p>\n
Let me explain:<\/p>\n
In Scaled agile, sprints \/ iterations are clubbed into ‘Program Increments’ (PIs), typically span over 6 sprints.<\/p>\n
Priorities, dependencies for the whole PI are planned in what is called PI planning<\/p>\n
In a PI, the last sprint is usually called an IP sprint<\/p>\n
Typical activities in an IP sprint are to:
\n– prepare for system demo,
\n– Inspect & adapt workshop (Retro for the PI),
\n– Continuous education & learning,
\n– Pre-PI planning activities<\/p>\n
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.<\/p>\n
More here:<\/p>\n