2024 Scrum Overview | Scrum Practices | Scrum in Real Life

Explore how agile emerged as a flexible, iterative approach to software development, guiding Scrum through the agile manifesto’s four values and twelve principles.

Learn why agile emerged for high uncertainty projects, using short cycles and adaptation, and how the agile mindset, manifesto values, and lean practices guide Scrum, XP, and Kanban.

Uncover the agile manifesto's four values and twelve guiding principles, prioritizing individuals and interactions, working software, customer collaboration, and responding to change to drive iterative delivery.

Compare agile and traditional project management to highlight empirical Scrum for knowledge work. Show how industrial work suits waterfall, with planning at the outset and value delivery at project end.

Explore the landscape of agile methodologies, including Scrum, Extreme Programming, lean product development, Kanban, and more. See Scrum as a framework for addressing complex problems, enabling high-value, customer-focused product delivery.

Adopt an agile mindset to manage high uncertainty, change, complexity, and risk, guided by the Agile Manifesto and 12 principles, contrasting agile with waterfall, and highlighting Scrum and Extreme Programming.

Define Scrum as a lightweight framework rooted in empirical process control, guided by the Agile Manifesto. Emphasize transparency, inspection, and adaptation to address complex work with evolving requirements.

Explore how empirical process control underpins scrum through transparency, inspection, and adaptation, and how the five values—commitment, courage, focus, openness, and respect—drive team success.

Explore the typical scrum timeline from vision and product roadmap to the product backlog and sprint lifecycle, including sprint planning, daily scrums, reviews, and retrospectives.

Show how Scrum uses empirical process control and the Agile Manifesto as principles. Frame Scrum as a lightweight framework with three pillars—transparency, inspection, adaptation—and values: commitment, courage, focus, openness, respect.

Explains the three Scrum team roles, Scrum Master, Product Owner, and developers, and their responsibilities, governance, and the self-organizing, cross-functional unit focused on the product goal, with no subteams.

The product owner maximizes value by managing the product backlog and aligning it with business requirements. They prioritize backlog items by value, ensure transparency, and communicate with customers and stakeholders.

Developers in scrum are self-organizing, cross-functional professionals who deliver a releasable increment each sprint, own the sprint backlog, uphold the definition of done, and share accountability as a single team.

The Scrum Master, the expert of scrum, coaches self-management, removes impediments, and guides product backlog management, stakeholder collaboration, and organizational adoption to maximize scrum value.

Scrum requires developers to share a single role and collaborate, with all responsible for outputs; Scrum masters differ from traditional managers and governance distributes management across three roles.

Develop people and teams to drive a motivated, high-performing, cross-functional, self-organizing Scrum team through teaching, facilitation, mentoring, and coaching under servant leadership and governance.

Learn the fixed scrum roles and team structure, including the scrum master, product owner, and developers, with cross-functional, self-managed teams of ten or fewer and backlog prioritization to maximize value.

Explore the five scrum events—the sprint, sprint planning, daily scrum, sprint review, and sprint retrospective—and learn how time boxes enable regularity, transparency, and inspection and adaptation within a sprint.

Turn the sprint into the heartbeat of Scrum by fixing a timebox where the team turns user requirements into a potentially releasable increment.

Sprint planning initiates the sprint by selecting product backlog items the team can deliver, creating the sprint backlog, and defining a sprint goal through collaborative, self-organized and self-managed scrum team.

Learn how the daily scrum, a 15-minute standup, helps developers inspect progress toward sprint goal and adapt the backlog by answering three questions: what was done, what's next, and impediments.

Inspect sprint outcomes and adjust product backlog during sprint review, a four hour time boxed session with developers, product owner, and customers to gather feedback and plan next steps.

Explore sprint retrospective as team's lessons learned session to inspect people, relationships, process, and tools, and to identify and plan improvements that boost quality and effectiveness for the next sprint.

Explore how the sprint acts as the container for all scrum events, including sprint planning, daily scrum, sprint review, and sprint retrospective, guiding governance and continuous improvement.

Explore the three scrum artifacts—product backlog, sprint backlog, and the increment—and how each provides a commitment (product goal, sprint goal, and definition of done) to maximize transparency and guide progress.

Learn to manage the product backlog as an evolving, prioritized list of user stories driven by business value and ROI, guiding sprint planning toward a clear product goal.

