Explore how Scrum turns a problem into a product backlog and sprint backlog, delivering increments through a Scrum team of product owner, developers, and Scrum Master.

Position Scrum as a mechanism to optimize the value delivery system in complex environments, explaining why adapting what to do and how to do it guides changes.

Compare waterfall and agile mindsets, highlighting how Scrum guides change through iterative releases, customer feedback, and evolving product vision in complex environments.

Explore how agile, rapid, and lean concepts interrelate to deliver the correct product vision with minimal waste in Scrum.

Trace the Agile Manifesto’s origins from Snowbird 2001 and explore its values and principles that underpin Scrum, crafted from lightweight approaches for high-uncertainty software development.

Explore the agile mindset and manifesto, focusing on uncovering better ways and being responsive to changes. Learn how teams collaborate with customers, deliver value, and treat setbacks as learning opportunities.

Explore the four agile values that power complex problem solving: individuals and interactions over processes and tools, working product over documentation, customer collaboration over contract negotiation, and responding to change.

Explore the 12 agile principles, classified into project, product, people, and process, and learn how to apply project-focused agile principles to sustain agility.

Explore five agile principles for project management, emphasizing early delivery of valuable, working products. Embrace changing requirements, deliver software frequently, and measure progress by working software.

Explore agile people principles that prioritize face-to-face communication, daily collaboration with business and developers, and empower motivated individuals in self-organizing teams through servant leadership.

Explore agile principle 12: reflect regularly to improve effectiveness, tune behavior, and continuously enhance how a product is built. Embrace ambidexterity: build the right product and build it right.

Discover how scrum implements agility as a flexible framework to address complex problems, deliver high-value results, and is adopted by over 60% of software teams.

Explore the cone of uncertainty and how variability in estimates shrinks over time, guided by VUCA and agile methods that outpace the traditional waterfall in software.

Recap assessment questions on the cone of uncertainty and sustainable pace, and clarify Scrum as an iterative, incremental framework aligned with the Agile Manifesto for PSM I prep.

Discover how scrum's aspects connect to drive change, from the product backlog and product goal to sprint planning, sprint backlog, daily scrums, increments, sprint reviews, retrospectives, and the product owner.

Learn how Scrum transforms ideas stored in the product backlog into value through sprints, led by the product owner who ensures backlog quality and transparency.

Discover how sprints transform the product backlog into valuable working software through sprint planning, daily scrums, and sprint reviews, with product owner driven backlog refinement driving iterative delivery.

Define the sprint backlog as the output of sprint planning and the input for sprint execution, outlining the sprint scope, sprint goal, selected product backlog items, and an actionable plan.

Explore the Scrum theory, empiricism, and lean thinking underpinning Scrum. Deepen your understanding of Scrum rules and recommendations to prepare for the PSM I assessment.

Explore how empiricism underpins scrum with transparency, inspection, and adaptation, using short, timeboxed sprints and events to learn, adapt, and manage risk.

Explore the five Scrum values—commitment, courage, focus, openness, and respect—and see how they drive transparency, inspection, and adaptation, building trust between the team and stakeholders.

Analyze Scrum theory and values through sample PSM I questions, confirming the pillars of transparency, inspection, and adaptation, and the five Scrum values: commitment, courage, focus, openness, and respect.

Understand the Scrum Team composition—the product owner, the Scrum master, and the developers—and their accountabilities, product backlog, and product goal to deliver a valuable increment each sprint.

The lecture tells a story about a company using Scrum where the product owner provided by the customer lacked authority, leading to delayed feedback, wasted sprints, and no real value.

Developers are cross-functional and self-managed, turning product backlog ideas into usable increments through autonomous sprint planning with the product owner. A mix of specialists and generalists ensures teamwork and redundancy.

The scrum master serves both the organization and the scrum team, removes impediments, coaches self-management, guides backlog management to maximize value, and leads Scrum adoption.

Learn how the Scrum Team allocates technical, contentual, and managerial contributions across the Scrum Master, Product Owner, and Developers, including shared practices like Product backlog refinement and progress inspection.

Learn how the Scrum Master promotes the Scrum process, removes impediments, and fosters self-management, with rules on undone work, the definition of done, and the sprint review.

Explore the Scrum Team's three accountabilities—Product Owner, Scrum Master, and Developers—and how they collaboratively create product increments, order the backlog, and support self-management and empiricism.

Explore how agile, Scrum artifacts and events turn product backlog into an increment, guiding sprint planning, sprint backlog, sprint reviews, and sprint retrospectives, with scaled Scrum and PSM I assessment.

