All sprints + minor changes

common-content/en/module/business-analysis/Requirements/index.md

@@ -0,0 +1,24 @@
++++
+title = "Requirements"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Write different types of requirements (functional, non-functional/quality, constraint)"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Read Chapter 1 of the [CPRE Foundation Level](https://cpre.ireb.org/en/downloads-and-resources/downloads#cpre-foundation-level-handbook). 
+
+Learn the definition of a requirement and note that Requirements Engineering is another term for a role involving Business Analysis competencies. 
+
+Note also the different types of requirements and that Quality Requirement is another term for [Non-Functional Requirement](https://en.wikipedia.org/wiki/Non-functional_requirement).
+
+1. Suggest at least two functional requirements for BrightStar based on your analysis up to now 
+2. Suggest at least two non-functional (quality) requirements.
+
+

common-content/en/module/business-analysis/acceptance-criteria/index.md

@@ -0,0 +1,21 @@
++++
+title = "Acceptance criteria"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Write clear acceptance criteria"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Read about [acceptance criteria](https://resources.scrumalliance.org/Article/need-know-acceptance-criteria) and how user stories can be made both more measurable and clearly understandable for developers. 
+
+For one of the user stories that you have so far identified for BrightStar, suggest 3 or more acceptance criteria.
+
+
+
+

common-content/en/module/business-analysis/agile/index.md

@@ -0,0 +1,18 @@
++++
+title = "Agile and others"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Explain the differences between agile and scrum",
+    "Describe how sprints and iterations are different"
+
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Understand the [Agile](https://youtu.be/Z9QbYZh1YXY?si=YDtrkFHORJ000z8s)/[Scrum](https://youtu.be/TRcReyRYIMg?si=ZE2sFQcwHh3oWTc5) principle, including Sprints, Iterations, Releases, [Backlog](https://www.aha.io/roadmapping/guide/release-management/product-release-sprint-backlog), etc.
+

common-content/en/module/business-analysis/business-domain/index.md

@@ -0,0 +1,20 @@
++++
+title = "Business domains"
+
+time = 90
+emoji = "🤖"
+objectives = [
+    "Identify key terms in the business domain",
+    "Represent the relationships among key entities in the domain in a conceptual data model (business domain model)"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Learn about the importance of terminology and how to use glossaries, data dictionaries and conceptual data models (business domain models) - use this [business analyst glossary](https://www.businessanalyststoolkit.com/business-analysis-glossary-of-terms-and-acronyms/) as an example. This is a [data dictionary](https://thebadoc.com/ba-techniques/f/defining-a-data-dictionary) and [data modelling](https://www.techtarget.com/searchdatamanagement/tip/7-data-modeling-techniques-and-concepts-for-business) you can refer to. 
+
+1. Write a glossary for a particular domain of interest within BrightStar
+2. Identify key business entities in that domain
+3. Create a simple data model using those entities - complete the first two sections (Intro & Data Modelling Fundamentals) of [this Udemy course](https://codeyourfuture.udemy.com/course/mastering-data-modeling-fundamentals/)

common-content/en/module/business-analysis/business-process-model/index.md

@@ -0,0 +1,18 @@
++++
+title = "Business process model"
+
+time = 90
+emoji = "🤖"
+objectives = [
+    "Represent the business’s internal processes as business process models using an appropriate notation (eg, UML activity diagrams or BPMN)"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Learn about business process modelling and notations used for this (eg, BPMN, UML). You can do the [Udemy crash course](https://codeyourfuture.udemy.com/course/business-process-mapping-and-modelling-crash-course/) for BPMN and understand the differences in [this article](https://miro.com/diagramming/bpmn-vs-uml/).
+
+1. Create a simple business process model for one existing business process within BrightStar
+2. Use swimlanes within the model to show where the responsibility for carrying out individual steps lies, taking care that swimlanes represent organisational units (organisation, department, role) and not systems

common-content/en/module/business-analysis/change-mgmt/index.md

@@ -0,0 +1,30 @@
++++
+title = "Change management"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "List relevant tasks a business analyst will support a change management team with",
+    "Apply scope changes to a project"
+
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Understand:
+- What is [change management](https://youtu.be/wxVgd8h1svU?si=3ckqHAce9mg_zzhA)? 
+- What is the difference between change management and organisational change management?
+- What are [scope changes](https://www.lucidchart.com/blog/scope-change-management), and how should you deal with them?
+
+1. Write a list of how you, as a Business Analyst, can support change management and the rollout of a project.
+
+2. Explain the difference of change management and organisational change management.
+
+3. Idenitfy possible scope changes that could happen on the use case you are working on. How would you deal with them? And who would have to be informed?
+
+4. Outline 3 ways a BA would support the launch (rollout activities).
+
+

common-content/en/module/business-analysis/data-modelling/index.md

@@ -0,0 +1,22 @@
++++
+title = "Data modelling"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Create a conceptual data model",
+    "Apply the relevant notations including ERD’s diagrams.",
+    "Explain the difference between business process models and the processes or workflows used in system design"
+
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Build on your existing knowledge of data modelling by completing section 3 (The Building Blocks of Data Modelling) of this [Udemy course](https://codeyourfuture.udemy.com/course/mastering-data-modeling-fundamentals/)
+
+1. Create a simple logical data model for the solution proposed in your storyboard above
+
+

common-content/en/module/business-analysis/demo/index.md

@@ -0,0 +1,60 @@
++++
+title="Demo"
+time=45
+tasks = [
+    "Explain your work to others at CEFR B2 level or higher.",
+    "Listen and understand standard speech spoken at a normal rate and follow even complex lines of argument provided the topic is reasonably familiar",
+    "Participate in meetings in your area of expertise, if you have help understanding some points.",
+    "Ask clarifying questions and revise your response based on new information.",
+]
+[build]
+  render = 'never'
+  list = 'local'
+  publishResources = false
++++
+
+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 {{<timer>}}10{{</timer>}}
+
+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 {{<timer>}}5{{</timer>}}
+
+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.
+<dl class="c-rubric">
+  <dt>Clearly introduce the topic to the stakeholders (aka the group).</dt><dd>Someone watching should be able to approve the next steps.<br /><br />The topic <strong>must not</strong> 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.</dd>
+  <dt>Explain what was done</dt><dd>Someone watching should be able to state what you have done in one sentence.</dd>
+  <dt>Explain the reasoning behind a choice.</dt><dd>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).</dd>
+  <dt>Show relevant artifacts (e.g. business mapping, data mapping, user story).</dt><dd>Someone watching should be able to identify at least one artifact of your work. Slides don't count as an artifact.</dd>
+  <dt>Stick to your time limit.</dt><dd>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.</dd>
+  <dt>Get buy in.</dt><dd>The stakeholders should leave your presentation satisfied with the outcome and direction.</dd>
+</dl>

common-content/en/module/business-analysis/design-mindset/index.md

@@ -0,0 +1,19 @@
++++
+title = "Design mindset"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Explain the difference between analysis and design"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+As we make a subtle switch from an analysis to a design mindset, watch this short motivator from [Steve Job](https://youtu.be/y1Yow6rd-lw?si=7hZY462MTHIe6iy1)s.
+
+
+
+

common-content/en/module/business-analysis/design-principles/index.md

@@ -0,0 +1,21 @@
++++
+title = "Design princples"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Explain the princples of a good design "
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+The principles of good design extend beyond software design, as you can read about with the [Bauhaus School](https://www.theinteriordesigninstitute.com/us/en/blog-bauhaus-design) or [James Dyson](https://medium.com/@ajal.connect/the-genius-of-james-dyson-revolutionizing-design-in-the-household-17e8351958fa) or again from [Steve Jobs](https://fs.blog/steve-jobs-on-design/). 
+
+1. What common universal design principles are shared among these examples?
+
+2. How might these apply in the context of software development? 
+
+3. Compare your answers with these ideas from the [Digital Design Manifesto](https://ddp.ireb.org/en/downloads-and-resources/downloads#digital-design-manifest)? 

common-content/en/module/business-analysis/design-solution/index.md

@@ -0,0 +1,22 @@
++++
+title = "Design a solution"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Design a solution for the use case"
+
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Considering all the content of your the use case, can you design a possible solution for it? 
+
+This can include any of the design elements (eg. storyboards, use cases, functional architecture, data models or class diagrams) already provided above or additional ones. 
+
+Pull these together to produce a coherent overall picture of your solution, which you are able to present.
+
+

common-content/en/module/business-analysis/epics/index.md

@@ -0,0 +1,26 @@
++++
+title = "Epics and features"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Describe requirements at high level or in more detail (levels of granularity)", 
+    "Write epics, features and stories"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Find some examples of epics, features and user stories. This [resource](https://scrum-master.org/en/epic-feature-and-user-story-in-agile-a-beginners-guide/) may be helpful.
+
+1. Suggest a list of epics for an improved solution within BrightStar
+
+2. Supposing you had limited resources for a first implementation of these changes, decide which of these epics would initially be in scope and justify this choice
+
+3. For one of your epics derive multiple features
+
+4. Show how your lower-level technical requirements can be traced back to higher-level business needs (traceability)
+
+

common-content/en/module/business-analysis/functional-architechture/index.md

@@ -0,0 +1,23 @@
++++
+title = "Functional architechture"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Describe what is functional architecture",
+    "Allocate required functionalities to modules or components within such as architecture"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+[This page](https://mrsdprojects.ri.cmu.edu/2020teamb/design/functional-architecture/) has an example of a functional architecture. Can you find any more? 
+
+1. Using one example of a functional architecture, show what universal design principles have (or have not!) been followed 
+
+2. Propose a functional architecture for part (or all) of the BrightStar solution 
+
+3. Describe the interaction among two or more component modules within your functional architecture using a sequence diagram
+

common-content/en/module/business-analysis/measure-success/index.md

@@ -0,0 +1,22 @@
++++
+title = "Measure success"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Explain the difference between OKR and KPI",
+    "Propose relevant success metrics for a project",
+    "Identify data sources for success metrics"
+
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+How do you measure success in deliveries? Read about OKRs and KPIs on [this page](https://agilemania.com/difference-between-okr-vs-kpi#:~:text=OKRs%20involve%20setting%20new%20objectives,collaborate%20on%20defining%20relevant%20KPIs.). 
+
+1. Propose 4 ways to measure your use case's success if it's successful 
+
+2. Explain where you'd get the information (i.e. data sources). 

common-content/en/module/business-analysis/new-use-case/index.md

@@ -0,0 +1,24 @@
+
++++
+title = "New use case"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Implement BA tools you learned in a project"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+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)?