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

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 might help you understand the differences.

Learn how to define measurable business goals using Objectives and Key Results (OKRs) and Key Performance Indicators (KPIs). Read OKR vs KPI to understand the differences and how they can be used together. For additional examples, see OKR vs KPI: Differences, Examples, and Use Cases.

Using the BrightStar case study:

1. Identify one business goal and define an Objective with two measurable Key Results.
2. Suggest two relevant KPIs to monitor business performance.
3. Explain how your proposed OKRs and KPIs relate to the business goal.

Learn about the use of personas - article 1 and article 2

• Create at least two personas describing users of BrightStar services

Learn about user journeys (user journey maps) with this article

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

Learn about writing well-formed user stories for business-level requirements - article. Read section 3.3.3 “INVEST: criteria for "good" backlog items” of the IREB RE@Agile Handbook.

1. Based on the requirements gathered for BrightStar, write 3 user stories.
2. Add acceptance criteria using Gherkin Format to each user story.
3. Review and refine your user stories using the INVEST criteria.
4. Consider whether you need to add any supporting documentation, such as an API spec, data flow, etc to suggest or facilitate implementation

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 as an example. This is a data dictionary and data modelling 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

Learn about business process modelling and notations used for this (eg, BPMN, UML). You can do the Udemy course on process modelling for BPMN, and then refer to this page here to understand the syntax of each notations (events, activity, artifact types).

Read about As-is and To-be process modelling and how these models help identify opportunities for process improvement.

You can also refer to this page to understand the differences between BPMN & UML in this article.

1. Create a simple As-is 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
3. Create a To-be business process model showing how the process could be improved. Briefly explain the key differences between the two models.
4. Review your processes now, thinking about the technical implementation, including system architecture, automation opportunities, and integration points, when applicable. What would you change and why?

Build the presentation of how you applied the key learnings of this week to the Bright Sparks case study.

The people in class can be the stakeholders and will evaluate your work.

The presentation must be less than 10 minutes long.