Free Coupons for Lean Agile Certifications - SM, PO, PM, BA

Agile is a set of values and principles, not a methodology. It enables iterative, value-driven, faster software delivery and inspect and adapt across many methodologies.

Discover how scrum, a lightweight framework, enables teams to deliver software iteratively through sprints, focusing on value, empiricism, and lean thinking to solve complex problems.

Explore the five scrum values—commitment, courage, focus, openness, and respect—and the three pillars of transparency, inspection, and adaptation to guide agile project teams toward continuous improvement.

Explore the three pillars of scrum—transparency, inspection, and adaption—and learn how visibility, regular inspection, and adaptive improvement drive value and collaboration.

Explore the five scrum values: courage, focus, commitment, respect, and openness, and see how transparent collaboration, sprint goals, and learning drive value and quality in agile teams.

Explore the five timeboxed scrum events: sprint, sprint planning, daily scrum, sprint review, and sprint retrospective, and learn about backlog refinement as an ongoing activity.

Explore how a sprint acts as heartbeat and container of scrum, a fixed duration from one week to one month, housing planning, daily scrum, review, retrospective, and a self-testable increment.

Plan the upcoming sprint through collaborative sprint planning, defining a clear sprint goal, refining product backlog items into tasks, and estimating effort with velocity to avoid overburdening the team.

Learn how the daily scrum synchronizes developers to review sprint progress, update the sprint backlog and scrum board, and address impediments with a 15-minute, any-technique format.

conduct the sprint review to inspect results, gather stakeholder feedback, and adjust upcoming work based on the definition of done; exclude incomplete items to the product backlog.

Sprint retrospective enables the scrum team to examine itself, identify improvement items, and set top priorities for the next sprint, updating the definition of done as needed.

Backlog refinement is an ongoing, non time-boxed process to prepare backlog items for sprint planning. It clarifies requirements, supports estimation, and prioritization with the Scrum team, usually 1–2 sprints ahead.

Explore how scrum artifacts maximize transparency of information, guiding the flow from product backlog to sprint backlog and ultimately the increment, delivered by developers with the product owner.

The product backlog is an evolving, prioritized list of requirements and the single source of truth, owned by the product owner, driving sprint work for maximum business value.

Create the sprint backlog by selecting PBIs from the product backlog to meet the sprint goal, plus a real-time plan of tasks owned and updated by developers throughout the sprint.

An increment is the cumulative sum of finished PBIs from the current sprint plus prior increments, fully tested through integration and usable, released by the product owner when feasible.

Master the scrum master role by implementing scrum within the team, coaching and mentoring members, removing impediments, and guiding self-managed teams through three pillars of empiricism: transparency, inspection, adaptation.

Explore the scrum master role, teaching lean thinking to remove waste, guiding value, flow, and quality, ensuring daily scrum communication with the product owner, and upholding scrum values.

Maximize value by owning and prioritizing the product backlog. Act as the voice of the customer, collaborate with stakeholders to identify requirements, and set the vision.

Understand the product owner's roles, accountability for release and cost of ownership, collaboration with stakeholders, backlog refinement, acceptance criteria, and scope renegotiation.

Explore the product owner's roles in agile Scrum, detailing backlog items clearly, prioritizing work toward the vision, canceling sprints when needed, and reviewing increments against the definition of done.

Developers alone produce sprint increment and ensure it meets the definition of done, while being self-managed, self-organized, and cross-functional, collaborating with the product owner and enabled by the scrum master.

Developers determine how the work is completed, picking backlog items self-organized and cross-functional, with no outside guidance, to meet the sprint goal via shared ownership, definition of done, and estimates.

Establish a definition of done aligned with organizational quality goals, promoting shared accountability for quality among the development team, while managing team changes to minimize productivity dips.

Learn Scrum basics and how ChatGPT enhances agile practices by guiding roles, events, and artifacts for iterative, transparent product development.

Master the product owner's role in backlog management and stakeholder alignment, and leverage ChatGPT to draft user stories, refine acceptance criteria, and prioritize features.

Learn how a scrum master, as a servant leader, uses ChatGPT to facilitate sprint planning, daily scrums, reviews, and retrospectives while removing impediments and coaching the team in scrum practices.

Explore how developers within Scrum collaborate to deliver a potentially releasable product increment each sprint, using ChatGPT for coding, testing, and documentation, and for task allocation, while supporting continuous improvement.

Explore scrum artifacts—product backlog, sprint backlog, and increment—and see how ChatGPT assists in prioritizing items, breaking down tasks, and tracking progress for transparent agile delivery.

Explore scrum events—sprint planning, daily scrum, sprint review, and sprint retrospective—and learn how ChatGPT can streamline facilitation, task breakdown, documentation, and continuous improvement.

Master sprint length under one month to enable inspect and adapt. Set a specific sprint goal with the product owner and developers, and track progress with velocity and burndown charts.

The rules of scrum enforce time-boxed events and a sprint goal to deliver a done, potentially releasable increment defined by the definition of done, with the product owner guiding scope.

Define the definition of done as a shared scrum team standard, owned by developers with product owner input, guiding sprint planning toward releasable software and criteria refined after each sprint.