Become a Scrum Guru the Easiest Way: Ultimate Scrum Guide
3.1 (29 ratings)
Instead of using a simple lifetime average, Udemy calculates a course's star rating by considering a number of different factors such as the number of ratings, the age of ratings, and the likelihood of fraudulent ratings.
321 students enrolled
Wishlisted Wishlist

Please confirm that you want to add Become a Scrum Guru the Easiest Way: Ultimate Scrum Guide to your Wishlist.

Add to Wishlist

Become a Scrum Guru the Easiest Way: Ultimate Scrum Guide

The best online source for becoming a cert. scrum master & gaining knowledge of a popular agile way to manage projects
3.1 (29 ratings)
Instead of using a simple lifetime average, Udemy calculates a course's star rating by considering a number of different factors such as the number of ratings, the age of ratings, and the likelihood of fraudulent ratings.
321 students enrolled
Created by Fareed Raja
Last updated 11/2015
Current price: $10 Original price: $40 Discount: 75% off
5 hours left at this price!
30-Day Money-Back Guarantee
  • 1 hour on-demand video
  • 3 Articles
  • 5 Supplemental Resources
  • Full lifetime access
  • Access on mobile and TV
  • Certificate of Completion
What Will I Learn?
  • Expand your career opportunities by staying relevant and marketable across all industry sectors adopting Agile practices
  • Demonstrate to employers and peers your attainment of core Scrum knowledge
  • Learn the foundation of Scrum master role from the best minds in Scrum
  • Fill the role of ScrumMaster or Scrum team member
  • Gain an understanding of the Scrum framework, including team roles, activities, and artifacts
View Curriculum
  • Have basic knowledge of the Agile methodology

Scrum is by far the most popular of the Agile frameworks for developing complex products. This course provides a working knowledge of the Scrum framework — the underlying principles, practices, techniques and skills necessary for you to succeed as a Scrum Master. If you are already on a Scrum team you will learn how to become a change agent to help your team achieve a higher level of success.

During the development of this course, my main focus remained on making this learning process easy and fun. I like teaching with a straight-to-the-point/no-fluff approach. This course has a good mix of video lectures, pdf guides, and quizzes in order to help you understand the objectives.

The course is a little over 1.5 hours and will also include resources for you to help out with the certification! I will eventually add practice exam questions as we progress in this class. There are several exercise files included in this course and more resources will be added on a weekly basis. You will go through the following 7 sections:

1. What is Scrum?

2. What are the 3 Scrum Roles?

3. What is the Process?

4. What are the 4 Scrum Ceremonies?

5. What are the 3 Artifacts of Scrum?

6. What are the 5 Values of Scrum?

7. What are the Top Scrum Terms?

By the end of this course you will be able to:

