diff --git a/common-content/en/module/business-analysis/Requirements/index.md b/common-content/en/module/business-analysis/Requirements/index.md
new file mode 100644
index 000000000..1c297885e
--- /dev/null
+++ b/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.
+
+
diff --git a/common-content/en/module/business-analysis/acceptance-criteria/index.md b/common-content/en/module/business-analysis/acceptance-criteria/index.md
new file mode 100644
index 000000000..86dad5716
--- /dev/null
+++ b/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.
+
+
+
+  
diff --git a/common-content/en/module/business-analysis/agile/index.md b/common-content/en/module/business-analysis/agile/index.md
new file mode 100644
index 000000000..f7dfa279d
--- /dev/null
+++ b/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.
+
diff --git a/common-content/en/module/business-analysis/business-domain/index.md b/common-content/en/module/business-analysis/business-domain/index.md
new file mode 100644
index 000000000..2480d028e
--- /dev/null
+++ b/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/)
diff --git a/common-content/en/module/business-analysis/business-process-model/index.md b/common-content/en/module/business-analysis/business-process-model/index.md
new file mode 100644
index 000000000..d030bb2c7
--- /dev/null
+++ b/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
diff --git a/common-content/en/module/business-analysis/change-mgmt/index.md b/common-content/en/module/business-analysis/change-mgmt/index.md
new file mode 100644
index 000000000..cefe063ce
--- /dev/null
+++ b/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).
+
+
diff --git a/common-content/en/module/business-analysis/data-modelling/index.md b/common-content/en/module/business-analysis/data-modelling/index.md
new file mode 100644
index 000000000..d4c4675e1
--- /dev/null
+++ b/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
+
+
diff --git a/common-content/en/module/business-analysis/demo/index.md b/common-content/en/module/business-analysis/demo/index.md
new file mode 100644
index 000000000..70dbdfb4b
--- /dev/null
+++ b/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>
\ No newline at end of file
diff --git a/common-content/en/module/business-analysis/design-mindset/index.md b/common-content/en/module/business-analysis/design-mindset/index.md
new file mode 100644
index 000000000..9ca69076c
--- /dev/null
+++ b/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.
+
+
+
+  
diff --git a/common-content/en/module/business-analysis/design-principles/index.md b/common-content/en/module/business-analysis/design-principles/index.md
new file mode 100644
index 000000000..6efc47b5d
--- /dev/null
+++ b/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)? 
\ No newline at end of file
diff --git a/common-content/en/module/business-analysis/design-solution/index.md b/common-content/en/module/business-analysis/design-solution/index.md
new file mode 100644
index 000000000..b33bd6927
--- /dev/null
+++ b/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.
+
+
diff --git a/common-content/en/module/business-analysis/epics/index.md b/common-content/en/module/business-analysis/epics/index.md
new file mode 100644
index 000000000..3be00ca0a
--- /dev/null
+++ b/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)
+
+  
diff --git a/common-content/en/module/business-analysis/functional-architechture/index.md b/common-content/en/module/business-analysis/functional-architechture/index.md
new file mode 100644
index 000000000..49efc096e
--- /dev/null
+++ b/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
+
diff --git a/common-content/en/module/business-analysis/measure-success/index.md b/common-content/en/module/business-analysis/measure-success/index.md
new file mode 100644
index 000000000..557c717f7
--- /dev/null
+++ b/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). 
\ No newline at end of file
diff --git a/common-content/en/module/business-analysis/new-use-case/index.md b/common-content/en/module/business-analysis/new-use-case/index.md
new file mode 100644
index 000000000..3f3c64087
--- /dev/null
+++ b/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)?
diff --git a/common-content/en/module/business-analysis/personas/index.md b/common-content/en/module/business-analysis/personas/index.md
new file mode 100644
index 000000000..1071cffb8
--- /dev/null
+++ b/common-content/en/module/business-analysis/personas/index.md
@@ -0,0 +1,18 @@
++++
+title = "Personas"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Use personas to characterise particular types of user customers’ interactions with the business"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Learn about the use of personas - [article 1](https://www.getfishtank.com/insights/personas-in-agile-business-analysis) and [article 2](https://www.productplan.com/glossary/persona/)
+
+- Create at least two personas describing users of BrightStar services
+  
diff --git a/common-content/en/module/business-analysis/prioritisation/index.md b/common-content/en/module/business-analysis/prioritisation/index.md
new file mode 100644
index 000000000..8a281383c
--- /dev/null
+++ b/common-content/en/module/business-analysis/prioritisation/index.md
@@ -0,0 +1,24 @@
++++
+title = "Prioritisation"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Describe the different priotisation techniques"
+
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Read about different [prioritisation techniques](https://www.atlassian.com/agile/product-management/prioritization-framework#:~:text=A%20product%20prioritization%20framework%20is,what%20to%20work%20on%20next.).
+
+ 
+1. For your user case, which prioritisation technique would you use and why?
+
+2. How will you use priotisation with stakeholders?
+
+3.  Which priorisation technique do you think is not good and why?
+
diff --git a/common-content/en/module/business-analysis/review/index.md b/common-content/en/module/business-analysis/review/index.md
new file mode 100644
index 000000000..3234665ef
--- /dev/null
+++ b/common-content/en/module/business-analysis/review/index.md
@@ -0,0 +1,20 @@
++++
+title = "Review your BA tools"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "List all important toold and techniques you learned for business analysis"
+
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Review your notes and work from Sprints 1-5.
+
+Make sure you have a list of the main ones you would like to experiment with.
+
+You will use them in the exercise during the class.
\ No newline at end of file
diff --git a/common-content/en/module/business-analysis/specification/index.md b/common-content/en/module/business-analysis/specification/index.md
new file mode 100644
index 000000000..6eb4c4e68
--- /dev/null
+++ b/common-content/en/module/business-analysis/specification/index.md
@@ -0,0 +1,20 @@
++++
+title = "Specification"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Compare backlog and specifications"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Take a look at a software requirements specification template such as one provided by the [IEEE](https://web.cs.dal.ca/~hawkey/3130/srs_template-ieee.doc). 
+
+How does this differ from your understanding of a product backlog, as used in an agile approach?
+
+
+  
diff --git a/common-content/en/module/business-analysis/system-boundaries/index.md b/common-content/en/module/business-analysis/system-boundaries/index.md
new file mode 100644
index 000000000..06931707a
--- /dev/null
+++ b/common-content/en/module/business-analysis/system-boundaries/index.md
@@ -0,0 +1,18 @@
++++
+title = "System boundaries"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Define the boundaries of the solution",
+    "Distinguish between in-scope and out-of-scope items."
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Read about system boundaries and context diagrams in sections 2.1.4 - 2.1.5.2 of the IREB [RE@Agile Handbook](https://cpre.ireb.org/en/downloads-and-resources/downloads#cpre-re-agile-handbook).
+
+
diff --git a/common-content/en/module/business-analysis/use-case-more-info/index.md b/common-content/en/module/business-analysis/use-case-more-info/index.md
new file mode 100644
index 000000000..1e04de67b
--- /dev/null
+++ b/common-content/en/module/business-analysis/use-case-more-info/index.md
@@ -0,0 +1,24 @@
++++
+title = "Additional info for your use case"
+
+time = 15
+emoji = "🤖"
+objectives = [
+    "Understand data related to the product"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+You have been given this additional information concerning BrightStar. 
+ 
+Our target demographic is Millennials and Gen Z (18- 40ish), who expect seamless digital and personalised experiences. 
+
+Success metrics:
+- Loyalty: 50% increase in digital sign-ups/app downloads (12 months), higher engagement/redemption, improved retention, reduced service calls. 
+- Returns: 30% reduction in transaction time, fewer complaints, improved staff efficiency, faster refunds. 
+- We prefer modern cloud-based (Azure, AWS, Google Cloud) and SaaS solutions with API integration. We want to move away from legacy on-premise systems, but some may stay due to data protection laws. Note: We currently manage different legacy CRM solutions across our food and clothing departments, and a major upgrade to our core accounts/ERP system is also planned next year, which could impact integration timelines. 
+- Furthermore, we've experienced some challenges with our previous external mobile development partner, so vendor selection for any new app is critical. Microsoft Dynamics 365 integration is a plus 
+
diff --git a/common-content/en/module/business-analysis/use-case-prep/index.md b/common-content/en/module/business-analysis/use-case-prep/index.md
new file mode 100644
index 000000000..409666ace
--- /dev/null
+++ b/common-content/en/module/business-analysis/use-case-prep/index.md
@@ -0,0 +1,20 @@
++++
+title = "Use Cases"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Describe the differences between use case, scenario and user story"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Read about use cases and use case diagrams as another way of representing the scope of a solution (e.g. in section 2.1.5.3 in the [RE@Agile Handbook](https://cpre.ireb.org/en/downloads-and-resources/downloads#cpre-re-agile-handbook)). 
+
+Describe in your own words the differences between a use case, a scenario and a user story.
+
+
+  
diff --git a/common-content/en/module/business-analysis/user-journey/index.md b/common-content/en/module/business-analysis/user-journey/index.md
new file mode 100644
index 000000000..e32ec897f
--- /dev/null
+++ b/common-content/en/module/business-analysis/user-journey/index.md
@@ -0,0 +1,19 @@
++++
+title = "User journey"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Represent customers’ interactions with the business as user journeys",
+    "Create user journeys showing the  “as-is” state with pain points and “to-be” solutions"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Learn about user journeys (user journey maps) with [this article](https://www.nngroup.com/articles/journey-mapping-101/)
+
+1. Create a user journey representing the “as-is” state for an existing BrightStar service, identifying possible pain points at each step
+2. Create a second user journey to illustrate an improved solution
diff --git a/common-content/en/module/business-analysis/user-stories/index.md b/common-content/en/module/business-analysis/user-stories/index.md
new file mode 100644
index 000000000..b00568f2e
--- /dev/null
+++ b/common-content/en/module/business-analysis/user-stories/index.md
@@ -0,0 +1,18 @@
++++
+title = "User stories"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Write well-formed user stories based on proposed solutions"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Learn about writing well-formed user stories for business-level requirements - [article](https://www.easyagile.com/blog/how-to-write-good-user-stories-in-agile-software-development)
+
+1. Write 3 user stories for BrightStar
+
diff --git a/common-content/en/module/business-analysis/ux-design/index.md b/common-content/en/module/business-analysis/ux-design/index.md
new file mode 100644
index 000000000..56c952dab
--- /dev/null
+++ b/common-content/en/module/business-analysis/ux-design/index.md
@@ -0,0 +1,19 @@
++++
+title = "UX Design and Storyboarding"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Create an interface (UI) using a wireframe or storyboard that represents the desired behaviour of a user"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Learn about Ux design and storyboards (for example, [this example](https://www.interaction-design.org/literature/article/ux-storyboards?srsltid=AfmBOopdPR4ABkVTjWhL0VfncLq6y6DlmLJroW6tj6R23uVfzl9Ct94t)) as ways of modelling a user’s interactions with a system:
+
+1. Create a storyboard or wireframe for a particular scenario within BrightStar
+
+2. Can you identify any design principles that you have followed in developing your storyboard?
diff --git a/common-content/en/module/business-analysis/vision-goals/index.md b/common-content/en/module/business-analysis/vision-goals/index.md
new file mode 100644
index 000000000..829d9db08
--- /dev/null
+++ b/common-content/en/module/business-analysis/vision-goals/index.md
@@ -0,0 +1,17 @@
++++
+title = "User research"
+
+time = 60
+emoji = "🤖"
+objectives = [
+    "Formulate a set of solution goals, objectives, or value propositions"
+]
+[build]
+  render = "never"
+  list = "local"
+  publishResources = false
++++
+
+Learn about formulating a clear vision and goals for a project or product when faced with the assorted needs and desires of a group of stakeholders.  
+
+[This resource](https://agile.appliedframeworks.com/applied-frameworks-agile-blog/why-the-product-goal-is-not-the-product-vision-in-scrum) might help you understand the differences.
diff --git a/org-cyf-tracks/content/business-analysis/sprints/1/_index.md b/org-cyf-tracks/content/business-analysis/sprints/1/_index.md
index bebbb35e7..e64da7cc5 100644
--- a/org-cyf-tracks/content/business-analysis/sprints/1/_index.md
+++ b/org-cyf-tracks/content/business-analysis/sprints/1/_index.md
@@ -5,5 +5,5 @@ layout = "sprint"
 emoji= "⏱️"
 menu_level = ["module"]
 weight = 1
-theme = "Business Analysis"
+theme = "Discovering Customer Needs"
 +++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/1/day-plan/index.md b/org-cyf-tracks/content/business-analysis/sprints/1/day-plan/index.md
index 6c3f89035..2b56f1113 100644
--- a/org-cyf-tracks/content/business-analysis/sprints/1/day-plan/index.md
+++ b/org-cyf-tracks/content/business-analysis/sprints/1/day-plan/index.md
@@ -1,25 +1,25 @@
 +++
 title = "Day-plan"
-description = "TODO"
+description = "Discovering customer needs"
 layout = "day-plan"
 emoji = "📅"
 menu_level = ["sprint"]
 weight = 3
 [[blocks]]
 name="Energiser"
-src="energisers/zip-zap-boing"
+src="energisers/introduce-yourself"
 time=20
 [[blocks]]
-name="Presentation: what have you learned so far?"
-src="module/business-analysis/presentation"
+name="Presentation: round 1"
+src="module/business-analysis/demo"
 time=60
 [[blocks]]
 name="Morning break"
 src="blocks/morning-break"
 time=15
 [[blocks]]
-name="Presentation: what have you learned so far?"
-src="module/business-analysis/presentation"
+name="Presentation: round 2"
+src="module/business-analysis/demo"
 time=60
 [[blocks]]
 name="Lunch"
diff --git a/org-cyf-tracks/content/business-analysis/sprints/2/_index.md b/org-cyf-tracks/content/business-analysis/sprints/2/_index.md
new file mode 100644
index 000000000..d525f7cd3
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/2/_index.md
@@ -0,0 +1,9 @@
++++
+title = "Sprint 2"
+description = "Investigating the Business Domain"
+layout = "sprint"
+emoji= "⏱️"
+menu_level = ["module"]
+weight = 1
+theme = "Investigating the Business Domain"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/2/backlog/index.md b/org-cyf-tracks/content/business-analysis/sprints/2/backlog/index.md
new file mode 100644
index 000000000..3079578a9
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/2/backlog/index.md
@@ -0,0 +1,9 @@
++++
+title = "Backlog"
+layout = "backlog"
+emoji= "🥞"
+menu_level = ["sprint"]
+weight = 2
+backlog = "Track-Business-Analysis"
+backlog_filter = "📅 Sprint 2"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/2/day-plan/index.md b/org-cyf-tracks/content/business-analysis/sprints/2/day-plan/index.md
new file mode 100644
index 000000000..ff0de0434
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/2/day-plan/index.md
@@ -0,0 +1,46 @@
++++
+title = "Day-plan"
+description = "Investigating the business domains"
+layout = "day-plan"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 3
+[[blocks]]
+name="Energiser"
+src="energisers/bad-interview-answers"
+time=20
+[[blocks]]
+name="Presentation: round 1"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Morning break"
+src="blocks/morning-break"
+time=15
+[[blocks]]
+name="Presentation: round 2"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Lunch"
+src="blocks/lunch"
+time=60
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="90"
+[[blocks]]
+name="Afternoon Break"
+src="blocks/afternoon-break"
+time=15
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="60"
+[[blocks]]
+name="Wrap"
+src="blocks/wrap"
+time=15
++++
+
+
diff --git a/org-cyf-tracks/content/business-analysis/sprints/2/prep/index.md b/org-cyf-tracks/content/business-analysis/sprints/2/prep/index.md
new file mode 100644
index 000000000..9d1735be5
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/2/prep/index.md
@@ -0,0 +1,32 @@
++++
+title = "prep"
+description = "Investigating the Business Domain"
+layout = "prep"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 1
+[[blocks]]
+name="Additional information for your use case"
+src="module/business-analysis/use-case-more-info"
+[[blocks]]
+name="Vision and goals"
+src="module/business-analysis/vision-goals"
+[[blocks]]
+name="Personas"
+src="module/business-analysis/personas"
+[[blocks]]
+name="User Journey"
+src="module/business-analysis/user-journey"
+[[blocks]]
+name="User stories"
+src="module/business-analysis/user-stories"
+[[blocks]]
+name="Business domain"
+src="module/business-analysis/business-domain"
+[[blocks]]
+name="Business process model"
+src="module/business-analysis/business-process-model"
+[[blocks]]
+name="Presentation"
+src="module/business-analysis/presentation"
++++
\ No newline at end of file
diff --git a/org-cyf-tracks/content/business-analysis/sprints/2/success/index.md b/org-cyf-tracks/content/business-analysis/sprints/2/success/index.md
new file mode 100644
index 000000000..8a54d2640
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/2/success/index.md
@@ -0,0 +1,7 @@
++++
+title = 'success'
+layout = 'success'
+emoji= '✅'
+menu_level = ['sprint']
+weight = 4
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/3/_index.md b/org-cyf-tracks/content/business-analysis/sprints/3/_index.md
new file mode 100644
index 000000000..bc460eb79
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/3/_index.md
@@ -0,0 +1,9 @@
++++
+title = "Sprint 3"
+description = "Business Analysis"
+layout = "sprint"
+emoji= "⏱️"
+menu_level = ["module"]
+weight = 1
+theme = "Specifying the Solution"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/3/backlog/index.md b/org-cyf-tracks/content/business-analysis/sprints/3/backlog/index.md
new file mode 100644
index 000000000..c04961ac7
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/3/backlog/index.md
@@ -0,0 +1,9 @@
++++
+title = "Backlog"
+layout = "backlog"
+emoji= "🥞"
+menu_level = ["sprint"]
+weight = 2
+backlog = "Track-Business-Analysis"
+backlog_filter = "📅 Sprint 3"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/3/day-plan/index.md b/org-cyf-tracks/content/business-analysis/sprints/3/day-plan/index.md
new file mode 100644
index 000000000..b32befa22
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/3/day-plan/index.md
@@ -0,0 +1,46 @@
++++
+title = "Day-plan"
+description = "Specifying the solution"
+layout = "day-plan"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 3
+[[blocks]]
+name="Energiser"
+src="energisers/18-and-unders"
+time=20
+[[blocks]]
+name="Presentation: round 1"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Morning break"
+src="blocks/morning-break"
+time=15
+[[blocks]]
+name="Presentation: round 2"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Lunch"
+src="blocks/lunch"
+time=60
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="90"
+[[blocks]]
+name="Afternoon Break"
+src="blocks/afternoon-break"
+time=15
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="60"
+[[blocks]]
+name="Wrap"
+src="blocks/wrap"
+time=15
++++
+
+
diff --git a/org-cyf-tracks/content/business-analysis/sprints/3/prep/index.md b/org-cyf-tracks/content/business-analysis/sprints/3/prep/index.md
new file mode 100644
index 000000000..b6f38f805
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/3/prep/index.md
@@ -0,0 +1,29 @@
++++
+title = "prep"
+description = "Specifying the solution"
+layout = "prep"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 1
+[[blocks]]
+name="Requirements"
+src="module/business-analysis/requirements"
+[[blocks]]
+name="System boundaries"
+src="module/business-analysis/system-boundaries"
+[[blocks]]
+name="Epics"
+src="module/business-analysis/epics"
+[[blocks]]
+name="Use case"
+src="module/business-analysis/use-case-prep"
+[[blocks]]
+name="Specification"
+src="module/business-analysis/specification"
+[[blocks]]
+name="Acceptance criteria"
+src="module/business-analysis/acceptance-criteria"
+[[blocks]]
+name="Presentation"
+src="module/business-analysis/presentation"
++++
\ No newline at end of file
diff --git a/org-cyf-tracks/content/business-analysis/sprints/3/success/index.md b/org-cyf-tracks/content/business-analysis/sprints/3/success/index.md
new file mode 100644
index 000000000..fa2496211
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/3/success/index.md
@@ -0,0 +1,7 @@
++++
+title = "Success"
+layout = "success"
+emoji= "✅"
+menu_level = ["sprint"]
+weight = 4
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/4/_index.md b/org-cyf-tracks/content/business-analysis/sprints/4/_index.md
new file mode 100644
index 000000000..fd7abd78d
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/4/_index.md
@@ -0,0 +1,9 @@
++++
+title = "Sprint 4"
+description = "Business Analysis"
+layout = "sprint"
+emoji= "⏱️"
+menu_level = ["module"]
+weight = 1
+theme = "Transforming Requirements to Solution Design"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/4/backlog/index.md b/org-cyf-tracks/content/business-analysis/sprints/4/backlog/index.md
new file mode 100644
index 000000000..9d54cdc9a
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/4/backlog/index.md
@@ -0,0 +1,9 @@
++++
+title = "Backlog"
+layout = "backlog"
+emoji= "🥞"
+menu_level = ["sprint"]
+weight = 2
+backlog = "Track-Business-Analysis"
+backlog_filter = "📅 Sprint 4"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/4/day-plan/index.md b/org-cyf-tracks/content/business-analysis/sprints/4/day-plan/index.md
new file mode 100644
index 000000000..c8ccaa0f7
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/4/day-plan/index.md
@@ -0,0 +1,46 @@
++++
+title = "Day-plan"
+description = "Transforming Requirements to Solution Design"
+layout = "day-plan"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 3
+[[blocks]]
+name="Energiser"
+src="energisers/18-and-unders"
+time=20
+[[blocks]]
+name="Presentation: round 1"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Morning break"
+src="blocks/morning-break"
+time=15
+[[blocks]]
+name="Presentation: round 2"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Lunch"
+src="blocks/lunch"
+time=60
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="90"
+[[blocks]]
+name="Afternoon Break"
+src="blocks/afternoon-break"
+time=15
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="60"
+[[blocks]]
+name="Wrap"
+src="blocks/wrap"
+time=15
++++
+
+
diff --git a/org-cyf-tracks/content/business-analysis/sprints/4/prep/index.md b/org-cyf-tracks/content/business-analysis/sprints/4/prep/index.md
new file mode 100644
index 000000000..0d5a8d51b
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/4/prep/index.md
@@ -0,0 +1,29 @@
++++
+title = "prep"
+description = "Transforming requirements to solution design"
+layout = "prep"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 1
+[[blocks]]
+name="Design mindset"
+src="module/business-analysis/design-mindset"
+[[blocks]]
+name="Design principles"
+src="module/business-analysis/design-principles"
+[[blocks]]
+name="UX Design"
+src="module/business-analysis/ux-design"
+[[blocks]]
+name="Functional architechture"
+src="module/business-analysis/functional-architechture"
+[[blocks]]
+name="Data modelling"
+src="module/business-analysis/data-modelling"
+[[blocks]]
+name="Design solution"
+src="module/business-analysis/design-solution"
+[[blocks]]
+name="Presentation"
+src="module/business-analysis/presentation"
++++
\ No newline at end of file
diff --git a/org-cyf-tracks/content/business-analysis/sprints/4/success/index.md b/org-cyf-tracks/content/business-analysis/sprints/4/success/index.md
new file mode 100644
index 000000000..fa2496211
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/4/success/index.md
@@ -0,0 +1,7 @@
++++
+title = "Success"
+layout = "success"
+emoji= "✅"
+menu_level = ["sprint"]
+weight = 4
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/5/_index.md b/org-cyf-tracks/content/business-analysis/sprints/5/_index.md
new file mode 100644
index 000000000..13139d2d7
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/5/_index.md
@@ -0,0 +1,9 @@
++++
+title = "Sprint 5"
+description = "Business Analysis"
+layout = "sprint"
+emoji= "⏱️"
+menu_level = ["module"]
+weight = 1
+theme = "Delivering solutions"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/5/backlog/index.md b/org-cyf-tracks/content/business-analysis/sprints/5/backlog/index.md
new file mode 100644
index 000000000..e1eab544c
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/5/backlog/index.md
@@ -0,0 +1,9 @@
++++
+title = "Backlog"
+layout = "backlog"
+emoji= "🥞"
+menu_level = ["sprint"]
+weight = 2
+backlog = "Track-Business-Analysis"
+backlog_filter = "📅 Sprint 5"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/5/day-plan/index.md b/org-cyf-tracks/content/business-analysis/sprints/5/day-plan/index.md
new file mode 100644
index 000000000..717936869
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/5/day-plan/index.md
@@ -0,0 +1,46 @@
++++
+title = "Day-plan"
+description = "Delivering solutions"
+layout = "day-plan"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 3
+[[blocks]]
+name="Energiser"
+src="energisers/popcorn-screen-share"
+time=20
+[[blocks]]
+name="Presentation: round 1"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Morning break"
+src="blocks/morning-break"
+time=15
+[[blocks]]
+name="Presentation: round 2"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Lunch"
+src="blocks/lunch"
+time=60
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="90"
+[[blocks]]
+name="Afternoon Break"
+src="blocks/afternoon-break"
+time=15
+[[blocks]]
+name="Study Group"
+src="blocks/study-group"
+time="60"
+[[blocks]]
+name="Wrap"
+src="blocks/wrap"
+time=15
++++
+
+
diff --git a/org-cyf-tracks/content/business-analysis/sprints/5/prep/index.md b/org-cyf-tracks/content/business-analysis/sprints/5/prep/index.md
new file mode 100644
index 000000000..78b87727f
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/5/prep/index.md
@@ -0,0 +1,23 @@
++++
+title = "prep"
+description = "Delivering solutions"
+layout = "prep"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 1
+[[blocks]]
+name="Agile and others"
+src="module/business-analysis/agile"
+[[blocks]]
+name="Measure Success"
+src="module/business-analysis/measure-success"
+[[blocks]]
+name="Change Management"
+src="module/business-analysis/change-mgmt"
+[[blocks]]
+name="Prioritisation"
+src="module/business-analysis/prioritisation"
+[[blocks]]
+name="Presentation"
+src="module/business-analysis/presentation"
++++
\ No newline at end of file
diff --git a/org-cyf-tracks/content/business-analysis/sprints/5/success/index.md b/org-cyf-tracks/content/business-analysis/sprints/5/success/index.md
new file mode 100644
index 000000000..fa2496211
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/5/success/index.md
@@ -0,0 +1,7 @@
++++
+title = "Success"
+layout = "success"
+emoji= "✅"
+menu_level = ["sprint"]
+weight = 4
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/6/_index.md b/org-cyf-tracks/content/business-analysis/sprints/6/_index.md
new file mode 100644
index 000000000..29c346290
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/6/_index.md
@@ -0,0 +1,9 @@
++++
+title = "Sprint 6"
+description = "Business Analysis"
+layout = "sprint"
+emoji= "⏱️"
+menu_level = ["module"]
+weight = 1
+theme = "Putting it all together"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/6/backlog/index.md b/org-cyf-tracks/content/business-analysis/sprints/6/backlog/index.md
new file mode 100644
index 000000000..1fc871eff
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/6/backlog/index.md
@@ -0,0 +1,9 @@
++++
+title = "Backlog"
+layout = "backlog"
+emoji= "🥞"
+menu_level = ["sprint"]
+weight = 2
+backlog = "Track-Business-Analysis"
+backlog_filter = "📅 Sprint 6"
++++
diff --git a/org-cyf-tracks/content/business-analysis/sprints/6/day-plan/index.md b/org-cyf-tracks/content/business-analysis/sprints/6/day-plan/index.md
new file mode 100644
index 000000000..476e23938
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/6/day-plan/index.md
@@ -0,0 +1,38 @@
++++
+title = "Day-plan"
+description = "Putting it all together"
+layout = "day-plan"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 3
+[[blocks]]
+name="Energiser"
+src="energisers/slack-libs"
+time=20
+[[blocks]]
+name="New Use case"
+src="module/business-analysis/new-use-case"
+time=120
+[[blocks]]
+name="Lunch"
+src="blocks/lunch"
+time=60
+[[blocks]]
+name="Presentation: round 1"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Afternoon Break"
+src="blocks/afternoon-break"
+time=15
+[[blocks]]
+name="Presentation: round 2"
+src="module/business-analysis/demo"
+time=60
+[[blocks]]
+name="Wrap"
+src="blocks/wrap"
+time=15
++++
+
+
diff --git a/org-cyf-tracks/content/business-analysis/sprints/6/prep/index.md b/org-cyf-tracks/content/business-analysis/sprints/6/prep/index.md
new file mode 100644
index 000000000..696494939
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/6/prep/index.md
@@ -0,0 +1,11 @@
++++
+title = "prep"
+description = "Putting it all together"
+layout = "prep"
+emoji = "📅"
+menu_level = ["sprint"]
+weight = 1
+[[blocks]]
+name="Review"
+src="module/business-analysis/review"
++++
\ No newline at end of file
diff --git a/org-cyf-tracks/content/business-analysis/sprints/6/success/index.md b/org-cyf-tracks/content/business-analysis/sprints/6/success/index.md
new file mode 100644
index 000000000..fa2496211
--- /dev/null
+++ b/org-cyf-tracks/content/business-analysis/sprints/6/success/index.md
@@ -0,0 +1,7 @@
++++
+title = "Success"
+layout = "success"
+emoji= "✅"
+menu_level = ["sprint"]
+weight = 4
++++