
Explore how agile scrum practices transform software project management by prioritizing people over processes, embracing change, and delivering fast value, contrasted with the waterfall model and its limitations.
explore the waterfall model as a linear, sequential project approach and compare it with agile, highlighting why customer-focused solutions emerged from a shift away from system-centric practices.
Define scope with stakeholders, gather requirements, plan the system, design architecture, implement and test units, integrate, verify, and deploy the product through the waterfall methodology.
The waterfall approach delays value delivery by reworking requirements and planning for changes, causing budget overruns and extended timelines in software projects.
embrace agile methods for software development through self-organizing cross-functional teams and customers, guiding adaptive planning, early delivery, and continual improvement in response to change.
Explore the phases of agile project management, from envisioning the project vision with what, who, and how, to speculate, explore, adapt, and finally close through value-driven iterations.
Examine Scrum and Kanban frameworks, contrasting sprint-based delivery with velocity against continuous delivery with lead time and cycle time, and key roles.
Learn how agile teams break scope into epics and user stories with story numbers, size and estimate work, plan backlogs and sprints, and deliver features via releases.
Define agile scope of work and explore how it evolves with learning and feedback to deliver three tech events in San Francisco, Miami, and New York, to accommodate 200,000 people.
Explore what epics are in agile scrum, how to break work into user stories, and define the problem statement, personas, and goals from the requester and performer perspectives.
Understand user stories as the smallest unit of work in agile, written from the end user or customer perspective to articulate a persona, an activity, and a result.
Agile teams use planning poker with Fibonacci numbers and t-shirt sizing to estimate user stories, align on effort, commit to sprint work, and forecast delivery.
Learn how the product backlog prioritizes user stories for early delivery and how backlog refinement, using Kanban or Scrum, keeps it properly prioritized with new stories, estimates, and splits.
Understand sprints as the heartbeat of scrum: fixed one-month-or-less timeboxes with planning, scrum, review, and retrospective, where work and backlog refinement occur and changes must not endanger the sprint goal.
Explore the sprint ceremonies that guide agile teams: sprint planning, daily standup, sprint review, and sprint retrospective, detailing planning, daily updates, stakeholder review, and continuous improvement.
Plan the sprint during sprint planning by using the product backlog as input to decide who will work and what will be completed, producing a sprint backlog and sprint goal.
Understand the scrum team, with an agile maker team, a product owner guiding scope and goals, and a scrum master guarding process and timelines to ensure on-time, high-quality delivery.
The daily standup is a 15-minute scrum where each member shares what they did in the last 24 hours, what they will do next, and blockers.
Conduct an informal, time-boxed sprint review where the team, Scrum Master, product owner, and stakeholders demo completed work, compare outcomes to sprint commitments, and update the backlog for next sprint.
Product owner welcomes stakeholders, presents the agenda, and the team shares sprint goals and done features while collecting feedback and prioritizing the backlog for upcoming sprints.
Lead the scrum team through a constructive sprint retrospective after the sprint review to reflect on what went well, what to improve, and how to implement changes.
Track agile progress using burn down and burn up charts to visualize remaining and completed work, with story points and sprints guiding the process.
Explore a practical Scrum workbook that guides you to define project scope, write epics and user stories, assign story and value points, and plan sprints for backlog management.
Learn to use a Scrum workbook to write epics and user stories, estimate with planning poker, map backlogs, and build burn down and burn up charts for sprint planning.
Learn to manage agile iterations with daily standups, sprint reviews, and retrospectives, tracking stories through to do, in progress, review, and done while capturing actions and feedback.
Learn seven agile rules—acceptance, compassion, awareness, journey, energy, reality, and practice—to master mindful leadership, reduce ego-driven decisions, and stand out as an effective Scrum master.
Become an effective Scrum Master, a true Servant-Leader in the Agile world.
When I went for my Scrum certification, I was very upset to see the standards that are set out there. I learned that getting a Scrum certificate is as simple as spending a few bucks without even preparing for or giving the exam. Such people out there are calling themselves true agilest.
I have made this easy-to-understand Agile Scrum course that will help learn the real values of Agile and the practices that comes with it.
What's unique about this course:
- It is animated to keep it interactive and engaging.
- It is short and easy to understand, so you don't get bored along the way.
- It starts from the basics of project management to get them right first.
- It covers all major aspects with examples (Waterfall, Agile, Scrum).
- It deep dives into every single Scrum ceremony for better understanding.
- It has a free workbook that will help you practice all the Scrum ceremonies without worrying about templates.
- The special video in the end is a life changer if you carefully understand and apply the techniques.
Who is this course for?
- This course is for people who are either exploring the IT Project Management role or are already in it and want to advance in their career.
- This course is also good for people who are in leadership roles and has a team to manage
Looking forward to seeing you in the course :)