6.3. Scrum Overview

Scrum is an Agile framework used to manage product development through empirical process control. It focuses on transparency, inspection, and adaptation.

Scrum is a framework that provides a structured approach for teams to develop products effectively and efficiently. It promotes control over the development process by ensuring that all actions taken are visible and can be inspected for improvements. This leads to better adaptability to changes throughout the development phases.

Think of Scrum as the rules of a game. Without clear rules, players may not understand how to play effectively or how to win. Similarly, Scrum establishes rules for how teams interact, adapt, and deliver, helping them achieve the best results.

Scrum Roles

• Product Owner: Owns the product backlog, prioritizes work based on value.
• Scrum Master: Facilitates the process, removes blockers, ensures Scrum is followed.
• Development Team: Cross-functional group that delivers the product increment.

Where does the BA fit in?

• May assist the Product Owner in backlog grooming, writing user stories, facilitating communication, and defining acceptance criteria.
• Acts as a bridge between business needs and development clarity.

In Scrum, there are defined roles that ensure that the process runs smoothly. The Product Owner represents the stakeholders and is responsible for maximizing the product's value by managing the product backlog. The Scrum Master ensures that the team follows the Scrum practices and helps to remove any obstacles they might face. The Development Team consists of members with various skills who collectively complete the tasks. The Business Analyst fits into this structure primarily by working closely with the Product Owner and Development Team to ensure that requirements are clear and well communicated.

Imagine a movie production team. The Director (Product Owner) makes key decisions about the film, while the Producer (Scrum Master) ensures the project runs smoothly without interruptions, and the Crew (Development Team) executes on set tasks to bring the film to life. The Script Supervisor (Business Analyst) ensures that the script (requirements) is understood by all actors and crew members, translating needs into actions.

📦 Scrum Artifacts

• Product Backlog: Ordered list of everything that might be needed in the product.
• Sprint Backlog: List of items selected for the current sprint + a plan to deliver them.
• Increment: The sum of all completed work that meets the Definition of Done.

Scrum artifacts provide valuable information that helps the team stay updated on their progress and required tasks. The Product Backlog is a comprehensive list of all desired features and improvements, prioritized based on value. The Sprint Backlog consists of selected items from the Product Backlog that the team commits to completing in the current sprint. The Increment is a measure of progress, representing the total work completed during a sprint that meets the team's definition of completeness.

Think of the Product Backlog as a menu in a restaurant; it lists all potential dishes that could be ordered. The Sprint Backlog is like the orders taken by the chef for that day. The Increment represents the dishes that have been prepared and are ready to serve—almost like the dishes on the serving counter that meet the restaurant's quality standard.

✅ Example of a Product Backlog Item (User Story):

As a registered user, I want to reset my password using email so that I can regain account access.

With Acceptance Criteria:

• Reset link is sent to the registered email.
• Link expires in 24 hours.
• Must verify user identity before resetting.

This user story is a simple way of stating a feature from the perspective of the end-user. It articulates what the user wants and why it’s important to them. The acceptance criteria are conditions that must be met for the story to be considered complete, ensuring that the development team has a clear understanding of what is required.

Imagine ordering a custom-made cake. The user story tells the baker what you want (to reset your password) and why (so you can regain access). The acceptance criteria are like specific instructions such as, 'The cake must have three layers,' 'It should be chocolate-flavored,' and 'It must include a 'Happy Birthday' message.' These guide the baker to deliver exactly what you've envisioned.

🔁 Agile Ceremonies

Agile teams work in time-boxed iterations (sprints), with key events to facilitate communication, planning, and improvement.

1. Daily Stand-up (Daily Scrum)

   • Duration: 15 minutes
   • Participants: Dev Team + Scrum Master (PO optional)
   • Purpose: Share updates, identify blockers, sync up

   Questions Asked:

   1. What did I do yesterday?
   2. What will I do today?
   3. Are there any blockers?

   BA Role:

   • Attend to track progress and understand blockers related to requirements or user stories.

2. Sprint Planning

   • When: Beginning of each sprint
   • Purpose: Define the Sprint Goal and select what will be delivered
   • Activities:
     • PO presents prioritized backlog items
     • Dev team estimates effort (e.g., using story points)
     • Sprint backlog is created
   • BA Role:
     • Clarify user stories, provide business context
     • Ensure requirements are well-understood and ready (Definition of Ready)

3. Sprint Review (Demo)

   • When: End of sprint
   • Purpose: Showcase completed work to stakeholders
   • Activities:
     • Dev team demonstrates completed stories
     • Stakeholders provide feedback
     • PO updates backlog based on feedback
   • BA Role:
     • Capture stakeholder feedback
     • Validate whether the increment meets business needs

4. Sprint Retrospective

   • When: After the Sprint Review
   • Purpose: Reflect on the process, not the product
   • Focus Areas:
     • What went well?
     • What didn’t go well?
     • What can be improved?
   • BA Role:
     • Participate actively
     • Suggest improvements in requirement clarity or team collaboration.

Agile ceremonies are regular meetings that support the Scrum framework. Each event has a specific purpose, ensuring the team communicates effectively and stays on track. The Daily Stand-up allows team members to quickly update each other and identify any issues. Sprint Planning occurs at the start of each sprint, aligning the team on what they will accomplish. The Sprint Review at the end of a sprint focuses on showcasing work and adapting based on feedback. Lastly, the Sprint Retrospective offers the team time to reflect and improve their processes.

Consider Agile ceremonies like a team of dancers rehearsing for a performance. The Daily Stand-up is like a quick warm-up where everyone shares their readiness and any issues they have. Sprint Planning is comparable to choreographing the routine together, deciding which parts to focus on. The Sprint Review is the rehearsal in front of an audience—gathering feedback to improve. Finally, the Retrospective is like a discussion afterward about what worked in the dance and what could be done better for the next performance.

--