Improvements to project board workshop

We ran the first project board workshop this weekend (https://github.com/CodeYourFuture/curriculum/issues/1347). People found it _really_ useful, and wish they'd done it earlier in ITP. We had volunteers giving a lot of really useful context about how they plan

Some points of feedback we could improve:
* People didn't understand why they were taking on roles of developers / QA - we should better expectation set "We're going to pretend to be in a planning meeting" or similar.
* Most people in the group didn't know what QA is. We should explain this - both expand the acronym, and explain briefly what the role is and why it is relevant to this exercise.
* We may want to prompt volunteers to share different ways they plan in their teams explicitly - our volunteers happened to, but I can imagine groups where the volunteers try to stick more precisely to the script, and don't share as much real-world context.
* The bullet point "What information could help us decide when we’re not sure?" - is implicit about what it's asking about (that it refers to the bullet point before). We should either clarify this in the bullet point, or combine it with the previous bullet point.
* People don't actually need to copy the miro board, just open it - let's stop telling them to copy it, because that involves permissions.

cc @kfklein15