Update BA curriculum with AI review exercises

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

@@ -3,7 +3,8 @@ title = "Requirements"
 
 time = 60
 objectives = [
-    "Write different types of requirements (functional, non-functional/quality, constraint)"
+    "Write different types of requirements (functional, non-functional/quality, constraint)",
+    "Use AI to review and improve the quality of requirements"
 ]
 [build]
   render = "never"
@@ -17,7 +18,9 @@ Learn the definition of a requirement and note that Requirements Engineering is
 
 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 
+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.
 
-
+Use AI to review the functional and non-functional requirements you suggested. Ask AI to:
+1. Review the functional and non-functional requirements you suggested: identify vague wording and missing details. Then challenge whether each requirement is grounded in BrightStar.
+2. Generate a few weak examples of functional and non-functional requirements for BrightStar. Compare them with your own requirements and explain what makes the examples weak and how they could be improved.

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

@@ -4,7 +4,8 @@ title = "Business domains"
 time = 90
 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)"
+    "Represent the relationships among key entities in the domain in a conceptual data model (business domain model)",
+    "Use AI to support and review business domain artefacts"
 ]
 [build]
   render = "never"
@@ -17,3 +18,7 @@ Learn about the importance of terminology and how to use glossaries, data dictio
 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/)
+
+Use AI to support your business domain analysis. Ask AI to:
+1. Generate a first-draft glossary for the BrightStar retail, loyalty, and CRM domain. Critically review and edit the glossary: remove irrelevant terms, correct definitions, and add important terms that AI missed.
+2. Review your conceptual data model using Customer, Transaction, LoyaltyCard, Product, and any other relevant entities. Ask AI to challenge the entities and relationships and explain any concepts or relationships that are unclear.

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

@@ -1,5 +1,5 @@
 +++
