Once you save your page, Confluence will use the page properties report macro to create an index of all the retrospectives in the space and add it to your sidebar:
How to use retrospectives
Host a retrospective at the end of each sprint or project to discuss what worked well and what could be improved. Write a wrap-up post about what you learn, and use those lessons to come up with a plan for making the next cycle more effective and efficient.
Tailor retrospectives to your working style. If your team's workflow is continuous and fluid, schedule retrospectives quarterly or even monthly to maintain accountability and growth. Focus on the overall process your team has followed since the last retrospective and try not to get caught up in the nitty-gritty details.
Run a retrospective whenever you finish rolling out a major initiative. Schedule a full hour and use that time to focus on how you worked together as a team and how that can inform your work together in the future, rather than the particulars of the rollout itself.
For more guidance on how you can use retrospectives with different teams, check out the retrospective play in the Atlassian playbook.
Customize your retrospectives
Retrospectives are created from a blueprint template, which means they come bundled with Confluence and are available across your whole site. Blueprint templates can be customized for each space, and the site admin can even change the default blueprint template for your whole site. To learn more about customizing blueprint templates or creating your own templates, see Blueprints and user-created templates.