for some reason this snippet thing never updates

I guess I just don't understand git...
CodeYourFuture · Jan 21, 2024 · 103ebd6 · 103ebd6
1 parent a401241
commit 103ebd6
Show file tree

Hide file tree

Showing 4 changed files with 3 additions and 53 deletions.
diff --git 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
 {{<note type="tip" title="Remember" >}}
 To make great software, we need to think about people, not just code.
 {{</note>}}
-
-### 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.
-
-{{<note type="activity" title="Exercise 10 Minutes" >}}
-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?
-
-{{</note>}}
-
-> As a [who], I can [what] so that **[why]**
-
-{{<note type="activity" title="Exercise 10 Minutes" >}}
-
-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".
-{{</note>}}
-
-### Reflecting
-
-{{<note type="glossary" title="Key Term" >}}
-A user story is a short sentence stating some goal a user can expect to achieve when using the product we are implementing.
-{{</note>}}
-
-{{<note type="activity" title="10 Minutes" >}}
-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?
-{{</note>}}
diff --git 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
@@ -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
@@ -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]]