A creative way to practice Slack communication through collaborative storytelling.

1. Facilitator: Create a dedicated thread in your team’s Slack channel.
2. Start with a simple prompt, eg:

• “Time travelers from 2030 visit to study our cohort as the pioneers of the tech industry. What made us so revolutionary?”
• “Scientists accidentally merged all our pets/favorite animals into one super-creature. Describe this majestic beast and its day at the office.”
• “Breaking news: Our entire team just discovered we have superpowers! What powers did each person get and how did we first discover them?”

Now, each person will add one sentence to the story using:

1. 😁 At least one emoji
2. One Slack formatting feature (bold, italic, bullet point)
3. One @mention of another team member, inviting them to continue the story.

Continue for 10 minutes ⏱ or until everyone has contributed.

As a group, work together to create and submit these key documents for a new business scenario. Each person should understand all parts of the submission:

1. A Problem Statement (what the problem is) & Stakeholder Map (who is involved).
2. 2-3 User Personas (descriptions of typical users).
3. An “As-Is” Process or User Journey Diagram (how things currently work).
4. 8-10 Requirements (what the solution needs to do, functional, non-functional).
5. 5 User Stories with acceptance criteria.
6. A high-level Solution Design (how you’d solve the problem).
7. What’s “In-Scope” (what you will do) and “Out-of-Scope” (what you won’t do for this project)?

Every Saturday we cook and eat together. We share our food and our stories. We learn about each other and the world. We build community.

This is everyone’s responsibility, so help with what is needed to make this happen, for example, organising the food, setting up the table, washing up, tidying up, etc. You can do something different every week. You don’t need to be constantly responsible for the same task.

At CYF we expect you to demo your work to the class. You must have many opportunities to practice how to clearly and simply explain your work to others. This is really important skill as a business analyst.

⏰ Timekeeper

The timekeeper will keep the groups on track.

Split randomly into groups of no more than 4 people. Mix up your teams. Each person will have 10 minutes to demo the work they did on the previous prep to the group. After the demo, the group will ask questions or give feedback for 5 minutes. Then the next person will demo their work.

🧑🏼‍🎓 Trainees

1. Demo 10 minutes ⏱

You will demo the work you did for this sprint as if you were presenting it to Brighsparks stakholders.

You will have 10 minutes to explain run the stakeholders through your findings and logic behind it.

2. Feedback 5 minutes ⏱

After the demo, the group will give you feedback for up to 5 minutes. Someone from the group might act as one of the main stakeholders and ask questions.

💡 Tips:

• Practice the format of demos before class.
• Keep it simple. Don’t try to show everything you did. Just show enough so it makes sense and shows progress.
• Keep it short. 10 minutes is enough.
• Explain what you did and why.
• Show the artifcats you created
• Ask for feedback.

Rubric

These are some criteria we will be using to assess your demo. You must meet 5 of the 6 criteria, and if you skip one we recommend you skip asking a question. This is not an ordered list - you can complete these criteria in any order.

Clearly introduce the topic to the stakeholders (aka the group).

Someone watching should be able to approve the next steps.

The topic must not be "I will tell you about my hard work". It must be about how you, as a Business anayst, evaluated and used the knowledge you acquired.

Explain what was done

Someone watching should be able to state what you have done in one sentence.

Explain the reasoning behind a choice.

Someone watching should be able to explain why you did at least one thing a particular way (and why it was a better choice than alternatives).

Show relevant artifacts (e.g. business mapping, data mapping, user story).

Someone watching should be able to identify at least one artifact of your work. Slides don't count as an artifact.

Stick to your time limit.

You should know how long you have for your demo, and stick to that time. You will be given a warning when you're running low on time.

Get buy in.

The stakeholders should leave your presentation satisfied with the outcome and direction.

Please feel comfortable and welcome to pray at this time if this is part of your religion.

If you are breastfeeding and would like a private space, please let us know.

At CYF we expect you to demo your work to the class. You must have many opportunities to practice how to clearly and simply explain your work to others. This is really important skill as a business analyst.

⏰ Timekeeper

The timekeeper will keep the groups on track.

Split randomly into groups of no more than 4 people. Mix up your teams. Each person will have 10 minutes to demo the work they did on the previous prep to the group. After the demo, the group will ask questions or give feedback for 5 minutes. Then the next person will demo their work.

🧑🏼‍🎓 Trainees

1. Demo 10 minutes ⏱

You will demo the work you did for this sprint as if you were presenting it to Brighsparks stakholders.

You will have 10 minutes to explain run the stakeholders through your findings and logic behind it.

2. Feedback 5 minutes ⏱

After the demo, the group will give you feedback for up to 5 minutes. Someone from the group might act as one of the main stakeholders and ask questions.

💡 Tips:

• Practice the format of demos before class.
• Keep it simple. Don’t try to show everything you did. Just show enough so it makes sense and shows progress.
• Keep it short. 10 minutes is enough.
• Explain what you did and why.
• Show the artifcats you created
• Ask for feedback.

Rubric

These are some criteria we will be using to assess your demo. You must meet 5 of the 6 criteria, and if you skip one we recommend you skip asking a question. This is not an ordered list - you can complete these criteria in any order.

Clearly introduce the topic to the stakeholders (aka the group).

Someone watching should be able to approve the next steps.

The topic must not be "I will tell you about my hard work". It must be about how you, as a Business anayst, evaluated and used the knowledge you acquired.

Explain what was done

Someone watching should be able to state what you have done in one sentence.

Explain the reasoning behind a choice.

Someone watching should be able to explain why you did at least one thing a particular way (and why it was a better choice than alternatives).

Show relevant artifacts (e.g. business mapping, data mapping, user story).

Someone watching should be able to identify at least one artifact of your work. Slides don't count as an artifact.

Stick to your time limit.

You should know how long you have for your demo, and stick to that time. You will be given a warning when you're running low on time.

Get buy in.

The stakeholders should leave your presentation satisfied with the outcome and direction.

You are done for the day. Take a moment to reflect on what you have learned and achieved.

Stand in a circle and share:

• 📛 your name
• 💪🏽 one thing you achieved today
• 👷🏾 the task you are going to work on next
• 🛟 one thing you need help with

Give yourselves a round of applause. Now you have earned your rest. Usually people go for a cup of tea or a pint after class. You are welcome to join and wind down together.