Mastering Agile & Scrum (From Basics to Real Delivery)

Understand the Agile mindset, principles, and why teams worldwide rely on it.

What is Agile ?

What is Scrum? and is it the same as Agile ?

Why do I have to switch and learn it?

What is the difference between Agile and Waterfall in the real world

The 4 Core Values of the Agile Manifesto:

1. Individuals and interactions over processes and tools
   Focus on people and communication rather than rigid systems.

2. Working software over comprehensive documentation
   Deliver real, usable results instead of endless paperwork.

3. Customer collaboration over contract negotiation
   Work closely with the customer throughout the project.

4. Responding to change over following a plan
   Adapt to changes instead of sticking blindly to an initial plan.

   
   

The 12 Principles of Agile (summary version):

1. Deliver value to the customer early and continuously.

2. Welcome changing requirements, even late in development.

3. Deliver working software frequently.

4. Business people and developers must work together daily.

5. Build projects around motivated individuals.

6. Prefer face-to-face communication.

7. Working software is the main measure of progress.

8. Maintain a sustainable pace.

9. Continuous attention to technical excellence and good design.

10. Simplicity — maximize the amount of work not done.

11. The best architectures and designs emerge from self-organizing teams.

12. Regularly reflect and adjust to become more effective.

Scrum Master, Product Owner, and Development Team responsibilities

Product Owner

Represents the customer or business.

Manage Backlog and priority.

Scrum Master:

Serves as a facilitator and coach

Manage Agile Process

Development:

A cross-functional group of professionals

Do the product increment

• A lightweight Agile framework focused on delivering value in short cycles

• Work happens in time-boxed iterations called Sprints (1–4 weeks)

• Team is cross-functional — everyone helps deliver value

• Progress is visible and transparent through artifacts & ceremonies

• Frequent inspection & adaptation through regular events

• Encourages continuous improvement every sprint

• Customer feedback is built-in, not postponed to the end

• Delivers usable “Increment” every sprint — not theory or half-done work

Product Backlog, Sprint Backlog, and Increment explained.

Product Backlog

A prioritized list of everything the product might need, managed by the Product Owner.

Sprint Backlog

The set of Product Backlog items selected for the current Sprint, plus a plan for delivering them.

Increment

Product Backlog = المستقبل
Sprint Backlog = الحاضر
Increment = النتيجة

What is a Product Backlog?

A dynamic, ordered list of everything the product may need in the future

Who Owns the Product Backlog

The Product Owner is responsible for managing, ordering, and refining the backlog.

How to Build a Product Backlog

Start with the product vision, gather ideas and requirements, and convert them into user stories.

How to Order (Prioritize) the Backlog

Items are ordered by value, urgency, customer impact, and effort.

It’s a Living Document

The backlog is never "finished" — it is constantly refined and updated.

How to define a story using “As a user, I want…” format.

I — Independent

The story should be self-contained, so it can be developed and delivered without depending on other stories.

N — Negotiable

The story is not a contract; it can be discussed and adjusted.

V — Valuable

The story must deliver value to the user or the business.

E — Estimable

The team should be able to estimate the effort required to complete the story.

S — Small

The story should be small enough to be completed within a single sprint.

T — Testable

The story must have clear acceptance criteria so it can be tested.

Practical methods to make stories small, testable, and deliverable.
What is an Epic?

A large user story that is too big to complete in a single sprint.

Why Split Stories?

To make them small, clear, testable, and deliverable in one sprint.

Practical Methods to Split Stories

1. By Workflow / Steps

2. By User Role

3. By Business Rules / Scenarios

4. Split based on different conditions or scenarios.

5. By CRUD Operations

   
   

Techniques for estimating user stories accurately and collaboratively.

1- Why We need to estimate in the first place

2- Most common ways of estimation

3- what is Story Point

4- Fibonacci Sequence

Continuous improvement of backlog clarity and prioritization.

الهدف النهائي: القصة تكون جاهزة 100% قبل تدخل السبرنت (Definition of Ready)

How to select stories, set goals, and define the Sprint plan.

In this role-play video, we explore some common Sprint Planning challenges that Scrum teams face in real life. Through realistic scenarios, you’ll see how to handle:

1. Over-commitment pressure from the Product Owner.

2. Pickup partially groomed stories.

Learn how to protect team capacity, ensure realistic commitments, and end Sprint Planning with clarity and shared ownership. Perfect for Scrum Masters, Product Owners, and Agile teams looking to improve planning skills.

Purpose, best practices, and common anti-patterns.

In this video, we explore a common Daily Scrum challenge where the meeting turns into a detailed technical discussion and exceeds the 15-minute time-box. Through a realistic scenario, you’ll learn how to keep the Daily Scrum focused, time-boxed, and aligned with the Sprint Goal, while handling technical discussions in the right way.

1. External Work Outside Sprint Scope

2. Daily Scrum Turns Into a Technical Discussion

How to demonstrate progress and gather feedback effectively

In this video, we explore two common backlog grooming challenges that Scrum teams face in real life:

1. “We Already Discussed This Offline or in the Past” – where only part of the team has context from prior discussions, leading to confusion during estimation.

2. “This Is Small, Trust Me” – where the Product Owner assumes a story is simple, but hidden technical complexity or dependencies create uncertainty for the team.

How sprint review must be done in the best way

In this video, we explore a common Sprint Review challenge where the Product Owner criticizes the team’s work without understanding the hidden complexities and challenges they faced. Through a realistic scenario, you’ll learn how to handle aggressive or critical feedback professionally

Turning insights into actionable improvement steps.

In this video, we explore a common Retrospective Review challenge,

where the team turn the retrospective into Blaming Battle

A brief welcome video explaining what this section covers, what tools we will use, and what students will achieve by the end , including hands-on Scrum and Jira experience.

High-level explanation of the client request (PRD) : a mobile app that connects cargo owners with truck drivers. We will summarize the business goal, main users, and core features (search, offers, accept, negotiation).

Practical demonstration of a Scrum project in Jira, workflows, and issue types.

Turn client requirements into structured epics and user stories. Learn how to write a good user story (As a… I want… So that…)

How to groom and refine user stories, split stories if needed, making sure the stories are ready for next sprint.

estimate story points, handling conflicts and over estimation

Live demonstration of working on user stories, updating status

Look at a sprint mid way , check progress

Simulate the Sprint Review meeting, show completed features, and demonstrate how to close a sprint

Discuss lessons learned, what went well, what can improve, and how feedback loops drive continuous improvement.

Wrap up what we built, what Agile concepts were used, and suggest next steps

How a Story travels through Scrum

Visualize progress of sub-tasks and Stories using real-time data.

Visualize progress of Bugs using real-time data.

Thank you for completing the course!

In this closing video, we wrap up the key lessons, share final advice for applying Agile and Scrum in real projects, and guide you on what to do next in your learning journey.

A quick, motivating send-off to help you start using everything you’ve learned with confidence.