How do you integrate Whiteboards in your Atlassian product use?

[Valerie Knapp]

I have seen some people writing and talking about using Whiteboards for different ceremonies, like a Retrospective. Does anyone have Whiteboards fully integrated into their ways of working, for example, write requirements in Confluence, transform into Jira issues and use Whiteboards to review a Sprint?

[James Rickards _Spark-Nel_]

Back when I was working with Deloitte, I used whiteboards to fully drive our Server to Cloud migration project. 300 live client projects and 3000 users.

I insisted the team use of whiteboards for:

• project induction and ensuring project goals / OKRs
• initial architectural and later the detailed design diagrams
• workshop to create the Work Break Down structure for the project phases and tasks, then creation of a story map for requirements best suited for that format
• kanban / scrum board to support daily planning and ensuring we aligned to the goals 
• risk management, and continuous improvement 
• fortnightly retrospectives
• a visual representation of Jira config settings to support a security audit
  • screenshots of the config pages, with lines drawn out from each setting to a card linking to the relevant wiki page about the setting and findings from the audit, and decisions around what to set there
• a visual map linking screenshots of settings to wiki pages about change control rules and nomenclature (e.g. name of workflows, screens etc)

This was all before Whiteboards were released to the public and have some of the more modern features.