
Master agile scrum fundamentals and the iterative delivery approach to confidently work in any scrum role. Get started with a high level overview and progressive detail to reach practical mastery.
Explore why organizations move from waterfall to agile-based delivery, emphasizing faster time-to-market, flexibility, and customer feedback through the Agile Manifesto's values and principles.
Explore the agile manifesto's four core values and twelve principles, including individuals and interactions over processes and tools, working software over documentation, and responding to change.
Learn how Scrum, a lightweight agile framework, reduces risk and delivers working software early through iterative sprints, guided by adaptation, transparency, inspection, courage, focus, commitment, respect, openness.
Compare traditional waterfall methods with agile scrum to show how waterfall works for predictable upfront planning, while scrum delivers iterative product increments and adapts to changing requirements.
Compare cost estimating in waterfall and Agile Scrum, outlining bottom-up and sprint-based approaches, and show how Agile Scrum mitigates risk with incremental value, frequent reviews, and near-term funding.
Explore key scrum terms and definitions, including roles (Product Owner, ScrumMaster, developers), artifacts (Product Backlog, Sprint Backlog, Product Increment), and events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective).
Cover the three main scrum roles: product owner, scrum master, and developers. Learn how cross-functional seven-person teams deliver agile products, with analysts, programmers, and technical architects involved.
Define the product owner's pivotal responsibilities in Scrum, including owning the product backlog and prioritizing PBIs with authority and funding, while exploring proxy product owner roles and stakeholder communication.
Lead the Scrum team as a ScrumMaster, acting as coach, guide, and facilitator to uphold Scrum principles and values, shielding developers from distractions and guiding Sprint Retrospectives to drive improvement.
Developers, the third Scrum role, deliver usable value through time-boxed sprints guided by the Definition of Done, self-organizing to plan from the Sprint Backlog, a subset of the Product Backlog.
Explore the product backlog, a prioritized list of requirements and the project’s to-do guide for Scrum. Discover user stories and how the product owner maintains and prioritizes backlog items.
Define and manage the sprint backlog, a subset of the product backlog containing user stories to develop, test, and deliver in a time-boxed sprint, using pre-sprint refinement and sprint planning.
Developers deliver a product increment at the sprint end that adds value, meets quality standards, and passes tests, interfaces with prior increments, and is production-ready under the DoD.
Explore key scrum artifacts you’ll encounter, including the product vision, product charter, sprint goal, the definition of done, burndown charts, and burnup charts.
Learn the basic cyclical approach of agile scrum, prioritizing requirements, estimating effort, delivering a two-week sprint, reviewing outcomes, and iterating with product backlog, sprint backlog, and product increment.
Learn how the product backlog is prioritized and delivered through sprints, with planning, daily scrums, reviews, and retrospectives shaping each product increment.
Define a sprint as a time-boxed 2–4 week cycle delivering sprint backlog and product increment. Agree the sprint goal with the whole team and keep it unchanged during the sprint.
Begin sprint planning with a 'what' session to define the sprint goal and select user stories, and a 'how' session where developers break work into tasks and form backlog.
Explain how the daily scrum helps developers inspect progress towards sprint goal, adapt the sprint backlog and tasks, report yesterday's work, today's plan, and impediments, with the scrum master facilitating.
Demonstrate the completed product increment to the product owner and stakeholders during the sprint review, showing only working software that meets the definition of done and guiding the next sprint.
Explore the sprint retrospective after the sprint review, focusing on individuals, team communication, scrum processes and tools, and the Definition of Done, and commit to time-boxed improvements.
Explore product backlog refinement, or pre-sprint planning, to prioritize items, split large work, and estimate effort with t-shirt sizing or Fibonacci, involving the product owner and ScrumMaster.
Define a product vision, project charter, and definition of done to start a Scrum project. Simulate sprint progress, events, tracking, and forecasting to move toward a Scrum-related role.
The product owner defines the vision to guide the Scrum team toward future value, align it with the product backlog, and adapt over time.
Discover how a project charter aligns agile scrum by outlining the product vision, project mission, and definition of success, and detailing stakeholders, scrum roles, MVP, and sprint burndown charts.
Define a clear definition of done to ensure a sprint delivers a release-ready, potentially shippable product increment that integrates with prior increments and meets business, technical, and quality criteria.
This course will provide you with the essential knowledge and techniques to successfully perform in any Scrum-related role or environment.
It is ideal for those who may be involved in a Scrum initiative for the first time and who need to be immediately effective, or 'traditional' Project Managers who wish to learn about alternative agile-based approaches to product delivery in order to widen their range of skills, capabilities and employment prospects.
The agile-based approach is covered in depth, and compared and contrasted with more traditional, waterfall-type project management in order to clearly highlight the benefits associated with iterative, incremental Product delivery.
A pragmatic, step-by-step approach is taken throughout the course in order that the student can quickly understand and subsequently utilise core Scrum concepts. All key processes, roles, artifacts and events are first explained to provide a foundational knowledge and understanding, and then incorporated in an example project that takes the student through all key stages of a Scrum initiative.
Throughout the course, 'real-world' behaviour and practises are highlighted to prepare students for what they might encounter in the business world, and enable them to adapt as required.
Quizzes are included to test your knowledge, and subtitles are available that can be displayed below the screen to avoid obscuring lecture information.
Finally, on successfully finishing the course, you will receive a Certificate of Completion in recognition of your newly-acquired knowledge and skills.