Scrum and SAFe 101: An Introduction for Absolute Beginners

Reintroduce Scrum’s framework: three artifacts (product backlog, sprint backlog, increment) with commitments and a definition of done, five events, and three roles (Scrum master, product owner, developers) grounded in empiricism.

Define the three Scrum roles—Scrum master, product owner, and developers—and explain how each role facilitates value, removes impediments, and sustains timeboxed events.

Learn how user stories drive Scrum work by turning a plain-language to-do list into a shared understanding. Explore alternatives like system shall statements and use cases, and the card-conversation-confirmation framework.

Learn how story points measure work size and effort through relative sizing—blueberries versus watermelon—and scales like Fibonacci and t-shirt sizing, with antipatterns and no estimates.

the sprint is the core time-boxed scrum event, usually 1–4 weeks, yielding a sprint backlog and a potentially deliverable, fully functional product increment, begun by sprint planning.

Sprint planning begins the sprint, time box to two hours per week, using product backlog priorities to align with the sprint goal and produce a sprint backlog and delivery plan.

Master the daily scrum, a 15-minute morning standup, not a status meeting, where developers coordinate toward the sprint goal, surface blockers, and keep communication concise.

Run through the sprint review as an inspect and adapt event that invites all stakeholders to hands-on test the increment, gather real feedback, and decide whether to pivot or continue.

Conduct the sprint retrospective, the team’s inspect-and-adapt event, to discuss sprint outcomes, uncover hidden assumptions, manage conflicts, and plan improvements for the next sprint.

Explore how Scrum artifacts—product backlog, sprint backlog, and increment—use commitments like product goal, sprint goal, and definition of done to boost transparency, focus, and empiricism.

Define the lean–agile mindset as the foundation of safe, embracing lean thinking and the agile manifesto; learn how self-organizing teams deliver value with consistent outcomes and the essential management buy-in.

Explore the four SAFe core values: alignment, transparency, respect for people, and relentless improvement, and how they support a lean, agile mindset through a common language and visualized work.

Explore SAFe lean-agile principles, applying systems thinking and an economic view, delivering early with integrated learning cycles, and using WSJF to balance value flow, cadence, and cross-domain planning.

Learn lean and agile leadership within the SAFe framework. Leaders create the change vision, coalition, and army of change agents to model lean and agile, with psychological safety and training.

Explore the safe framework's vision concept, distinguishing portfolio and solution visions, and learn how swot and toes analyses guide realistic, aspirational product direction.

Explore the safe implementation roadmap, a lean agile leadership guide. It outlines 13 steps, tipping points, and four key business benefits.

Explore how SAFe defines an agile team as a cross-functional group of ten or fewer and how stream-aligned, enabling, platform, and subsystem teams deliver value with Scrum or Kanban.

Grow team and technical agility by building cross-functional agile teams, aligning to agile release trains, and embedding built-in quality through continuous feedback and relentless improvement.

Explore team flow in scaled agile and safe, learning eight principles to visualize work, limit whip, reduce bottlenecks, and deliver value faster.

Apply Safe team Kanban to visualize a workflow with WIP limits and Kanban board columns and swimlanes, pulling work as capacity allows.

Explore how SAFe team Kanban aligns planning and delivery across an ART, sets PI objectives, replenishes the backlog, and optimizes flow with metrics like flow time and velocity.

Explore safe scrum within the agile release train, align iterations and PI objectives, and demonstrate working increments through system demos, continuous delivery, and relentless inspect-and-adapt improvement.

Explore the team backlog as an ordered list of user stories, enablers, and maintenance tasks, refined collaboratively across the ART backlog, team context, and stakeholders, with capacity guidance.

Explore architectural runway as a flexible, agile architecture that balances emergent design with intentional structure, enabling enabler stories delivered within iterations to support evolving features.

Explore Pi planning within the SAFe framework to align teams and stakeholders on a shared vision through a two-day planning event, with risk, dependencies, and confidence voting.

Explore how an agile release train unifies 5–15 cross-functional teams (50–125 people) into a long-lived, value-driven art that designs, builds, validates, and continuously releases customer value through a shared cadence.

Explore the next steps to Scrum certification across major tracks, including CSM with Scrum Alliance and PSM with Scrum.org, costs, prerequisites, and study resources at scrum guides.org.

Explore next steps for safe certification, starting with leading safe as the entry level certification, then take the not proctored exam after a two day course and $600 to $1200.