Agile Scrum for Beginners Complete Framework + Certification

Scrum is a lightweight, empiricism-based framework that uses an iterative backlog-driven process to deliver potentially shippable product increments and adapt through transparency, inspection, and adaptation.

Trace the history of scrum from the 1986 Harvard Business Review article to the Agile Manifesto, highlighting the cross-functional team approach and its use in software, hardware, marketing, and sales.

Compare waterfall's linear, top-to-bottom phases and a complete requirements document with Scrum's minimum viable product-driven, 1–4 week iterations that deliver working software and enable fast feedback.

Explore the Scrum framework's roles, events, and artifacts, from the product backlog and product owner prioritization to sprint planning, daily scrum, reviews, retrospectives, and pillars of transparency, inspection, and adaptation.

Explore how scrum's three rules frame the development and delivery of products. Identify the product owner, scrum master, and development team, and how self-organizing cross-functional teams deliver iterative product increments.

Drive scrum success by prioritizing and clarifying the product backlog, and ensuring it is visible for the development team and stakeholders to align what and when to build.

The lecture follows Sara, the customer side product owner, as she gathers broad requirements from stakeholders through workshops and interviews and refines them into a GIRoA backlog of epics.

Lead the Scrum team as a servant leader, coaching the product owner and development team, removing impediments, facilitating Scrum events, and guiding backlog prioritization to maximize value and productivity.

As the scrum master, I collaborate with customers to define goals, set a backlog aligned with value, and pivot when needed, using Jira to prioritize backlog items.

The development team in Scrum is self organized and cross functional, estimating and delivering the sprint goal with a nimble 3–9 member size.

Identify the development team's required skills based on project goals, then staff a cross-functional four-person team with UI design, database design, programming, and system testing, and self-organizes for sprint planning.

Explore the three central scrum artifacts, product backlog, sprint backlog, and the increment, and learn how each drives the product creation process.

Identify the product backlog as a prioritized list of known requirements, with top items detailed for development and testing, and refined through backlog refinement by the product owner and team.

Visualize the product backlog on JIRA, detailing backlog items, epics, estimates, and priorities. The product owner Sara updates and shares the backlog to guide development and ensure transparency.

Align the sprint backlog with upcoming sprint goals by visualizing work on a scrum board, using columns and swim lanes to promote transparency, collaboration, and timely increments.

See the sprint backlog on a scrum board, with remaining days and a sprint goal, tracking items from to do through in progress, testing, acceptance test to done across epics.

An increment is a working, shippable software piece that sums all items completed in the current sprint with prior increments, and must be usable and meet the definition of done.

This increment shows how sprint outcomes align with the product vision by delivering login, adding customers, and centralized customer information system, validating progress toward customer satisfaction and efficiency goals.

Explore how scrum events, sprint planning, daily scrum, sprint review, and sprint retrospective, form a time-boxed loop within each sprint, promoting regularity and minimizing non-scrum meetings.

Define a sprint as a one-to-four week cycle hosting all work, with a sprint goal and flexible plan, delivering working software and renegotiations with the product owner when needed.

Discover a sprint example with a two-week cycle featuring sprint planning on Tuesdays at 9:30, sprint review mondays, daily scrum mornings, retrospective after events, backlog refinement, and a downloadable template.

Collaborate in sprint planning to define what can be delivered next using the product backlog, increment, velocity, capacity, and product owner priorities, then set the sprint goal and sprint backlog.

Develop a sprint by selecting top backlog items based on velocity, create and populate a sprint, set duration and goals, and track progress on a scrum board.

The daily scrum is a 15-minute standup for the development team to synchronize work. Each member shares yesterday’s work, today’s plan, and any impediments, while avoiding status reporting.

See a real world daily scrum from Jira where team members share yesterday's work, today's plan, and impediments, with quick synchronization and follow-ups outside the meeting.

Demonstrate completed work from the last sprint and gather stakeholder feedback during the sprint review, or demo. Prepare attendance, confirm completion, and present only finished increments for evaluation and pivots.

Demonstrate a real world sprint review with invited stakeholders via Skype, review completed and planned backlog items, re-prioritize unfinished work, and collect feedback on the sprint goal.

Join the Scrum team for the sprint retrospective to review the completed sprint, assess what went well and what can be improved, and inspect and adapt the process.

Conduct a real world sprint retrospective using sticky notes or a whiteboard to capture what went well and what can be improved, then vote with three dots to prioritize actions.

Explore scrum metrics that promote transparency, a key pillar of empirical process control, and cover estimating, planning poker, burn down, and velocity to master agile measurement.

Explore estimation techniques for requirements, including our method, t-shirt sizes, and story points, and learn to estimate hours for development, testing, and acceptance with velocity and planning poker previews.

The team estimates each backlog item on a zero-to-100 scale to plan the next sprint, while the backlog remains a living, changing list.

Use planning poker to engage the scrum team in estimating refined backlog work with cards or apps. Facilitate rounds, timebox discussions, and reach consensus by comparing high and low estimates.

Estimate the backlog with planning poker by comparing story points to a baseline, using cards or an app, and discussing each requirement’s effort and the definition of done.

Learn how burndown charts visualize a sprint’s progress by plotting work left versus time, compare actual progress to the ideal line, and use it to identify overcommitment or oversized estimates.

See a real-world burn down for a sprint tracked in an automated burn down chart, updated as progress and comments convert 36 story points into real-time insights, including non-working days.

Velocity measures how much work the team completes per sprint and uses the average across three sprints to predict next sprint capacity and planned story points.

See a real world velocity example in agile scrum, tracking 36 story points per sprint, then learn to calculate average velocity with a tool or Excel.

Learn the core Scrum framework, roles, artifacts, events, and metrics, including product backlog, sprint backlog, increments, planning poker, burn down chart, and velocity, with a contrast to waterfall.

Master Scrum and Agile concepts, differentiate Agile from Waterfall, engage in the Scrum process with other professionals, set up and run projects using the Scrum framework, and plan next steps.

Study the official Scrum guide and the agile manifesto, including the 12 principles, compare Scrum.org and Scrum Alliance certification options, and consider an advanced course to deepen practice.

Refine the product backlog by detailing, estimating, and ordering items with the product owner and development team, adding and removing items as needed in a weekly sprint cadence.