Agile Ways of Working: Scrum, Kanban & Lean Agile Practices

Trace the history and evolution of agile from iterative and incremental development to the Agile Manifesto, and explore scaling frameworks like SAFe, Scrum, and Kanban.

Clarify that agile is a mindset, not a framework, and embrace change through delivering value, collaborating with customers, adapting requirements, and continuous improvement via iterative delivery.

Discover the Agile manifesto's four values: individuals and interactions over process and tools; working software over documentation; customer collaboration over contracts; and responding to change over following a plan.

Learn the twelve Agile Manifesto principles and how they apply to real projects, including customer satisfaction through early delivery, frequent working software, and sustainable, continuous improvement.

Identify value, map the value stream, create flow, establish pull, and pursue perfection through continuous Kaizen to maximize customer value and minimize waste.

Apply Kaizen, the continuous improvement mindset, by making small, regular changes that accumulate to deliver faster software delivery, better quality, and smoother collaboration within agile practices.

Explore how agile and traditional project management differ, contrasting waterfall planning with iterative delivery and showing when each approach best fits changing requirements and uncertainty.

Explore how Scrum, a lightweight, adaptive framework, helps teams tackle complex problems through iterative delivery in sprints, leveraging feedback, empiricism, and lean thinking to deliver value.

Explore the three pillars of Scrum—transparency, inspection, and adaption—and how they build trust, enable visibility of progress, and guide adjustments for better outcomes.

Explore the five Scrum values—commitment, focus, openness, respect, and courage—and how they drive transparency, inspection, and adaption in agile teams.

Explore how the Scrum framework integrates people, events, and artifacts to deliver value in small increments through empiricism, transparency, inspection, and adaptation.

Define sprint as a fixed time-box that acts as the heartbeat of scrum. Keep a consistent duration and a clear sprint goal to enable fast feedback and value delivery.

Explore the daily scrum, a 15-minute, developer-focused stand-up that inspects progress toward the sprint goal, adapts the sprint backlog, and plans the next 24 hours through coordination.

Inspect the sprint increment with stakeholders, gather feedback, and decide next steps to maximize value, emphasizing collaboration, definition of done, and timely adaptation.

The product backlog is an ordered, evolving list that serves as the single source of work for the Scrum team, guiding value delivery toward the product goal.

The sprint backlog turns the sprint goal into a living plan by selecting product backlog items for the sprint and detailing the developers' actionable plan, evolving while ensuring transparency.

The product owner leads value maximization in scrum by owning the product backlog, prioritizing high-value work, and guiding collaboration with stakeholders and developers toward a clear product goal.

Developers in scrum are cross-functional, self-managing teams that build a valuable increment each sprint, create and adapt the sprint backlog, and maintain quality through collaboration and collective ownership.

Visualize work with a kanban board and cards, limit work in progress, maximize flow from todo toward done, and track lead time with a pull system.