From 103ebd65473d16c16145fdbf0b9fb34932f7000a Mon Sep 17 00:00:00 2001 From: Sally McGrath Date: Sun, 21 Jan 2024 08:52:42 -0700 Subject: [PATCH] for some reason this snippet thing never updates I guess I just don't understand git... --- .../en/blocks/requirements/index.md | 49 ------------------- .../en/blocks/user-stories/index.md | 2 - .../en/module/portfolio/requirements/index.md | 2 - .../portfolio/sprints/1/day-plan/index.md | 3 ++ 4 files changed, 3 insertions(+), 53 deletions(-) diff --git a/common-content/en/blocks/requirements/index.md b/common-content/en/blocks/requirements/index.md index 7e8784fe2..ad2a00563 100644 --- a/common-content/en/blocks/requirements/index.md +++ b/common-content/en/blocks/requirements/index.md @@ -31,52 +31,3 @@ We're going to think about a few projects and discover some requirements. This i {{}} To make great software, we need to think about people, not just code. {{}} - -### User Stories - -We can discover requirements with something called 'User Stories'. The simplest user story looks like this: - -> As a [type of user], I can [achieve some goal]. - -#### Imagine a coursework tracker - -As trainees, you have coursework to do. Imagine a website which tracks how coursework is going for you all. Thinking about that website, some user stories could be: - -- As a trainee, I can ask for help with a topic or task. -- As a mentor, I can see who needs extra support. -- As a trainee, I can see what coursework I need to complete and when. -- As a mentor, I can see what coursework has not been completed. - -These each take the form "As [who], I can [what]". They don't say why yet. - -{{}} -In groups of about 5. - -Talk about why the "who" is useful. What would we be missing if we didn't think about the "Who"? - -Now think about the "why" for each of the listed user stories. Why are they important? - -{{}} - -> As a [who], I can [what] so that **[why]** - -{{}} - -Write some user stories for our coursework tracker on a Jamboard. - -Think about the "who", "what", and "why" for each. - -You can think of new "who"s (e.g. the people who write the coursework questions), and as many "what"s as you want - but make sure you remember the "why". -{{}} - -### Reflecting - -{{}} -A user story is a short sentence stating some goal a user can expect to achieve when using the product we are implementing. -{{}} - -{{}} -Why is thinking about user stories useful? - -What's useful about thinking about the "who" and the "why"? What could go wrong if you don't think about them? -{{}} diff --git a/common-content/en/blocks/user-stories/index.md b/common-content/en/blocks/user-stories/index.md index 023f6a43d..219a769b9 100644 --- a/common-content/en/blocks/user-stories/index.md +++ b/common-content/en/blocks/user-stories/index.md @@ -12,8 +12,6 @@ emoji= '🧩' 4='Translate requirements into high-level design outlines' +++ -{{< snippet "snippets/requirements.md" >}} - #### Imagine a coursework tracker As trainees, you have coursework to do. Imagine a website which tracks how coursework is going for you all. Thinking about that website, some user stories could be: diff --git a/common-content/en/module/portfolio/requirements/index.md b/common-content/en/module/portfolio/requirements/index.md index e05fa07e5..3827bee6d 100644 --- a/common-content/en/module/portfolio/requirements/index.md +++ b/common-content/en/module/portfolio/requirements/index.md @@ -9,8 +9,6 @@ emoji= '🧩' 2='Identify and explain the key user stories for your project' +++ -{{< snippet "snippets/requirements.md" >}} - In addition to [who] and [what], good user stories also include [why] > As a [who], I can [what] so that **[why]** diff --git a/org-cyf/content/portfolio/sprints/1/day-plan/index.md b/org-cyf/content/portfolio/sprints/1/day-plan/index.md index 84e874bf7..2dc2f01fb 100644 --- a/org-cyf/content/portfolio/sprints/1/day-plan/index.md +++ b/org-cyf/content/portfolio/sprints/1/day-plan/index.md @@ -25,6 +25,9 @@ src="blocks/morning-break" name="Gathering requirements" src="blocks/requirements" [[blocks]] +name="User stories" +src="blocks/user-stories" +[[blocks]] name="Choosing a project" src="module/portfolio/requirements" [[blocks]]