Tutorial on Agile Scrum Master.

Explore scrum roles and stakeholder management, identify who is affected, and use the onion diagram to engage the product owner, scrum master, and developers to meet needs.

Explore the scrum lifecycle, from requirement elicitation to the product backlog items, managed by the product owner, with features like chat, calls, file sharing, and encryption.

Learn to plan two week sprints, prioritize the product backlog to form a minimum viable product, and deliver a working software increment with each sprint.

Explore the Scrum lifecycle from product backlog to increments, detailing sprint planning, daily scrum, sprint review, and sprint retrospective, with roles for product owner, developers, and the Scrum Master.

the product owner guides the scrum team and holds the vision. they prioritize backlog and shape the release plan through stakeholder input to maximize value and ROI while managing risk.

Prioritize backlog items by value with product owners, using ranking to deliver the most valuable features first. Apply cost-benefit analysis and payback period to justify prioritization through cash flow projections.

Explore net present value and discounting cash flows to decide investments, compare projects with NPV and IRR, and use cost-benefit analysis to prioritize Scrum backlog items.

Prioritize backlog using risk value analysis, Moscow method, and Kano model—must have, should have, could have—while the product owner translates stakeholder input into backlog priorities and roadmap.

The scrum master serves the team as a servant leader, facilitates rituals, removes obstacles, and protects the team while supporting their use of Scrum.

Identify developers as cross-functional, generalist teammates in a Scrum team, responsible for coding, testing, and design, who collaborate and self-manage to deliver product value.

Scrum teams are self-managing and guided by the Scrum master, with the product owner prioritizing the backlog and developers pulling work into sprints, while matrix managers recruit and mentor.

Discover scrum ceremonies and the lifecycle, from product backlog to sprint delivery, covering the sprint, sprint planning, daily scrum, sprint review, and sprint retrospectives, with timeboxing and 1–4 week sprints.

Timeboxing defines a fixed duration for all Scrum ceremonies, such as sprints and daily scrums, ensuring focus, predictable delivery, and avoidance of Parkinson's syndrome and student syndrome.

Explore release in Scrum: go live timing, production deployment, and how each sprint can be a mini release with a potentially shippable product; learn timeboxing, release planning, and sprint expectations.

learn how a sprint functions as a time-boxed period in scrum, delivering a working software increment from the sprint backlog, with 1 to 4 week durations and retrospectives guiding adjustments.

Identify factors shaping sprint duration, including must-finish dates, risk, feedback availability, and urgency. Explain timeboxed sprints of one to four weeks and contrast Scrum's incremental delivery with Waterfall.

Explore the daily scrum, a 15-minute stand-up where developers report yesterday's work, plan today, and raise impediments through the three questions to sustain development flow toward the sprint goal.

Showcase the sprint's completed work, collect feedback, and adapt the product backlog to refine requirements and keep the team on track toward a potentially shippable increment.

Review the completed sprint to identify what went well and what didn’t using love it, lose it, and improve it, assign actions with the team, and keep retrospectives time-boxed.

Explore agile planning principles and multiple planning levels, from backlog grooming and sprint planning to release and portfolio plans, emphasizing time-boxed, flexible iteration toward working software.

Develop a release plan that maps the product vision to a releasable increment by estimating user stories, setting sprint duration and velocity, and prioritizing backlog items.

Velocity measures a team's sprint progress by summing completed story points, with only finished stories counting, guiding sprint planning and backlog prioritization.

Sprint planning, a key scrum ceremony, translates the product backlog into a velocity-driven sprint plan with a sustainable pace, sprint goals, and task-based estimates.

Learn to plan sprints and levels from daily to release by calculating team capacity, accounting for leaves and daily hours, and scheduling tasks, buffers, and scrum rituals for reliable velocity.

Discover how the product backlog, sprint backlog, and release backlog organize user stories and epics, guided by the product owner's value maximization and backlog grooming.

Explain how the release backlog derives from the product backlog, supports epics and stories toward release, and uses sprint backlog to break stories into tasks, with backlog refinement and grooming.

Explore how to write effective user stories in agile scrum, outlining the three Cs and INVEST criteria, and explain how to define acceptance tests, definition of done, and value-driven tasks.

Create and analyze story cards and user stories with identifiers, names, descriptions, acceptance tests, and dependencies, then group stories into epics and apply invest criteria for backlog prioritization.

Learn scrum best practices such as continuous refactoring, pair programming, and continuous integration, with refactoring defined as improving readability and maintainability without changing functionality.

Develop team skills through pair programming, where one driver writes code and the navigator guides, enabling better design, higher quality, cross-training, and effective debugging of complex logic.

Explore continuous integration from extreme programming, as teams integrate features across sprints with automated builds, single source repository, daily mainline commits, and self-testing.

Learn configuration management in scrum through automation, disciplined code check-ins and reviews, and static code analyzers, while embedding built-in quality with extrinsic and intrinsic metrics across planning, daily scrum, reviews.

Write a failing test first, then implement code to pass it, and repeat iterative cycles to evolve software, reduce defects, and enable safe refactoring in Agile.

Define done criteria for sprint, user stories, releases, and the product, with examples like design completed and reviewed by the architect and full testing, to ensure we build quality in.

Learn scrum estimation principles and units like story points and ideal days, with planning poker and affinity estimating, while understanding cone of uncertainty and the top-down vs bottom-up approaches.

Compare estimation approaches in agile by contrasting underestimation and overestimation, and explain sizing with story points or ideal days, converting ideal days to actual days amid distractions and task context.

Estimate user stories with story points using analogous benchmarking to assign relative points, then apply non-linear scales like Fibonacci and W scale to improve predictability.

Learn planning poker and affinity estimation techniques for agile teams, using Fibonacci-based card decks, story points, and t-shirt sizing to quickly estimate many user stories with time-boxed discussions.