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.

Define agile as a set of values and principles, not a methodology or framework. Deliver value through iterative development, small increments, and continuous inspect and adapt within the agile umbrella.

Explore the Agile Manifesto and its values—individuals and interactions over processes, working software over documentation, customer collaboration, and responding to change over following a plan.

Explore the 12 Agile Manifesto principles, from customer-focused early delivery and welcoming change to sustainable development, face-to-face collaboration, and self-organizing teams for maximum business value.

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.

Learn how scrum artifacts maximize transparency by shaping information from the product backlog to the sprint backlog and increment, through product owner, developers, and scrum master.

Explore the product backlog as the living, prioritized scrum artifact and single source of truth that, owned by the product owner, drives sprint work toward maximum business value.

The sprint backlog selects PBIs for the sprint, defines the sprint goal, and provides an actionable plan for delivering the increment, created and updated by developers.

Define the increment as the cumulative sum of finished PBIs from the current sprint and earlier ones, tested and meeting the definition of done, released by product owner when feasible.

Discover how a scrum team of up to ten delivers value in every sprint through product owner, scrum master, and developers, with backlog, sprint planning, daily scrums, reviews, and retrospectives.

Lead the implementation of scrum within the team, coaching, mentoring, and facilitating toward a high-performing, self-managed unit while removing impediments and educating on scrum values and agile principles.

The Scrum Master removes waste to enable lean processes, guides value, flow, and quality, and coaches developers to align with product goals, ensuring daily 15-minute Scrum and teaching Scrum values.

The product owner acts as the voice of the customer and value maximizer, owning and prioritizing the product backlog to deliver top-priority increments aligned with a clear vision.

Explain the product owner's roles, including owning and releasing the product, managing total cost of ownership, backlog refinement, acceptance criteria, and the product backlog as the single source of truth.

The product owner reduces backlog waste by detailing items for the current sprint, ensures clear and unambiguous backlog items for developers, defines the product vision, and prioritizes requirements.

Developers deliver the increment at the end of each sprint, are self-managed and self-organized, and form a cross-functional team that ensures release-ready software meets the definition of done.

Developers self-manage and select work from the product backlog, ensure cross-functional capability, own the sprint backlog, and drive progress to meet the sprint goal and definition of done.

Developers define the definition of done with organizational quality goals, uphold shared accountability for quality, and schedule sprint-boundary changes to minimize productivity dips while keeping the team under ten.

sprint begins with sprint planning and ends with sprint retrospective, keeping the sprint goal intact, renegotiating scope, and delivering an updated increment in a fixed-length cycle.

Keep sprint length under one month, set a specific, measurable sprint goal through owner–developers negotiation, and monitor progress with burndown charts and daily scrums to guide backlog and velocity.

Learn scrum rules: time-boxed events, sprint goal to deliver a releasable increment, quality defined by done, avoid scope changes, know sprint cancellation, fixed length, and the single product owner.

Defines the definition of done as a shared scrum team standard for when a backlog item is complete, guiding testing and releasable software criteria.

Learn why agile estimations matter in scrum for accountability, predicting timelines, sprint management, value delivery, and risk management, using planning poker or t-shirt sizing.

Discover how agile transcends software to become a customer-centric business mindset that delivers value through iterative development, transparency, accountability, and cross-functional collaboration.