
Begin this Scrum Master course by exploring agile foundations and Scrum history, then master the three Scrum goals, events, and practices like user stories, prioritization, and estimation.
This Lecture is a quick whistlestop tour on the history of agile and lean and how agile became the giant it is today.
In this leacture we deep dive into Empiricism and the three pillars that hold up scrum, Transparency, Inspection and Adaption.
In this lecture we take a brief look at the five Scrum Values: Commitment, Courage, Focus, Respect and Openness.
This lecture is a bonus video on the waterfall method from a recent webinar that we held.
In this lecture we break down The Scrum Framework and look at all the Roles, Events and Artifacts that take place in scrum
WE currently have a notes doc in Scrum 101 - Convert to video
In this lecture we start to break down the three scrum roles, The Product Owner, The Scrum Master and The Development Team and how they work together.
In this lecture we deep dive into the role of The Product Owner and look at how the Product Owner manages the Product Backlog and look at the relationship between the Organization and the Product Owner.
In this lecture we look at the role of The Development Team and look into how they fit in with the Organization.
In this lecture we look the role of The Scrum Master and look at key roles and responsibilities of The Scrum Master.
In this lecture we look at how The Scrum Master fits in with the team and their relationship with The Product Owner, The Development Team and The Organization.
Explore the five Scrum events, including sprint planning, daily scrum, sprint review, and sprint retrospective, and learn how these time-boxed meetings enable regular inspection, adaptation, and transparency.
Define a time-boxed sprint as delivering one body of work into a usable product increment, with sprint events, a product backlog, one-month horizons, and inspect-and-adapt.
Learn how sprint planning grounds the team with a clear sprint goal, defines the sprint backlog and plan, and aligns the scrum roles to deliver a working increment.
Define the sprint goal as the objective outlined by the product owner, drawn from the product backlog, delivering a coherent function and guiding team collaboration during sprint planning.
Attend the daily scrum, a 15-minute dev team stand-up to inspect sprint progress and plan the next 24 hours, answering the three questions about yesterday, today, and impediments.
Inspect the sprint increment, adapt the product backlog, and align stakeholders with the product direction in an informal, time-boxed sprint review led by the product owner.
Cancelling a sprint is rare and justified when the sprint goal becomes obsolete due to direction or market changes; the product owner may cancel and re-estimate backlog items.
Explore how scrum artifacts, the product backlog, sprint backlog, and the increment, represent work transparently to support value and risk decisions across the team.
The product backlog is an ordered list, a living document and the single source of truth for all product requirements, continuously evolving as the product and its environment evolve.
Define the sprint backlog as the product backlog items plus the plan for delivery, a living, flexible document not set in stone guiding the sprint goal.
Identify the increment as the sum of all completed product backlog items and prior increments, and ensure it is in usable condition and meets the definition of done.
Definition of done is a shared, product-specific quality checklist marking an increment’s completion, including branding, user acceptance testing, legal notifications, integration, and documentation, refined in sprint retrospectives.
Review the definition of done and its relation to roles, events, and artifacts, showing how the development team delivers a potentially releasable increment each sprint.
Explore monitoring progress toward goals with burn down and burn up charts. See how burn down tracks work left over time and burn up shows work completed toward releases.
Use burn down charts to track work remaining for sprint progress and release planning. Compare actual versus average trends to gauge if the team stays on track toward goal.
Note: As mentioned in video, I have included additional notes on Burn Down charts in the resource section of that lecture (ie Burn Down Charts)
Also, I have put some very high level notes on cumulative Flow diagrams under "Bonus - Monitoring Progress (Notes)"
Plan and estimate to deliver value across the enterprise, coordinating with marketing and sales. Prioritize the backlog, size the sprint backlog in sprint planning, and inform leadership with release plans.
Absolute sizing uses time units to estimate backlog, while relative sizing uses Fibonacci-like scales; baselines and triangulation with two and five help refine estimates using effort, complexity, risk, and uncertainty.
Examine the dangers of estimation as a guess with high uncertainty and how turning estimates into commitments can drive overtime and lower quality, despite agile planning and continual refinement.
We need to add the intro and outro. Note: I am not happy with the last minute or so, need to consider this as a priority two post live
Explore estimation methods in Scrum, including absolute sizing, relative sizing, and T-shirt sizing, and learn how to apply spikes and backlog grooming to break down product backlog items.
Convert story point size into duration using velocity to support release planning and sprint estimates. Account for risk, uncertainty, and complexity to explain how empirical results improve estimate accuracy.
Explore estimation techniques for agile projects, including estimation by expert opinion and estimation by analogy. Apply triangulation across stories and use planning poker to set consistent story points.
learn planning poker for relative estimation of product backlog items, using baselines, Fibonacci sequences, and consensus-driven rounds to reach agreement.
The product backlog is the single source of truth, and the product owner is accountable for prioritization. Prioritization uses value, risk, dependencies, and release ability, guided by empiricism and transparency.
Prioritize the backlog by value and size to deliver high-value items early and gain faster customer feedback; balance what to deliver with how to implement it during sprint planning.
Master the MoSCoW technique to align stakeholders on backlog priorities in scrum through a focused workshop. Assign items to must have, should have, could have, or won't have this time.
Please note: I have included a simple Relative Weighting calculator in excel format.
IT is also available here as a google sheet:
https://docs.google.com/spreadsheets/d/11JZKLLDCl-aXcmlraAwseDRIIaxVBst6BT3aTboBFlk/edit?usp=sharing
Dont forget the spreadsheet here
Explore the difference between release and deployment, noting evolving definitions from customer-focused releases to focused deployments, and how agile and devops enable frequent, safe, complete changes to the live environment.
This course leads the student on a journey starting with the Scrum basics and leading to more advanced Scrum thinking and practices.
Part 1 focuses on complete beginners and is comprehensive in covering all areas of Scrum basics, starting with the history of Scrum, moving onto definitions, theory and values, before a deep dive into the the 3 Scrum roles, the 5 Scrum events and the 3 Scrum Artifacts.
This section will also help you in your journey to Agile Scrum certification and I have cross referenced this course with a number of the popular Scrum master certifications like the PSM1 and the CSM to make sure it covers all the areas needed.
Part 2 focuses on more advanced topics. It focuses beyond the Scrum guide and into topics that are referenced in the Scrum guide but not elaborated on. User stories, value, prioritization, release management and estimation are each discussed
It not only dives into the theory but also gives specific focus to some of the more widely used techniques / practices in Scrum today, giving the student a more practical grounding, moving away from the question of “what is Scum?” onto the question of “how do we use Scrum?”
We also designed two practices tests which not only help you in your revision but the format and difficulty give you a preview into the types of questions that you will need to answer in your Scrum Master certification
And beyond this, we have added a section focusing on the background to Scrum. Focusing on agile project management with topics like Agile, Lean and Waterfall, to help you with context on Scrum and how it evolved.
And finally, we are continually adding more clips and webinars covering practical topics like “what to do on Day one of a new Scrum team?” and many more. This section is regularly added to!
So, if this is what you need, I hope you enjoy it!
Dave