-title = "User research"
+title = "Business Requirements"
 
 time = 60
 objectives = [

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

@@ -3,7 +3,8 @@ title = "Communicating effectively"
 
 time = 30
 objectives = [
-    "Formulate and ask effective, open-ended questions during stakeholder interviews to uncover business needs and pain points."
+    "Formulate and ask effective, open-ended questions during stakeholder interviews to uncover business needs and pain points.",
+    "Use AI to practise stakeholder communication"
 ]
 [build]
   render = "never"
@@ -15,3 +16,4 @@ Describe at least two tailored communication approaches suitable for particular
 
 Research about open-ended questions. Consider what kind of open-ended questions you would ask each of stakeholders and why.
 
+Use AI to practise stakeholder communication. Ask AI to role-play as one of the BrightStar stakeholders. Practise asking open-ended questions and adapting your communication style to that stakeholder. After the conversation, ask AI for feedback on your questions and communication approach.

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

@@ -28,7 +28,7 @@ Then the next person will demo their work.
 
 ### 1. Demo {{<timer>}}10{{</timer>}}
 
-You will demo the work you did for this sprint as if you were presenting it to Brighsparks stakeholders.
+You will demo the work you did for this sprint as if you were presenting it to BrightStar stakeholders.
 
 You will have 10 minutes to explain run the stakeholders through your findings and logic behind it.
 

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

@@ -4,7 +4,8 @@ title = "Epics and features"
 time = 60
 objectives = [
     "Describe requirements at high level or in more detail (levels of granularity)", 
-    "Write epics, features and stories"
+    "Write epics, features and stories",
+    "Use AI to review the structure and traceability of epics, features, and user stories"
 ]
 [build]
   render = "never"
@@ -14,12 +15,13 @@ objectives = [
 
 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
+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).
 
-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
+Use AI to review your epics, features, and user stories. Ask AI to:
+1. Check your understanding of the differences between epics, features, and user stories, and how they are connected.
+2. Review your user stories against the [INVEST criteria](https://cpre.ireb.org/en/downloads-and-resources/downloads#cpre-re-agile-handbook)
+3. Challenge the traceability between business goals, epics, features, user stories, and lower-level requirements.
 
-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/personas/index.md

@@ -3,7 +3,8 @@ title = "Personas"
 
 time = 60
 objectives = [
-    "Use personas to characterise particular types of user customers’ interactions with the business"
+    "Use personas to characterise particular types of user customers’ interactions with the business",
+    "Use AI to review personas and identify missing information"
 ]
 [build]
   render = "never"
@@ -12,6 +13,12 @@ objectives = [
 +++
 
 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
+1. Identify the relevant demographic information from the BrightStar case study.
+2. Create at least two personas describing users of BrightStar services.
 
+Use AI to review your personas. Ask AI to review your BrightStar personas and identify:
+1. Assumptions that are not supported by the case study information.
+2. Personas that are too similar to each other.
+3. Important user needs, behaviours, or pain points you may have missed.
+
+Review the AI feedback and decide which suggestions are valid.

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

@@ -5,15 +5,20 @@ time = 60
 objectives = [
     "Present finding from a business analysis perspective.",
     "Present and discuss the latest learnings on the sprint.",
+    "Use AI to review and practise a presentation"
 ]
 [build]
   render = "never"
   list = "local"
   publishResources = false
 +++
 
-Build the presentation of how you applied the key learnings of this week to the Bright Sparks case study.
+Build the presentation of how you applied the key learnings of this week to the BrightStar case study.
 
 The people in class can be the stakeholders and will evaluate your work. 
 
 The presentation must be less than 10 minutes long.  
+
+Use AI to review and practise your presentation. Ask AI to:
+1. Review the English and spot any gaps in the presentation.
+2. Practise the presentation with you and give feedback on your delivery and explanation.

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

@@ -3,7 +3,8 @@ title = "Specification"
 
 time = 60
 objectives = [
-    "Compare backlog and specifications"
+    "Compare backlog and specifications",
+    "Use AI to review and challenge comparisons between an SRS and an agile product backlog"
 ]
 [build]
   render = "never"
@@ -15,5 +16,8 @@ Take a look at a software requirements specification template such as one provid
 
 How does this differ from your understanding of a product backlog, as used in an agile approach?
 
+Use AI to review your comparison. Ask AI to:
+1. Challenge your comparison of an SRS and an agile product backlog and identify anything you may have missed.
+2. Generate an example of the same BrightStar requirement represented in a specification and as a backlog item.
 
-  
+Compare the two examples and explain the differences.

common-content/en/module/business-analysis/stakeholder-mapping/index.md

@@ -4,7 +4,8 @@ title = "Stakeholder mapping"
 time = 45
 objectives = [
     "Identify potential stakeholders in a project/product context", 
-    "Tailor communication approaches for different stakeholder types"
+    "Tailor communication approaches for different stakeholder types",
+    "Use AI to review stakeholder mapping and identify gaps"
 ]
 [build]
   render = "never"
@@ -13,3 +14,10 @@ objectives = [
 +++
 
 Create a stakeholder map and a preliminary RACI matrix for a given scenario, identifying key stakeholders and their potential roles and responsibilities. 
+
+Use AI to review your stakeholder mapping. Ask AI to review your stakeholder map and identify:
+1. Missing stakeholders
+2. Unclear or incomplete roles and responsibilities
+3. Gaps in the stakeholder relationships or RACI matrix
+
+Review the AI feedback and decide which suggestions are valid for BrightStar.

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

@@ -4,6 +4,7 @@ title = "SWOT Analysis"
 time = 45
 objectives = [
     "Gather and summarise information about a business's current business situation, for example with the help of SWOT analysis",
+    "Use AI to review and improve a SWOT analysis"
 ]
 [build]
   render = "never"
@@ -13,4 +14,10 @@ objectives = [
 
 You were given a lot of information on the case study. Considering everything you know so far, and maybe making some assumptions, perform a SWOT analysis for BrightStar.
 
-If you do not know what a SWOT analysis is, research about it first. 
+If you are not familiar with SWOT analysis, read this [SWOT Analysis Guide](https://www.indeed.com/career-advice/career-development/swot-analysis-guide) before starting the exercise.
+
+Use AI to review and improve a SWOT analysis. Ask AI to review your BrightStar SWOT analysis and identify:
+1. Missing strengths, weaknesses, opportunities, or threats
+2. Points that may be unclear or unsupported
+
+Review the AI feedback and decide which suggestions are valid for BrightStar.

common-content/en/module/business-analysis/system-boundaries/index.md

@@ -4,14 +4,21 @@ title = "System boundaries"
 time = 60
 objectives = [
     "Define the boundaries of the solution",
-    "Distinguish between in-scope and out-of-scope items."
+    "Distinguish between in-scope and out-of-scope items",
+    "Use AI to critically review system boundaries and identify missing actors, systems, dependencies, or unclear boundaries"
 ]
 [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).
+Read about system boundaries and context diagrams in sections 2.2 "Specifying the system boundary", including sections 2.2.1.1 "Context diagram" and 2.2.1.2 "Natural language documentation of scope and system boundary", of the [IREB RE@Agile Handbook](https://cpre.ireb.org/en/downloads-and-resources/downloads#cpre-re-agile-handbook).
 
+Ask AI to review the system boundaries you defined for BrightStar and identify:
+1. Missing actors.
+2. Missing external systems.
+3. Missing dependencies.
+4. Unclear system boundaries.
 
+Compare the AI feedback with the BrightStar project information and decide which suggestions are valid.

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

@@ -3,17 +3,22 @@ title = "Use Cases"
 
 time = 60
 objectives = [
-    "Describe the differences between use case, scenario and user story"
+    "Describe the differences between use case, scenario and user story",
+    "Use AI to review and improve explanations of use cases, scenarios, and user stories"
 ]
 [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)). 
+Read about use cases and use case diagrams as another way of representing the scope of a solution (e.g. in section 2.2.1.3 "Use case diagram" in the [IREB 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.
 
+Use AI to review your explanation. Ask AI to::
+1. Review your explanation of the differences between a use case, scenario, and user story.
+2. Identify any inaccuracies or unclear points.
+3. Provide one example of a use case, a scenario, and a user story for BrightStar.
 
-  
+Review the AI examples and explain why each one is, or is not, a valid example of the artefact.

common-content/en/module/business-analysis/user-research/index.md

@@ -4,14 +4,16 @@ title = "User research"
 time = 60
 objectives = [
     "Describe different methods of user research and requirements gathering (e.g., interviews, surveys, usability testing)", 
-    "Explain the  purpose and benefit of each user research"
+    "Explain the  purpose and benefit of each user research",
+    "Explore how AI can support user research"
 ]
 [build]
   render = "never"
   list = "local"
   publishResources = false
 +++
 
-Read about common user research methods, including interviews, surveys and usability testing 
+Read about common user research methods, including interviews, surveys and usability testing.
+Choose a research method for the BrightStar case study and explain why it is an appropriate choice in that context.
 
-- Choose a research method for the BrightStar case study and explain why it is an appropriate choice in that context
+Explore how AI can support user research. Think about how AI could make user research faster, easier, or more effective. Ask AI to suggest ways it could support different stages of user research, such as preparing questions, analysing responses, or identifying patterns. Review the suggestions and decide which uses would be appropriate for BrightStar.

common-content/en/module/business-analysis/user-stories/index.md

@@ -3,15 +3,23 @@ title = "User stories"
 
 time = 60
 objectives = [
-    "Write well-formed user stories based on proposed solutions"
+    "Write well-formed user stories based on proposed solutions",
+    "Use AI to format and review user stories and acceptance criteria"
 ]
 [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)
+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). Read section 3.3.3 "INVEST: criteria for \"good\" backlog items" of the [IREB RE@Agile Handbook](https://cpre.ireb.org/en/downloads-and-resources/downloads#cpre-re-agile-handbook).
+1. Write 3 user stories for BrightStar.
+2. Add acceptance criteria to each user story.
 
-1. Write 3 user stories for BrightStar
+Use AI to support and review your user stories. Ask AI to:
+1. Format your user needs using the structure: "As a [user], I want [X] so that [Y]".
+2. Review your user stories against the INVEST criteria.
+3. Review the acceptance criteria and identify any unclear or missing criteria.
+4. Generate a few weak user story examples that fail one or more INVEST criteria. Compare them with your own user stories and explain which INVEST criteria they fail and how you would improve them.
 
+Review the AI feedback and decide which suggestions are valid for BrightStar.

common-content/en/module/business-analysis/vision-goals/index.md

@@ -3,14 +3,22 @@ title = "User research"
 
 time = 60
 objectives = [
-    "Formulate a set of solution goals, objectives, or value propositions"
+    "Formulate a set of solution goals, objectives, or value propositions",
+    "Use AI to challenge the alignment and grounding of a product vision and goals"
 ]
 [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.  
+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.
+1. Explain the difference between a product vision and product goals in your own words.
+2. Suggest a product vision and goals for BrightStar based on the case study information.
 
-[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.
+Use AI to review your vision and goals. Ask AI to challenge your proposed vision and goals and identify:
+1. Goals that do not support the vision.
+2. Vague or unclear goals.
+3. Suggestions that are not grounded in the BrightStar project information.
+
+Review the AI feedback and decide which suggestions are valid.

org-cyf/content/tracks/business-analysis/sprints/3/prep/index.md

@@ -20,9 +20,6 @@ src="module/business-analysis/use-case-prep"
 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"
 +++