Scrum Master Tutorial | Google Project Management Certificate

Google Career Certificates
Google Career Certificates
27,584
0
Published 2021-06-14
Dive deep into the setup and day-to-day execution of a Scrum team. We will go beyond what is provided in the official Scrum Guide, and share the most popular tools, methods, tips and tricks for working with a Scrum team.

0:00 Introduction
0:24 Building a Product Backlog
5:36 Writing User Stories
11:01 Backlog Refinement and Effort Estimation
18:20 Introduction to the Sprint
21:18 Sprint Planning
25:12 The Daily Scrum and Sprint Review
30:11 The Sprint Retrospective
32:45 Velocity and Burndown Charts
38:23 Utilizing Kanban Boards
41:42 Tools for Transparency and Collaboration

This video is part of the Google Project Management Certificate, which introduces learners to project management fundamentals including various approaches, tools, and templates, goal-setting, risk management, team dynamics, and data-driven decision-making.

The program, created by Google employees in the field, is designed to provide you with job-ready skills in about 6 months to start or advance your career in Project Management.

Take the Certificate HERE: goo.gle/3R3IpIH

Subscribe HERE: bit.ly/SubscribeGCC

#GrowWithGoogle #GoogleCareerCertificate #ProjectManagementD

Why earn a Google Career Certificate?
► No experience necessary: Learn job-ready skills, with no college degree required.
► Learn at your own pace: Complete the 100% online courses on your own terms.
► Stand out to employers: Make your resume competitive with a credential from Google.
► A path to in-demand jobs: Connect with top employers who are currently hiring.
All Comments (10)
  • @phoenixg4694
    So succinct, practical and perfect in it's level of detail and explanation. Thank you, Sue.
  • @Hello2024Hi
    Why I don’t see any scrum master openings at Google 😁
  • @JM_Hansei
    Seems to me that Scrum teams waste a lot of time on the estimation phase of a project. Why can't the Agile and Scrum evangelist invent a better way (agile) to calculate estimations? Why can't you just assign those singular values of Hard, Medium or Low for a User Story? Also, to mee seems too monotonous and so exhausting gather daily in those standups questioning the same over and over again. If I know what I'm doing now, what did I did yesterday, and what issues do I have, why does the other person in the team needs to hear it? Another source of time wasting those daily-standups meetings. I'm still not very convinced about using all of this so hyped Scrum-Agile way of working.