Agile Scrum Mastery: Certification + Project Simulation 2026

Discover the product backlog, a prioritized, visible artifact at the heart of Scrum that guides what to build and in what order. Backlog items include features, defects, improvements, and spikes.

Master the deep product backlog by applying detailed, emergent, estimated, and prioritized criteria, and use backlog grooming and just in time refinement toward the MVP.

Uncover how user stories use the A3C card structure—card, conversation, and confirmation—to capture who, what, and why, with acceptance criteria and ongoing dialogue guiding agile work.

Lead as the scrum master, establishing Scrum, coaching the team, defending against interference, unblocking impediments, and acting as a change agent to improve team effectiveness.

The scrum master serves the team, removes impediments, and ensures scrum events are positive, productive, and kept within the timebox. They help define the product goal and facilitate stakeholder collaboration.

Learn how to prepare for sprint planning with a groomed backlog, updated user stories, an up-to-date product roadmap, a clear definition of done, and a team-defined sprint goal.

Join the sprint pre-planning session to finalize backlog readiness, using silent estimation with Fibonacci story points to order 24 backlog items and align the team on sprint length.

Use the go roadmap template to build a goal oriented product roadmap guiding sprints toward the nine-month MVP, detailing releases, user stories, metrics, and stakeholder alignment.

Define a robust, living definition of done as a checklist that confirms a sprint's work is potentially shippable, including design review, code completed, end user documentation, testing, and release.

Prepare the sprint goal for Homeslice using the sprint goal template, outline backlog and user stories for a basic search experience to validate designs via user testing.

Defines sprint goal as a unifying objective, with commitments from developers and product owner, and permits sprint backlog changes to meet it, while enforcing the definition of done for increments.

Timeboxing assigns fixed time boxes to all scrum events, including sprint planning, daily scrums, sprint reviews, and retrospectives, and even spikes, to keep the sprint focused.

Explore the sprint planning agenda, including the sprint goal, backlog and demo date, timeboxing to four hours, and breaking stories into tasks for a two-week sprint.

The product owner must attend sprint planning to collaboratively refine scope, importance, and estimates for each story, guiding sprint backlog selection and sprint goals through direct dialogue with the team.

Learn how cross-functional developers design, build, test, and integrate sprint increments, embrace self-management and transparency, and develop T-shaped skills for flexible collaboration.

Identify the roles of developers in Scrum, create and size sprint backlog items, plan delivery of a usable increment, and understand timeboxed events and accountability.

Learn how estimation and velocity shape sprint scope and the MVP release by sizing stories, measuring velocity from completed work, and calculating duration as size divided by velocity.

Explore estimating stories using man days, t-shirt sizes, or story points, with story points as a relative measure of volume, risk, and complexity that stays independent of individual skills.

Estimate stories with planning poker to engage the full team, reveal simultaneous estimates, discuss differences, and converge on the total work using Fibonacci-based points.

Lead a sprint planning session to define a basic search experience goal and estimate stories like search by location, search by price, and view a property profile with planning poker.

Discover how to communicate sprints with a one-page info sheet displayed on the wall, detailing team, sprint number, sprint goal, stories with sizes, velocity, key dates, and availability.

Arrange the team space to foster creativity and collaboration by seating the team together with good audibility and visibility, designating a dedicated design area and sprint backlog.

Discover how the scrum master builds a wall-based sprint backlog with columns for not checked out, checked out, and done, tracks progress with a burndown chart, and manages unplanned items.

Lead a daily scrum that starts on time in front of the task board, keeps updates concise, and prioritizes sprint goal progress and impediments for developers.

Define the sprint backlog as the sprint goal, PBIs, and delivery plan by the developers; daily scrums inspect progress toward the goal and adapt the backlog in a 15-minute timebox.

Manage flow in scrum by balancing parallel work and swarming to meet the sprint goal, avoid idle work and multitasking, and target bottlenecks for faster value delivery.

The sprint is the heartbeat of scrum, delivering a usable increment. Runs one week to one month; product owner may cancel if needed; quality remains non-negotiable.

Dispel the sprint review myth by emphasizing collaboration and transparency; move beyond demos to jointly inspect the increment, actively involve stakeholders, and keep the backlog central.

Inspect sprint outcome with Scrum team and stakeholders, decide adaptations toward the product goal, present only items meeting the definition of done, and update backlog in a four-hour sprint review.

participate in a time-boxed sprint retrospective under three hours to reflect on the last sprint, identify what worked and didn’t, and prioritize improvements via dot voting for concrete actions.

Wrap up project one by building a vision board and a backlog via user story mapping. Execute sprint planning, daily standups, and the sprint review to deliver a shippable increment.

Explore project two by adapting Scrum for remote teams using Trello, turning story maps and vision outputs into a digital product backlog and preserving agile values.

Explore how Trello uses boards, lists, and cards to organize tasks, boost transparency, and support agile scrum collaboration.

Set up a Trello board for scrum, using boats as projects, lists for not checked out, checked out, and done, with stories as cards.

Lead a hands-on Trello exercise to build a home slice backlog, generate 24 story cards from pasted titles, and organize them into product and sprint backlogs.

Master task and deadline management in agile scrum using Trello: convert tasks to stories, use checklists, assign due dates and reminders, and leverage keyboard shortcuts.

Collaborate with your team by setting a board background and avatar, inviting members, assigning stories, and managing observers and permissions to streamline sprint work.

Learn how to show task dependencies in Trello by linking stories with a checklist, using the book appointment and cancel appointment example to enforce prerequisites.

Learn to segment stories with labels in Trello by epics, blockers, and bugs, applying and managing color-coded labels and shortcuts for rapid project tracking.

Master Trello search and filters to quickly locate stories by labels, assignees, or deadlines, using keyboard shortcuts like Q and F across boards.

Add story points in Trello using the Agile tools power up, assign estimates to cards, and monitor sprint progress with work in progress limits to keep the backlog manageable.

Run sprint retrospectives in Trello by forming a Homeslice team, moving the board, and guiding the retro with what worked, what didn’t, and actions.

Jira powers software scrum projects with built-in backlog, stories, bugs, epics, and burndown reports. Confluence integration supports enterprise documentation and migrating from physical scrum walls to digital backlogs.

Organize and prepare the backlog in a next-gen Jira project by creating and detailing stories, dragging them into sprint one, and defining the definition of ready.

Discover how Confluence stores documentation and product requirements, linked to Jira backlog items, using templates for meeting notes, OKRs, and product plans.

Explore creating automation rules in Jira Next-Gen, including auto-assigning issues when moved to checked out and updating start dates, with sprint backlog setup and testing.

Add story point estimates to backlog items and epics in next gen projects, enabled in project settings, and use them to drive sprint reports and monitor progress.

Monitor sprint health by analyzing burn down and burn up charts, scope changes, and velocity, then use the cumulative flow diagram to spot bottlenecks and predict future capacity.

Master next gen Jira administration by creating projects, editing project settings, managing users and access levels, and configuring keys, issue types, visibility, and features.

Learn Confluence administration by linking Jira and Confluence, creating and managing spaces (site and personal), using templates, setting labels, and configuring permissions to control access and collaboration.

Discover Scrum Guide 2020 updates: simpler language, fewer prescriptive rules, renamed development team to developers, a new product goal, and three-part sprint planning to guide value.