Agile Fundamentals Certification

Explore waterfall versus agile delivery, emphasizing rapid MVP iterations, incremental cycles of requirements, design, implementation, and verification, and using customer feedback to reduce risk and guide product increments.

Understand the agile MVP approach by building iterative, usable increments—from a skirting board to a car—guided by customer feedback from early adopters to improve the product quickly.

Agile is a mindset guided by four values and twelve principles, not mere ceremonies. Learn how Scrum, self-organizing teams, definition of done, cadence, and timeboxing enable design thinking and SAFe.

Explore agile values that transform software development by prioritizing individuals and interactions over processes and tools, and working software over comprehensive documentation, fostering collaboration, productivity, and adaptability.

Explore agile values that favor customer collaboration over contract negotiation and responding to change over following a plan, guiding teams to build the right product with customers.

Explore the agile manifesto and 12 principles, focusing on early customer value, welcoming change, frequent working software, collaborative teams, face-to-face communication, and regular reflection and adjustment.

Scrum is a lightweight framework, not a methodology, enabling value through adaptive solutions for complex problems, with a scrum master, product owner, and scrum team coordinating backlog, sprints, and increments.

Explore the Scrum framework built on empiricism and lean thinking, with pillars of transparency, inspection, and adaptation, and accountabilities, time-boxed events, artifacts, and the definition of done.

Describe scrum artifacts and commitments, including the product backlog, sprint backlog, and sprint goal; show how a team delivers an increment that meets the definition of done.

Explain scrum theory rooted in empiricism and lean thinking, emphasizing waste reduction, essential focus, and iterative, incremental delivery by a cross-functional team guided by transparency, inspection, and adaptation.

Discover the three scrum pillars—transparency, inspection, and adaptation—and how visible artifacts like the product backlog, sprint backlog, and increment enable inspection and adaptive improvement.

Explore the five scrum values—commitment, openness, courage, respect, and focus—and how they guide sprint goals, openness about challenges, and team collaboration in agile product development.

Lead a scrum team of ten or fewer—the product owner, Scrum Master, and up to eight developers—focused on one active product goal and delivering a useful increment each sprint.

Developers plan the sprint, adhere to the definition, and adapt daily to deliver a high-quality product increment, while handling architecture, testing, documentation, and UI design within the scrum team.

Drive value as the product owner by defining and communicating the product goal, managing and ordering the product backlog, and ensuring transparency for stakeholders and the scrum team.

Establish the scrum per the scrum guide by guiding the product owner, developers, and stakeholders through clear product backlog items, events, and artifacts to improve team effectiveness.

Define stakeholders per the scrum guide expansion pack, including customers, users, decision makers, sponsors, regulators, experts, and AI and laws, with intentional, regular engagement to deliver value.

Explore the Tuckman model of group development and its five stages—forming, storming, norming, performing, adjourning—to understand leadership, conflict, cohesion, trust, and collaboration in teams.

The product backlog is a living, transparent plan of PBIs ordered by ROI and other factors to maximize value. The product owner manages it as the single source of work.

Define and sustain a single active product goal that guides the scrum team's backlog and sprint planning, with measurable progress, clear boundaries, and ongoing collaboration with the product owner.

Define the sprint backlog as the plan to achieve the sprint goal, listing PBIs and the how-to tasks to refine, develop, and test, while remaining adaptable as learnings emerge.

Define the sprint goal as a single, binding objective that explains why the sprint exists, guides the team's focus, and provides flexibility in implementing PBIs.

An increment is a concrete, usable stepping stone toward the product goal. Each increment adds value in scrum, is verified, and must meet the definition of done.

Establish the definition of done as the formal state of an increment that meets quality measures. Provide examples like code review, automated tests, and updated documentation to show completion.

Explore agile product development with scrum, guiding teams from a new product idea to market-ready increments through vision crafting, backlog prioritization, sprint planning, and continuous improvement.

Explore the core concept of a user story, a concise end-user focused description of who, what, and why, applied with invest criteria to deliver valuable, testable agile outcomes.

Explore the three Cs of good user stories: card, conversation, and confirmation, and learn how this dialogue-based approach helps agile teams create clear, actionable requirements with testable acceptance criteria.

Apply the rice framework to quantify reach, impact, confidence, and effort, multiply impact by confidence and divide by effort to obtain a priority score for data-driven roadmaps.

Explore sprint fundamentals in scrum: fixed lengths up to one month and continuous backlog refinement. Protect sprint goals and deliver product increments for predictable progress and faster learning.

Sprint acts as a container for all other scrum events, including sprint planning, daily scrum, sprint review, and sprint retrospective, with a product increment delivered at sprint end.

Explore how scrum events enable inspection and adaptation of artifacts such as the product backlog, sprint backlog, and product increment, guided by the scrum guide.

Understand sprint planning within scrum to set a sprint goal, build a sprint backlog, and forecast how to deliver value with the product owner and developers.

The daily scrum is a 15-minute time-boxed event mandatory for all developers to inspect progress toward the sprint goal and plan 24 hours ahead, with flexible structure and optional attendees.

Explore how the time-boxed sprint review inspects the sprint increment with the scrum team and stakeholders, updates the product backlog, and supports strategic planning for the next sprint.

Inspect how the last sprint went, focusing on people, processes, tools, and the definition of done. Timebox the sprint retrospective and identify actionable improvements for the next sprint.