---
# System prepended metadata

title: TA Instructions for bootcamp 1

---

# TA Instructions for bootcamp 1

With students do the following steps:

Introduction
--- 

1. Explain the goal of the exercise sessions, e.g. to have the chance to practice some of the core methods in UX design. Explain that selecting the right method is very context dependent. Therefore, in this course students will be asked to select the methods they want to use. We have produced a guidebook both for methods that will be practiced in class and additional ones that can be done in own time. Additionally, students can find and use their own methods.
2. Share your screen and go to the [Introduction](https://hackmd.io/@UED24/HkJLCPFuT) of the guidebook
3. Briefly introduce the HackMD guidebook and how it is intended as a way to keep important information in one place as well as to support in-class exercises
4. Go to the [UX and Usability Requirements](https://hackmd.io/@UED24/H1Ctevau6) page. Show how the requirements are listed here and remind about using consistent terminology when talking about UX and usability goals. There is no need to go through each requirement in detail.
5. Go to the [User requirements](https://hackmd.io/@UED24/Sy_uFBT_a) page. Briefly summarise the content and how to informally or formally express requirements, e.g. through user stories.
6. Remind that a key goal of UX design methods is to elicit new user requirements as well as validate proposed features or design decisions.

Tasks
--- 
**TASK ONE**
7. Divide students into small groups
8. Still on the same page, go to Task One, river crossing challenge. Explain the task to students. Decide how much time you want to give for students to complete the task (timings are indicative but not strict so you can adjust according to how much time is available). 
9. After students have tackled the task, you can decide depending on number of students/mode (e.g. FTF or online) how to mediate a brief discussion. For example;
    a. Lead from the front, and select a group to present ideas. Ask who has same ideas as first group. Ask if groups had any different ideas. **Summarise** by pointing out that while it is fun to jump into the solution, there are too many unknowns on who would use the river crossing, budget and time constraints, or similar, to be able to choose the best one.   
    b. ask students to assess another groups work (e.g. online in Miro)
    c. ask each group to find another group to work with to go through their proposed solutions and ask questions/critique them (FTF mode only)
    **TASK TWO**
9. Still on same page, go to TASK Two. Explain the task to students.
10. As before, spend 5 minutes or so on feedback sharing
11. **Key findings/summaries** could be how to express the informally stated requirements as more formal user stories. Also, discuss that the requirements might still be based around a quite narrow group of stakeholders. Caution against jumping too quickly from requirements to solutions.
 **TASK THREE**
12. Go to the page on [Problem Statements](https://hackmd.io/@UED24/HyapRwY_6) 
13. If there is time, do Task 3 as outlined on the page, otherwise summarise the importance of making probem statements user centred rather than solution centred.
 **TASK FOUR**
1.  Go to the page on [personas](https://hackmd.io/@UED24/H1wfnh9up) 
2.  Briefly introduce/flag the content in the page, e.g. background to personas, critiques.
3.  Direct students to do the persona task in their groups
4.  Summarise by pointing out and giving example on how a personas could be used to find user requirements which can be represented as a user story (use example from the page if you don't have one from the groups).


###### tags: `instructions'