Agile and Scrum Master Certification Preparatory Class

This lecture gives a brief description, definition and explanation of what scrum is a management frame work for delivering value

In this lecture, you will learn:

1. simple definition of what methodology is

2. definition of what frameworks are

3. applicative differences between framework and methodology

In this lecture you will learn the basic ideology/theory of scrum. It explains what empiricism is and what lean thinking is and how these ideologies make up the scrum theory. Concepts like iteration, lean thinking, rationalism etc are discussed.

In this lecture you will learn the definition of complexity, you will learn about complexity science and what complex problems are. Students will benefit by understanding Complexity Science, a field that studies evolving, unpredictable, yet adaptive systems. You will learn to distinguish truly complex problems (with many unknown unknowns) from those that are merely complicated. This knowledge provides a powerful mental model to better analyze and navigate challenges in business, technology, and everyday life, helping you choose the right approach for the right problem and avoid applying simple solutions to complex situations.

This lecture describes what simple problems are and provides various examples of them.

This lecture describes, defines and gives examples of what complicated problems are.

This lecture explains how to identify complex problems, marked by unclear definitions, unpredictable outcomes, and interconnected variables. These challenges lack linear solutions and involve frequent surprises. Examples include curing cancer or raising a child. It emphasizes the need for adaptive, iterative approaches rather than fixed methods to manage uncertainty and reach effective solutions.

This lecture teaches on the five key differences between complex and simple systems. One can learn that in complex systems, elements are self-organizing and their interaction leads to unpredictable, emergent behavior. In contrast, simple systems have codependent parts that create predictable, linear outcomes. Complex systems adapt, while simple systems merely respond to stimuli.T he learner is advised to consult the attached resources for further reading.

This video explains empiricism in Agile and Scrum, where complex problems are solved through experimentation, not just planning. It contrasts simple work (like building a house) with complex challenges (like raising a child) to show why adaptation is key. Viewers will learn how Scrum uses transparency, inspection, and adaptation (TIA) to navigate uncertainty and continuously deliver value.

After this lecture, you will gain a clear understanding of Transparency, the first and most crucial pillar of the Scrum framework. Viewers learn how making work visible to both the team and stakeholders is essential for making good decisions, reducing project risk, and increasing value. It explains how transparency in key artifacts like the product backlog and sprint backlog enables the other pillars of inspection and adaptation, forming the foundation of empirical process control in any complex project.

Learners will understand the vital role of Inspection, one of Scrum's three pillars. You'll see how Scrum's five events (like the Daily Scrum) are specifically designed to provide a regular rhythm for inspecting progress and work. This helps teams detect deviations and potential problems early, ensuring everyone agrees on the value being created and preventing issues from escalating.

Viewers will grasp the concept of Adaptation, the third pillar of Scrum. You'll learn why empowered, self-managing teams are crucial for making quick adjustments based on what they discover during inspection. The key takeaway is that adaptation drives continuous improvement, ensuring the process and product are always evolving to better meet goals and deliver value.

This lecture mentions the five scrum values in form of a mnemonics C FOR C.

This lecture explains the benifits of the values of courage, commitment and focus as scrum values. Students will gain a clear understanding of three core Scrum values: Courage, Focus, and Commitment. You will learn why courage is essential for transparency and asking for help, how focus keeps the team aligned on the Sprint Goal without distraction, and how commitment is about dedication to the team and its goals. This knowledge helps foster a more effective and collaborative Scrum environment.

Trainees will learn about the crucial Scrum values of Respect and Openness. You'll understand why respecting team members as skilled individuals is vital in a non-hierarchical team and how being open about work and challenges builds the transparency needed for success. This lesson is key to fostering a strong team dynamic.

This lecture explains the fundamental structure of a Scrum Team. You will learn the three core accountabilities (Scrum Master, Product Owner, Developers), the ideal team size for staying nimble (10 or fewer), and how multiple teams can work on a single product while sharing one Product Owner and Product Backlog.

You will gain a deep understanding of the Scrum Master role. This video details how a Scrum Master acts as a servant leader who serves the Scrum Team, the Product Owner, and the wider organization by coaching, removing impediments, and ensuring the Scrum framework is understood and enacted correctly.

This lecture expantiante on the stances of the product owner as a Visionary, Collaborator, Customer Representative, Decision Maker, Experimenter and Influencer.

Participants will learn about the role and four key accountabilities of Developers on a Scrum Team. You will understand that they are responsible for creating the sprint plan (sprint backlog), instilling quality by adhering to the Definition of Done, adapting their plan daily, and holding each other accountable as professionals.

This video provides a foundational understanding of the five Scrum Events. It focuses on the Sprint as the "containing event" for all other activities. You'll learn why sprints have a fixed length, what happens during a sprint, and how they provide a consistent rhythm for turning ideas into value.