Define and track the sprint backlog, a plan by and for the developers comprising top-priority product backlog items, the sprint goal, and a flexible delivery plan updated throughout the sprint.

Identify the increment as a usable stepping stone toward the product goal, additive to increments, verified, ready by sprint end, and defined by the definition of done to support empiricism.

Align the definition of done across the scrum team to ensure a shared understanding of completion and enable product owner approvals of potentially releasable increments through sprint planning and reviews.

Visualize remaining work over time with a project burndown chart to monitor progress toward the goal, compare planned versus actual story points, and show the product owner's forecast with developers.

Maximize transparency with Scrum artifacts: product backlog, sprint backlog, and increment. Assign commitments to each artifact: product goal, sprint goal, and definition of done; burndown charts show progress.

Explore generally accepted scrum practices and tools for translating user needs into the product backlog, estimating with story points and planning poker, and visualizing sprint progress with burndown charts.

Explore how to write user stories and assign story points, using the three C's and INVEST, and apply t-shirt and Fibonacci sizing to plan and prioritize the backlog.

Learn planning poker, a collaborative Scrum estimation technique using story points to size backlog items, align team understanding, and converge on sprint estimates.

Master velocity in Scrum to forecast what the team can deliver. Convert ideal time to actual days and account for distractions to predict sprint and project duration using story points.

Explore task boards in scrum to track sprint progress with columns: to do, in progress, and done. Highlight information radiators that keep the team transparent and enable self-management.

Use burndown charts to track daily completed story points and remaining work, helping teams forecast sprint goals, while burn up charts show completed work and scope changes.

Learn how product backlog refinement, or grooming, keeps the backlog prioritized and up to date through collaboration between the product owner and developers, with the product owner accountable.

Explore story maps as a high-level planning tool for scrum backlogs, identifying the backbone features, the walking skeleton, and prioritized releases to align teamwork early.

Learn how to run effective sprint, release, and project retrospectives in scrum by following five steps, gathering data, generating insights, and turning them into actionable backlog items with owners.

Explore spikes as time-boxed problem-solving tools, distinguish architectural and risk-based spikes, and learn how refactoring reduces technical debt and narrows the cone of uncertainty in scrum.

Size user stories with story points and planning poker, track velocity with task boards and burndown or burn up charts, and refine the backlog while addressing spikes and technical debt.

Prioritize value driven development, risk reduction, in agile and Scrum to deliver high business value early through incremental release and sprint planning, guided by ROI, IRR, and NPV.

Learn value driven prioritization in scrum as the product owner ranks the backlog by value. Balance financial value, cost, learning, and risk using simple, 100 point method, dot voting.

Deliver incremental value by releasing working product increments each sprint, from test to production, and apply the MVP or MEF concept as a small yet complete feature set.

Implement work in progress limits to manage task flow and reduce bottlenecks. Apply Kanban principles within Scrum to limit in-progress items, cut waste, and minimize rework.

Refine backlog grooming to stay flexible with customer needs, adding stories, prioritizing or removing items, and slicing work as scope changes, with the product owner coordinating estimates and sprint planning.

Explore value driven planning in scrum, detailing how releases and sprints organize short time-box development periods to deliver valuable outcomes through high level visioning, story maps, and just enough estimating.

Hold a stakeholder-inclusive release planning meeting to prioritize the backlog items, size user stories (must-have and should-have), and slice them into sprint-sized chunks, delivering valuable functionality in upcoming releases.

Sprint planning gathers team and product owner to review backlog items, clarify user stories, break them into tasks with acceptance criteria and tests, and use task boards for sprint backlog.

Assess business value with present value, net present value, and internal rate of return. Prioritize backlog by business value, backlog grooming, and planning across three levels for value-driven delivery.

Explore four real-life scrum case studies to learn governance, adaptation, and practical application of the scrum framework, events, artifacts, and team roles for project success.

Follow a real-world scrum case starring Alex as product owner to gather requirements, build and prioritize a product backlog, plan sprints, hold daily scrums, review increments, and reflect in retrospectives.

Refocus the business by narrowing 100 projects to 12 priorities. Apply scrum at scale with one project per team in two-week sprints to boost productivity and roi.

Learn how the Dutch railways replaced a failed waterfall project with a distributed Scrum approach, delivering a large, multi-team information system with early releases, velocity tracking, and automated testing.

See how a major European telecom deployed scrum at scale with cross-functional feature teams and a single backlog, guided by Executive Action Team, to boost app ratings in six months.