Enrol in this Udemy course and jump to video 14 (What is Scrum?) in section 5. Watch this video to review Scrum basics.

Stretch: Watch any of the subsequent videos in section 5 if you would like to drill into any more details.

Now let’s try and apply our knowledge of Agile business analysis in the BrightStar project:

1. Prepare an initial backlog for BrightStar using the requirements gathered and refined in previous sprints (5-20 backlog items, depending on the level of detail). You may use Epic, Feature and Story types of backlog items. Use GitHub projects to document this. Other tools for managing backlogs and Kanban boards include Jira and Azure DevOps. Find out which tool the company you are applying to or will work for uses, and familiarise yourself with it. This GitHub page explains more details. You can use the Milestone feature as an Epic.

2. Read about prioritisation techniques, including RICE, Kano, MoSCoW, Value vs. Effort, Opportunity Scoring, and Cost of Delay. Describe how you would approach setting priorities for your backlog items. Consider the information needed, the stakeholders involved, and what you would need to clarify about the team’s existing prioritisation approach. Prioritise understanding of the prioritsation technique you know the company you are applying to or will work for uses.

3. Formulate a Definition of Ready for the BrightStar product development process

4. Describe how you would go about setting sprint goals and how you would reflect these decisions in the backlog

5. Describe the MVP for your planned BrightStar development

6. Formulate a Definition of Done for backlog items. Define clear criteria that must be met for each item to be considered complete.

7. Consider how feedback from your sprint deliverables would affect your prioritisation and goal setting for later sprints

Learn and reflect on these questions, so you can understand how change affects your work.

1. What is change management, and how does it affect the BA?

2. What is the difference between change management and organisational change management?

3. What are scope changes, and how should you deal with them?

4. How could change management conflict with Agile principles? How would you handle this conflict pragmatically?

5. Thinking about the roadmap you built, how will change management be part of your MVP?

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.

Do you want to learn something extra?

• Plan and prepare a Retrospective for your BrightStar scrum team. Consider that it can be a hybrid team. Think about the board, how you want the interaction to be, how you want to lead it.

• Read about Roadmaps and prepare a Roadmap for the next 2-4 product increments (a product increments might be one quarter of the year, for example) of your BrightStar solution