This lecture introduces the five formal events in Scrum, with a special focus on the Sprint as the "heartbeat of Scrum." Learners will understand that the Sprint is not a meeting but a time-boxed container for all work. You'll grasp its fixed-length nature and its role in providing a cadence for inspection and adaptation.

Viewers will gain a complete overview of the Sprint Planning event in Scrum. You'll learn its purpose (initiating the sprint), who attends (the whole Scrum Team), and the three key questions it answers: "Why is this sprint valuable?", "What can be done?", and "How will it get done?". The video also clarifies the event's output (the Sprint Backlog) and its time-box rules.

This video will teach you the purpose and function of the Daily Scrum. Learners will understand why this short daily meeting is crucial for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the upcoming day. You'll grasp how this event improves communication, identifies impediments, and promotes quick decision-making within the team.

This lecture explains what sprint review is, when it begins in a scrum event, who attends it, and the functions of the various accountabilities in the event. You will learn the purpose and structure of the Sprint Review. You'll understand that this is a working session, not just a presentation, where the Scrum Team and stakeholders inspect the sprint's outcome. The goal is to collaborate on future adaptations of the product backlog based on what was accomplished and learned.

This lecture explains what the last scrum event is -sprint retrospective, when it begins in a scrum event, who attends it, and the functions of the various accountabilities in the event. This lecture clarifies the purpose of the Sprint Retrospective. Learners will understand that this internal team meeting is focused on improving quality and effectiveness. The team inspects how the last sprint went regarding individuals, interactions, processes, and their Definition of Done, creating a plan for improvements in the next sprint.

This video highlights the differences between Sprint Review and Sprint Retrospectves as scrum events. You will learn the crucial differences between the Sprint Review and the Sprint Retrospective. This video clarifies that the Review focuses on inspecting the product with stakeholders, while the Retrospective is a team-only event for inspecting the process. Viewers will understand who attends each meeting, what is discussed, and their distinct purposes.

Scrum Artefacts are the values we deliver in scrum, this video teaches us by explaining and listing what those values are, introducing the Product Backlog, Sprint Backlog and increment. This video teaches you about the three official Scrum Artifacts. You will learn that the Product Backlog, Sprint Backlog, and Increment are designed to maximize transparency. A key takeaway is understanding how each artifact has a corresponding commitment (Product Goal, Sprint Goal, and Definition of Done) that provides focus and a measure of progress for the team.

This lecture teaches about Product Backlog, its definition, who refines it and who are responsible for coming up with lists of what makes it up. Viewers will gain a clear understanding of the Product Backlog in Scrum. You'll learn that it's the single source of work for the team and what "ready for selection" means. The video explains the ongoing process of backlog refinement, clarifying how the Product Owner and Developers collaborate to break down and size items, ensuring work is understood before a Sprint begins.

The product goal is the entire object of collaboration in scrum to deliver to the stakeholders what the team considers value. The product goal describes the future states of the product. This lecture teaches that.

Viewers will learn the core concepts of Product Backlog Refinement (PBR). You'll understand that it's an ongoing activity, not a formal event, where the team breaks down and clarifies backlog items. The video uses a simple, practical scenario to show how this collaborative discussion between the Product Owner and Developers ensures work is well-defined before a Sprint starts.

This video teaches two common techniques for Product Backlog Refinement: User Stories and Planning Poker. You'll learn the INVEST criteria for good user stories and how they encourage conversation. It also explains how the collaborative estimation game of Planning Poker helps teams agree on the size of work items, clarifying that developers are ultimately responsible for estimations in Scrum.

This video provides a deep dive into the Sprint Backlog, clarifying that it is a plan made by and for the Developers. You'll learn its purpose is to guide the team toward the Sprint Goal and how it provides a real-time, visible picture of the work. It also explains how the Sprint Backlog is created in Sprint Planning and inspected daily during the Daily Scrum.

You will learn the crucial role of the Sprint Goal. The video explains that it is the single objective for a Sprint that provides focus and encourages the team to work together, not on separate, disconnected tasks. Viewers will also understand that while the scope of work can be negotiated with the Product Owner during a Sprint, the Sprint Goal itself must remain unchanged.

This video offers a comprehensive overview of the Scrum artifact called the Increment. It clarifies what defines a functional Increment and explains the process for ensuring it meets the required quality standard, known as the Definition of Done. Furthermore, the lecture details how multiple Increments are integrated and discusses the specific conditions under which they can be released, including who is responsible for that decision.

This video explains the importance of the Definition of Done (DoD) in Scrum. You'll learn that it's a formal description of quality that an increment must meet to be considered complete. Viewers will understand that the DoD creates transparency by providing a shared understanding of "done," and that any work not meeting it cannot be released or shown in the Sprint Review.