Describe the Scrum framework to others

  • roles and responsibilities
  • use of each artifact
  • purpose of each meeting/ceremony
  • Explain the difference between the Scrum framework and other processes and systems

  • contrast with Waterfall
  • contrast ScrumMaster role with traditional roles
  • contrast the Scrum product backlog with traditional requirements
  • Be a successful Scrum Master for a Scrum team

  • be a change agent leader
  • facilitate each type of Scrum meeting
  • know how to detect and correct potential impediments to Scrum success
  • help a team adopt Scrum or improve their use of Scrum
  • have conversations about process, structures and values
  • use several conflict resolution techniques
  • Help a Scrum team plan successfully

  • plan a release
  • plan a sprint
  • create/maintain a prioritized product backlog
  • Who is the target audience?
    • Anyone who works on or with a Scrum team, or wants to learn what Scrum is all about
    • Executives, Managers, Programmers, Testers, Product Owners, Scrum Masters, Project Managers, Product Managers, Analysts, UI Designers, Architects, etc
    • Anyone responsible for a successful use and/or roll out of Scrum in a project/enterprise
    Students Who Viewed This Course Also Viewed
    Curriculum For This Course
    41 Lectures
    1 Lecture 00:54
    What is Scrum?
    4 Lectures 10:19

    Scrum is a process framework that has been used to manage complex product development since the early 1990s. Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and development practices so that you can improve.

    Preview 01:44

    Understand what is the main goal of the scrum framework. How it helps ask all the important questions.

    Preview 01:29

    Waterfall vs. Agile approach. Know how things were done in the past. This will help you value the scrum process even more.

    Preview 03:43

    Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

    Preview 03:23
    What are the important Scrum roles
    3 Lectures 08:58

    The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:

    • Clearly expressing Product Backlog items;
    • Ordering the items in the Product Backlog to best achieve goals and missions;
    • Optimizing the value of the work the Development Team performs;
    • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
    • Ensuring the Development Team understands items in the Product Backlog to the level needed.
    Product Owner

    The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.

    The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.

    The Scrum Master

    Teams have the following characteristics:

    • They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
    • Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment;
    • Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule;
    • Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule; and,
    • Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
    The Scrum Team
    The 3 Scrum Artifacts
    4 Lectures 07:55

    User stories are composed of three aspects:

    • a written description or short title of the story used as a token for planning and as a reminder to have conversations
    • conversations about the story that serve to flesh out the details of the story
    • acceptance tests that convey and document details and that can be used to determine when a story is complete
    What is a story?

    The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.

    The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal.

    The Spring Backlog

    The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

    A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists.

    The Product Backlog

    A burn down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. That is, it is a run chart of outstanding work. It is useful for predicting when all of the work will be completed.
    The Burndown Chart
    The Scrum Process
    1 Lecture 05:09
    The Scrum Process Explained
    The 4 Scrum Ceremonies
    5 Lectures 08:34
    What are Ceremonies?

    The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.

    Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.

    Sprint Planning answers the following:

    • What can be delivered in the Increment resulting from the upcoming Sprint?
    • How will the work needed to deliver the Increment be achieved?
    First Ceremony: Sprint Planning Meeting

    The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, the Development Team members explain:

    • What did I do yesterday that helped the Development Team meet the Sprint Goal?
    • What will I do today to help the Development Team meet the Sprint Goal?
    • Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
    Second Ceremony: Daily Scrum Meeting

    The Sprint Review includes the following elements:

    • Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
    • The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;
    • The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
    • The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
    • The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to date (if needed);
    • The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
    • Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
    • Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.
    Third Ceremony: Sprint Review Meeting

    The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

    The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches all to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.

    Fourth Ceremony: The Sprint Retrospective
    The 5 Values of Scrum
    5 Lectures 05:17
    First Value: Commitment

    Second Value: Focus

    Third Value: Openness

    Fourth Value: Courage

    Fifth Value: Respect
    Key Scrum Terms
    10 Lectures 09:36
    Terms - B

    Terms - D

    Terms - E

    Terms - F

    Terms - I

    Terms - P

    Terms - R

    Terms - S

    Terms - V

    Scrum Terms (Downloadable PDF)
    4 pages
    1 Lecture 01:40
    What's Next?
    Exercise Files
    4 Lectures 00:00
    Burndown Chart
    1 page

    Velocity Example
    1 page

    Product Backlog
    1 page

    Scrum Process
    1 page
    1 More Section
    About the Instructor
    Fareed Raja
    4.2 Average rating
    209 Reviews
    6,905 Students
    4 Courses
    MBA | Digital Marketer | Author | World Traveler

    An expert in consumer behavior and international relations, I have many years of experience in dealing with different professionals from across the globe; from every day consumers to decision making government officials.

    A passionate project professional, graduated with Bachelor's degree in Marketing from University of South Alabama, and later received MBA degree from one of the oldest Jesuit schools in the States; Spring Hill College.

    I believe that inspiration comes from little things in life and it's up to us to use these inspired moments to create something that makes a difference. I love studying consumer behavior and constantly look for patterns within certain segments.

    I am always up for new business ventures and enjoy sharing knowledge and all kinds of crazy ideas. It's safe to say that in the last 15 years of my professional career, I have learned more from interacting with people from all sorts of backgrounds and professions.