Goal

  • Understand the concept of Scrum
  • Learn how to apply Scrum in software development
  • Practice Scrum using a simple CLI “Hit and Blow” game

Team Roles

Assign roles within your team:

  • Product Owner (1 person)
    • Represents the customer and stakeholders
    • Owns and prioritizes the Product Backlog
  • Scrum Master (1 person)
    • Facilitates Scrum events
    • Removes blockers and supports the team
  • Developers (everyone else)
    • Build the product during each Sprint

Creating the Product Backlog

  • The Product Backlog is a list of prioritized user stories
  • Based on your User Story Map and Release Plan
  • Maintained and updated by the Product Owner
  • All members can comment, but only the Product Owner can change it
  • The backlog evolves throughout the project

Use Excalidraw to visually manage the product backlog

Sprint Planning Meeting

  • Select stories to complete in this Sprint
  • Break down each story into tasks
  • Estimate task effort using: 1, 2, 3, 5, 8, 13, ∞ (Planning Poker)
  • Create a Kanban board for this Sprint in Excalidraw

Facilitated by the Scrum Master

Sprint: Implementation (Part 1)

  • Start coding based on the Sprint Backlog
  • Use Mob Programming:
    • One developer is the Driver (writes the code)
    • Others are Navigators (guide and review)
  • Apply TDD (Test-Driven Development) as much as possible

Daily Scrum

  • A brief daily checkpoint
  • Each developer answers:
    • What was done?
    • What will be done next?
    • Are there any problems?

Goal: Share information, not solve problems
Facilitated by the Scrum Master
Developers solve issues together – the Scrum Master is not a manager

Sprint: Implementation (Part 2)

  • Continue development as in Part 1
  • Prepare for the Sprint Review:
    • Merge code and ensure it runs as a working product

📣 Sprint Review

  • Attended by the Product Owner, Scrum Master, and Developers
  • Demonstrate the current state of the product
  • Possible outcomes:
    • Product does not work at all
    • Product works but some stories are incomplete
  • Product Backlog may be updated based on feedback

Sprint Retrospective

  • Reflect on the Sprint:
    • Was it a success or a failure?
    • Were estimates accurate?
    • Was task assignment and teamwork effective?

Use KPT method:

  • K (Keep) – What worked well
  • P (Problem) – What caused issues
  • T (Try) – What to improve next time

Write KPT feedback in Excalidraw

Time Schedule

Phase Time
Sprint Planning 6 min
Implementation (1) 10 min
Daily Scrum 3 min
Implementation (2) 10 min
Sprint Review 5 min
Sprint Retrospective 6 min
Total 40 min

This mini-sprint is a simulation of real Scrum practices. Focus on collaboration, feedback, and continuous improvement.