Demonstrates how Scrum works by detailing events and artifacts through a real production case study of a web app, and invites applying Scrum to your own projects.

Explore konyu, a proxy for bidding on Yahoo Auctions Japan items, with language and currency settings, authentication, wallet funds, watch lists, and shipment after winning.

Explore Scrum artifacts—the Product Backlog, Sprint Backlog, and Increment—and how their commitments, like the Product Goal, Sprint Goal, and Definition of Done, maximize transparency, enable inspection, adaptation, and guide progress.

Analyze artifact transparency through a sensor analogy, linking signals and feedback to the product backlog. Collaborate as the Scrum Master with the Product Owner, developers, and stakeholders to boost transparency.

Connect the Product Goal to the product vision and strategy, drive the Product Backlog and Sprint Goals, and use feedback and increments to validate progress.

Explore the product backlog as the single source of work for the scrum team, detailing just-in-time items, refinement, and the path from epics to ready backlog items for a sprint.

Explore how epics describe features and how user stories use card, conversation, and confirmation to capture customer value with acceptance criteria, within a living product backlog.

Learn how to order the product backlog using size, risk, value, and dependencies to maximize return on investment, with examples prioritizing high-value user stories.

Learn how agile estimation uses lightweight methods to forecast work with story points and planning poker, balancing effort and accuracy while noting that estimates are never exact.

Agile teams use relative sizing with story points on a semi-Fibonacci scale to estimate product backlog items, not time, with planning poker guiding the team to agreement.

Discover planning poker, a collaborative, consensus-based agile estimation method using story points. Teams discuss backlog items, privately estimate with cards, then reveal and align.

Classify backlog items with the Kano model into mandatory, linear, and exciter to prioritize value, using surveys to gauge desirability and inform ordering.

Explore how backlog refinement stays emergent and ongoing, breaking down items into description, order, and size to ready top backlog items for the sprint. Note the unofficial Definition of Ready.

The definition of ready is not Scrum Guide practice, but provides criteria to determine when a product backlog item is ready. It promotes transparency and shared understanding through backlog refinement.

Monitor progress toward the product goal by summing remaining work, and learn the Scrum Guide's three practices: burndown, burnup, and community flow in the upcoming lectures.

Explore how a burn-down chart tracks remaining product backlog effort over time, using story points, and compares actual progress to a baseline velocity to reveal late delivery and backlog refinements.

Learn how a burn-up chart tracks work completed and scope changes from sprint to sprint, showing how backlog additions affect total work and project progress.

Explore the cumulative flow diagram to visualize how product backlog items move through states over time, comparing it with burn-up and burn-down charts and highlighting work in progress.

Learn how the product backlog is ordered by the product owner, what defines the backlog, and how ready items fit a sprint, including epics, user stories, and the product goal.

Learn about the Increment and its commitment to the Definition of Done, building understanding before delivering the next product increment.

Define the definition of done as a formal set of criteria that marks a product increment complete and meets quality measures, promoting transparency and shared understanding of what done means.

Identify who defines the definition of done by aligning with organizational standards and external guidelines; Scrum teams adopt the organization’s DoD or create a product DoD with a single standard.

Define the definition of done as a continuous, evolving set of criteria that improves quality, with retrospectives guiding changes and static code analyzers exposing technical debt in increments.

Explore technical debt as the cost of poor software practices, including code decay and architecture deterioration, and examine how Scrum practices like the definition of done and retrospectives manage it.

Explore how the increment is cumulative across sprints, from completed product backlog items that meet the definition of done, and remains usable and releasable, driving empiricism and product learning.

Clarify Scrum Increment concepts from PSM I questions: an Increment is usable but not required to be released, and the Definition of Done governs release readiness and adaptation.

Understand sprint planning, daily scrum, sprint review, and sprint retrospective, along with the sprint backlog, all time-boxed to promote transparency and provide formal inspection and adaptation.

Analyze upcoming work and map backlog items to the product goal. Define a sprint goal and select items for the sprint backlog, considering capacity, velocity, and the definition of done.

Define the sprint backlog by setting the sprint goal, selecting backlog items, and decomposing them into technical tasks that developers own and map to system components.

Explore sprint planning essentials by analyzing the sprint backlog, sprint goal, and Scrum Guide guidelines, including the eight-hour time-box for two-week sprints.

Explains that the sprint backlog is a real-time, visible plan for the sprint goal with selected backlog items and initial tasks on a Scrum board, while remaining work can change.

Analyze key truths about the sprint backlog, its emergent nature, and how developers own and modify it through collaboration with the product owner to stay aligned with the sprint goal.