Master Agile & Scrum Basics

compare waterfall and agile, showing how agile delivers mvps in one-month cycles through requirements, design, implementation, and verification, with rapid customer feedback to reduce risk.

Learn how to define a minimum viable product and apply an incremental, iterative agile approach to deliver usable releases, gather customer feedback, and accelerate product evolution.

Explore agile as a mindset guided by four values and twelve principles, and see how it drives practices like Scrum, self-organizing teams, definition of done, cadence, time box, and retrospectives.

Prioritize individuals and interactions and working software to boost collaboration and efficiency over processes, tools, and comprehensive documentation, countering waterfall bottlenecks.

Prioritize customer collaboration over contract negotiation and embrace responding to change over following a plan to keep agile teams aligned with customer needs and deliver the right product.

Master agile principles by exploring the agile manifesto and the 12 principles, prioritizing customer value through early and continuous delivery of valuable software, and embracing change in development.

Learn how the scrum framework is built on empiricism and lean thinking, with transparency, inspection, and adaptation guiding three accountabilities, five events, and artifacts: product backlog, sprint backlog, and increment.

Learn scrum artifacts and commitments, including the product backlog, sprint backlog, and sprint goal, and how the product owner and developers collaborate with the Scrum Master.

apply the scrum pillars of transparency, inspection, and adaptation to reveal artifacts like the product backlog, sprint backlog, and increment; use formal events to inspect progress and adapt to feedback.

Explore the five scrum values, respect, openness, courage, commitment, and focus, and how they drive the sprint goal, transparency, inspection, and adaptation within the scrum framework.

Explore the scrum team, the unit of scrum, with one product owner, one scrum master, and up to eight developers, all cross-functional, self-managing, and focused on a single product goal.

Developers in a scrum team plan the sprint backlog, adhere to the definition to deliver a high quality product, adapt daily toward the sprint goal, and hold each other accountable.

The expansion pack formalizes stakeholders as a Scrum role, including customers, users, decision makers, regulators, sponsors, experts, and non-human entities like laws and AI, with regular engagement to validate value.

Explore the Tuckman model of forming, storming, norming, performing, and adjourning to understand team development and collaboration. Apply these stages to navigate conflicts, build trust, and achieve cohesive performance.

Explore how the product backlog guides agile teams by prioritizing product backlog items to maximize value, maintain transparency, and align with the evolving product goal, managed by the product owner.

Frame the sprint goal as a single commitment by the scrum team to why this sprint exists, guiding the sprint backlog and allowing flexible PBI delivery toward the objective.

Explore how increments in Scrum build toward the product goal, delivering usable, thoroughly tested value and aligning with the definition of done to ensure cohesive, quality increments.

Define the definition of done to ensure quality and transparency in scrum based products, detailing when an increment meets criteria such as code review, automated tests, and updated documentation.

Master agile product development using scrum, guiding teams from idea to release with a prioritized product backlog, PBIs and user stories, sprint planning, daily scrums, and reviews.

Learn how user stories drive agile product development by articulating who, what, and why, meeting invest criteria and aligning the scrum team around customer value.

Master the three c's of good user stories—card, conversation, and confirmation—to help agile teams write clearer, actionable stories with defined acceptance criteria and measurable value.

Explore the Rice framework for prioritizing product initiatives by quantifying reach, impact, confidence, and effort. Apply the scoring method to rank roadmaps and drive data-driven decisions.

Daily Scrum is a 15-minute, time-boxed event for all developers to inspect progress toward the sprint goal and plan the next 24 hours, with optional attendance by the product owner.

Inspect and adapt drives the sprint review, a time-boxed scrum event that gathers the whole team and key stakeholders to review the sprint increment and update the product backlog.

Explore how sprint retrospective drives continuous improvement by inspecting last sprint, refining people, processes, tools, and the definition of done, then turning insights into actionable improvements.