Agile Scrum Fundamentals: A One-Hour Crash Course

Explore how a Scrum team, formed by the Product Owner, Scrum Master, and Developers, turns the product backlog into valuable increments each sprint through self-managed, cross-functional collaboration toward product goal.

Maximize value delivery by the product owner through backlog prioritization aligned with the product goal, with developers' work guided under the Scrum Master's oversight.

Developers in Scrum transform backlog items into usable increments, work cross-functionally, self-manage, and share accountability, balancing specialists and generalists to enable collaboration and autonomy in sprint planning.

Explore how Scrum operates through a real-case study simulating a web app, detailing events and artifacts. Learn to apply Scrum to your own projects now.

Explore a case study of Konyu, a proxy for Yahoo Auction Japan, and its features from search and bidding to wallet payments and shipment.

The product goal defines a future state guiding the Scrum Team and shaping the product backlog, a vehicle to deliver value whose long-term objective the product owner communicates.

Define a measurable product goal that guides the scrum team toward the product vision. Use a vision board example to set targets, features, dates, and metrics that validate success.

Organize the product backlog as an ordered emergent list of needed improvements, prioritized by the product owner, refined into small user stories with acceptance criteria that fit a sprint.

Deliver vertical increments that provide usable features each sprint, with architecture ready to handle new features. Serve as the compass of Scrum, guiding stakeholders and enabling authentic feedback.

Define the definition of done as a set of criteria that marks when an increment meets quality measures and aligns the Scrum team and stakeholders, guiding feedback and sustaining velocity.

Learn how sprint planning launches the sprint with a clear sprint goal. Align product backlog items to the product goal and consider capacity, definition of done, and specialist input.

Developers finalize the sprint backlog by aligning the sprint goal with selected product backlog items and decomposing them into actionable tasks, using sketches and team consensus to forecast work.

Develop the product by performing cross-functional development work across sprints, visualize progress with scrum boards and swim lanes, and move backlog items from to do to done.

Explore the daily scrum, a 15-minute, timeboxed meeting for the team to review progress toward the sprint goal, update the sprint backlog, and surface impediments through three questions.

Understand how the sprint review inspects the increment, gathers feedback from users and stakeholders, and updates the product backlog to advance toward the product goal in a time-boxed session.

Learn how to execute a Sprint Review by presenting the increment to stakeholders, ensuring only done work is shown, and fostering transparency, collaboration, and market analysis.

Conduct the sprint retrospective to inspect and adapt the Scrum team, discuss what went well, what didn't, and adjust the definition of done to improve people, process, and tools.

Apply the Scrum fundamentals learned to your organization, analyze current scenarios, and use useful increments to drive the product vision and team improvements. Share your success to inspire others.