Prep for Scrum with Kanban Exams

Explore scrum, the popular agile framework for software development, including its rules, scrum team roles, events, and artifacts like the product backlog, sprint backlog, and increment.

You've reached your first milestone by starting this Udemy course, joining the top 20% of learners, and you’ll benefit from playback controls, English subtitles, Q&A support, and quality-checked lectures.

Explore the three pillars of scrum—transparency, inspection, and adaptation—rooted in empiricism, and see how the definition of done, events, and artifacts enable clarity and early course corrections.

the product owner bridges developers and customers to maximize value, is the sole owner of the product backlog, and ensures clear, visible requirements for the team.

Learn how scrum developers form a cross-functional, self-managing team that delivers a done, potentially releasable increment each sprint by following the sprint backlog toward the sprint goal.

Explore the scrum master's servant leadership role, guiding the scrum team, coaching self-management and cross-functionality, removing impediments, and coordinating events to drive value, transparency, and organizational adoption.

Explore the five scrum events—sprint, sprint planning, daily scrum, sprint review, and sprint retrospective—and how timeboxing drives transparency, inspection, and adaptation to align goals and deliver a potentially releasable increment.

Define a scrum sprint as a fixed timebox, typically 1–4 weeks, to deliver a potentially releasable product increment, guided by sprint planning, daily scrum, sprint review, and sprint retrospective.

Explore sprint planning, where the product owner and developers define what will be delivered and how, set the sprint goal, and produce the sprint backlog within an eight-hour timebox.

Daily scrum is a 15-minute, daily event for developers focused on evaluating progress and planning the next day, with flexible formats that boost communication and decisions toward the sprint goal.

Foster collaboration between the scrum team and stakeholders by reviewing the sprint's completed work and product increment, updating the backlog, and planning the next sprint with transparency and adaptive priorities.

Inspect the sprint team's performance in the retrospective, identify what went well and what could be improved, and drive growth, process and tool improvements within a three-hour time box.

Introduce scrum artifacts that reveal work, value, and empiricism, including product backlog, sprint backlog, and increment, with commitments like product goal, sprint goal, and definition of done.

Explore the product backlog as an emergent, ordered list and single source of work. Product owner and developers refine PBIs through backlog refinement toward the product goal amid market feedback.

Explore sprint backlog, a live, developer-owned plan that pairs the sprint goal with selected product backlog items and an actionable delivery plan, with real-time transparency to the team and stakeholders.

Explore the scrum artifact increment—the final, usable, inspectable output of a sprint that cumulatively advances the product goal, guided by the definition of done.

Explore the advantages and disadvantages of Scrum, including transparency, daily stand-ups, team accountability, fast delivery, and continuous customer feedback, alongside risks like scope creep and poorly defined tasks.

Explore how Kanban visualizes the workflow to drive process improvement, identify bottlenecks, and serve as an easy, flexible starting point for teams adopting agile with a Kanban board.

Visualize team workflow with a kanban board, physical or Jira, using columns from input queue through analysis, development, build ready, testing, and release to reveal inefficiencies.

Identify inefficiencies in a kanban workflow by analyzing testing bottlenecks and WIP limits, and learn to set practical WIP caps to improve flow and prevent backlogs.

Identify underutilization of resources using a Kanban board and improve flow by shifting to a pull-based system. Team-driven flow management reduces lead time and overload, optimizing work across steps.

Manage unequal sized tasks in Kanban by adding a scoping phase to create tasks of equal size, track the board, and break down long work into smaller tasks.

Explore how a kanban board uses business review feedback loops to manage rework. Mark review rounds with sticky notes to track iterations, reduce waste, and optimize wip limit for throughput.

Discover how a Kanban board reveals non product related work, such as external dependencies, demonstrations, improvement tasks, and recruitment steps, using dedicated columns and escalation as needed.

Explore the kanban daily stand up, a flexible, board-focused meeting that tracks task progress, highlights blockers, and fosters collaboration with no fixed duration or demos.

Explore how Kanban requires teams to create explicit rules, such as WIP limits and the definition of done, to guide workflow and interaction with stakeholders.

Explains key Kanban flow metrics—work in progress, throughput, and cycle time—and how to use Little's Law and the cumulative flow diagram to predict team performance for customer questions.

Measure work in progress on a Kanban board by counting items in defined process steps, and learn how WIP limits provide transparency and control over the workflow.

Measure cycle time from pickup to completion and compute flow efficiency to optimize flow with WIP limits and capacity adjustments.

Measure throughput as amount of work completed per unit time, using tasks, stories, or features. Track it per step to reveal bottlenecks and distinguish it from arrival rate and velocity.

Explore Kanban flow metrics with work item age and aging work in progress charts. Learn to track start dates and use percentiles to gauge flow health and identify at-risk items.

Learn to compute work item age and craft an aging work in progress chart in Excel, with 50th, 70th, 85th, 95th percentile lines, safe/danger bands, and a combo chart.

Explore how leading and lagging indicators measure performance, predict outcomes, and guide improvements. Balance current metrics with cycle time and work item age to drive delivery.

Discover Little's law and how throughput, work in progress, and cycle time link in a stable flow, illustrated through a burger shop analogy and a flow-based development system.

Use Little's law to assess process predictability by averaging throughput, cycle time, and WIP across multiple sprints; avoid forecasting future outcomes.

Explore the five assumptions behind Little's law and learn how consistent units, equal arrival and throughput, steady WIP, complete workflow, and stable WIP age ensure reliable flow.

Explore the cumulative flow diagram (CFD) to visualize Kanban workflow, measure lead time, cycle time, throughput, and work in progress, and identify bottlenecks to improve delivery.

Explore how scrum with kanban blends strict scrum with flow, using a kanban board, defined workflow, and wip limits to pull work and improve cycle time and throughput.

Integrate Kanban with Scrum by defining and visualizing a clear workflow on the Kanban board, establishing policies, steps, wip limits, and completion definitions to strengthen Scrum rules.

Implement work-in-progress limits to create a pull-based flow in Scrum, with the Scrum team setting limits and using WIP, work item age, and service level metrics to sustain throughput.

Define and calculate service level expectation from historical cycle times to estimate delivery dates, set a benchmark for flow, and use percentile values (50th, 85th) to guide prioritization.

optimize batch size in scrum to balance holding costs and transaction costs, enabling faster feedback and more efficient inspection and adaptation across sprints.

Discover how Kanban integrates with Scrum, placing the Kanban board at Scrum events and using flow metrics like throughput and cycle time to guide sprint planning and delivery.

Celebrate crossing the final milestone and completing the course to receive your certificate of completion after the next lecture.