Login Get started

🔥Certified Scrum Master Full Course | Scrum Master Training | Scrum Master Course | Simplilearn

Simplilearn・154 minutes read

The Simply Learn Scrum Master full course video covers key concepts of scrum, emphasizing the need for agile methodologies and the advantages of Scrum for project efficiency and collaboration. Scrum involves self-organizing teams, daily scrums, and iterative development to deliver project value efficiently and effectively.

Insights

Scrum emphasizes agile methodologies for quick adaptability, iterative development, and efficient project deliverables through self-organizing teams.
Agile methodologies like Scrum offer benefits such as predefined schedules, predictable costs, enhanced client visibility, and early project value realization.
Scrum's history dates back to the 1980s, and its framework enables collaborative, self-organizing teams to deliver project outcomes efficiently.
Scrum involves key artifacts like the product backlog, Sprint backlog, and product increment, enhancing transparency and work understanding.
Scrum ceremonies like Sprint planning, daily scrums, Sprint reviews, and retrospectives ensure continuous improvement, value delivery, and effective team collaboration.

Get key ideas from YouTube videos. It’s free

Recent questions

What are the key concepts of Scrum?
Scrum involves iterative development, self-organizing teams, and collaboration.

Related videos

Summary

00:00

"Scrum Master Course: Agile Methodologies Explained"

Scrum Master full course video by Simply Learn covers key concepts related to scrum, including its definition, components, process, and methodology.
The tutorial emphasizes the need for agile methodologies due to the limitations of traditional waterfall models in accommodating changes quickly.
Agile methodologies, like Scrum, focus on iterative development, involving self-organizing cross-functional teams collaborating to create working software pieces.
Advantages of agile methodologies include predefined schedules, predictable costs, client visibility, greater interaction between project teams, and early project value realization.
Scrum specifically allows for efficient project deliverables, time and money utilization, and division of projects into smaller units called Sprints for fast-moving projects.
Scrum meetings, like daily scrums, provide teams with visibility, feedback from clients, and the ability to make changes based on feedback easily.
Scrum's history dates back to the 1980s, with the term introduced by management experts and further developed by Jeff Sutherland and Ken Schwaber in 1995.
The Agile Alliance was founded in 2001, leading to the publication of the Agile Software Development with Scrum in 2001 and the establishment of the Scrum Alliance in 2002.
Scrum.org was created in 2009, offering Scrum certifications, and the first Scrum Guide was published in 2010, leading to increased adoption of Scrum methodologies.
Scrum is a framework enabling teams to collaborate, self-organize, work on problems, reflect on victories and losses, and provide project deliverables efficiently in time and money.

17:17

"Scrum Framework: Team Collaboration for Value Delivery"

Each team member possesses unique skills and capabilities, with cross-skilling encouraged for collective ownership and feature delivery.
The Scrum team comprises the product owner, Scrum master, and team members, each with distinct roles and objectives that cannot be merged.
The product owner focuses on maximizing ROI by determining, prioritizing, and refining product features in collaboration with the business.
The Scrum master aids teams in applying Scrum, removing impediments, and fostering agile practices adoption.
The Scrum team, a self-organizing group, collaborates to fulfill stakeholder requirements and deliver value.
Scrum includes three key artifacts: the product backlog, Sprint backlog, and product increment, enhancing transparency and work understanding.
The product backlog lists tasks for achieving stakeholder goals, with constant reprioritization and addition of new items.
Sprint backlogs, subsets of the product backlog, contain tasks for specific time-boxed iterations to achieve Sprint goals.
Product increments combine completed tasks from Sprints, ensuring each increment complements previous work and aligns with project vision.
The Scrum framework involves product backlog creation, Sprint planning, team collaboration, daily scrums, Sprint reviews, retrospectives, and product increments delivery, ensuring continuous improvement and value delivery.

33:41

Effective Scrum Board for Task Completion

Daily scrum involves action items to keep the team focused on task completion and priorities.
The scrum board is a visual tool accessible to all team members, divided into slots like to do, in progress, and done.
New sprints start with a reset of the existing board and creation of a new scrum board.
Visual systems like the scrum board are effective, drawing inspiration from Kanban for task completion.
Themes, epics, and user stories are grouped together for planning purposes, with epics being large user stories.
User stories are functions or features desired by the product owner, turning into working software providing value to the customer.
Tasks are disaggregated from user stories during the Sprint planning meeting, estimated in ideal time.
Use cases exemplify user stories, detailing what the user wants and how the system should support it.
User stories can use a fictitious user or persona to understand the user's needs and goals.
User story cards contain a brief description of the user story, following the format "As a user, I want this feature so that I can."

53:32

"User Stories: Estimation, Prioritization, Implementation, Velocity, Planning"

User stories typically include a title, unique identifier, description, and acceptance criteria.
Estimation of size can be in ideal days or story points, with story points being more common.
Value points are assigned by the product owner to prioritize user stories.
User stories may indicate their origin (customer, technical domain) and level of uncertainty (X Factor).
User stories are turned into working software, requiring effort to figure out how to implement them.
User story cards in software packages like Trello or Jira can contain more information and dynamic links.
Large user stories may need to be subdivided into smaller ones for completion within a Sprint.
Subdividing user stories can be based on operational boundaries, exceptions, or data boundaries.
Velocity is the team's capacity to complete work in a Sprint, observed from past performance.
Release planning involves establishing goals, estimating target stories, assigning stories to Sprints, and meeting conditions of satisfaction.

01:14:38

"Scrum Estimation and Planning Techniques Explained"

Sprint two builds on the progress made in Sprints one and two to facilitate the release of Sprint three.
Rolling wave planning involves detailed planning for the near term and high-level planning for the future.
Deciding as late as possible is encouraged to ensure more information is available for planning later releases.
The cone of uncertainty highlights the evolution of estimates from initial guesses to more accurate figures.
The product owner's belief in the team's capabilities influences estimation accuracy.
Scrum estimation exposes inaccurate estimates early, leading to adjustments and improvements.
Velocity tracking in Scrum showcases the team's learning curve and performance improvement over time.
Ideal time for user stories is based on uninterrupted work time, while elapsed time accounts for distractions.
Story points in Scrum measure relative size and effort of tasks, aiding in estimation and comparison.
Planning poker is a collaborative and efficient estimation technique that engages the entire team and ensures consensus on estimates.

01:34:22

Effective Memorization Strategy for Successful Scrum Teams

Memorization strategy is crucial, with the mnemonic "C-S-O-R-C" representing commitment, focus, openness, respect, and courage.
Commitment entails delivering value to customers with team buy-in and focus on important tasks.
Focus involves concentrating on a few key tasks at a time through time boxing.
Openness, akin to transparency, involves sharing project information openly.
Respect encompasses self-respect, respect for others, concepts, and stakeholders.
Courage is necessary for making commitments, handling uncertainty, sharing disagreements, and technical debates.
The Scrum life cycle includes grooming and pruning the product backlog, Sprint planning meetings, daily scrums, Sprint reviews, and retrospectives.
Sprint planning meetings involve selecting user stories, disaggregating tasks, and estimating work.
Daily scrums are brief meetings for team updates on tasks, impediments, and plans.
Sprint reviews showcase software, gather feedback, and allow the product owner to accept or reject work.

01:54:46

"Scrum Team Dynamics and Roles Explained"

User stories are written by the product owner and developed by team members based on a product backlog.
The product backlog is a prioritized list of user stories owned by the product owner.
Technical considerations may lead to user stories being added or removed from the product backlog.
The definition of done is a checklist agreement between the product owner and the team, usually prepared by the scrum master.
The product owner defines the project vision, requirements, and priorities, resisting the urge to manage the team during a sprint.
The development team, comprising 5 to 9 members, self-organizes to meet the product owner's goals.
The scrum master is a servant leader who facilitates scrum ceremonies, removes obstacles, and coaches the team.
Scrum masters exhibit responsibility, humility, collaboration, commitment, influence, and knowledge.
Scrum masters resolve issues hindering team progress, protect the team, and coach the team through agile principles.
Scrum teams should be small, self-sufficient, cross-functional, and ideally comprised of generalizing specialists.

02:14:20

"Scrum: Agile Methodology for Project Success"

Scrum involves Sprint backlogs that may become invalid due to changes in priorities or mid-course corrections, with Sprint cancellations being rare.
A Sprint starts with a planning meeting and ends with a review and retrospective, utilizing three backlogs: product, release, and Sprint.
The product backlog contains all user stories for the project, continuously pruned for maximum customer value, including technical and non-functional stories.
Scrum ceremonies include Sprint planning, daily scrum, Sprint review, and Sprint retrospective, each with specific time constraints and attendee requirements.
The Sprint planning meeting, crucial for team capacity and defining goals, is time-boxed based on Sprint duration and involves selecting user stories based on team velocity or commitment.
The daily scrum, a 15-minute meeting for all team members, focuses on individual updates on tasks, impediments, and coordination of work.
The Sprint review, time-boxed based on Sprint duration, aims to demonstrate working software, obtain feedback, and assess acceptance or rejection.
The Sprint retrospective, time-boxed for reflection and improvement, involves the team answering key questions and using problem detection techniques for continuous enhancement.
The definition of done, crucial for reporting and value delivery, varies for features, Sprints, and releases, serving as a checklist created by the Scrum Master in consultation with the team.
A practical example of a Scrum meeting for a new project, WeatherMaster, showcases the daily stand-up format, including updates, impediments, and team coordination facilitated by the Scrum Master.

02:33:50

"Kanban: Efficient Workflow Management with Transparency"

Kanban utilizes a kanban board to identify and resolve bottlenecks cost-effectively and efficiently.
Transparency is crucial in Kanban, with all task-related information displayed on the board for team awareness.
Work in Kanban is divided into smaller, manageable pieces to limit work in progress.
The Kanban board consists of three main components: the to-do list, ongoing column, and completed column.
Software versions of the Kanban board, like Trello, replace physical boards with digital cards for tracking progress.
Kanban and Scrum share lean and agile principles, focusing on reducing waste and incremental product delivery.
Both frameworks aim to limit work in progress, enhance visibility of blockers, and use pull scheduling.
Scrum divides projects into time-constrained iterations, while Kanban follows an event-driven approach for continuous delivery.
Scrum restricts changes during a Sprint, while Kanban allows changes at any time within the workflow.
Scrum measures progress using velocity, while Kanban focuses on lead time for task completion.

02:52:22

"Scrum methodology: sprint, backlog, collaboration, efficiency"

In a Sprint, tasks are identified from the product backlog to achieve a goal and added to the Sprint backlog.
The product increment is a combination of completed product backlog tasks and previous increments' value, ensuring usability.
Product backlog lists items for product development, while Sprint backlog lists tasks for each Sprint, taken from the product backlog.
Product backlog is customer-driven, while Sprint backlog is team-driven, with specific goals for each Sprint.
Scrum Master promotes Scrum adoption, facilitates team understanding, and ensures adherence to Scrum values and practices.
Daily stand-up sessions last 15 minutes, discussing completed tasks, pending tasks, obstacles, and addressing any unaccomplished tasks.
Scrum ban combines Scrum and Kanban methodologies to minimize work batching and adopt a pull-based system for efficient work completion.
Sprint 0 involves minimal effort to create a project vision and product backlog skeleton, aiding in estimating product releases.
Scrum of scrums facilitates collaboration between multiple Scrum teams for complex projects, ensuring transparency and scalability.
User story mapping arranges user stories based on priority and sophistication levels, aiding in understanding system functionalities and planning releases.

03:10:17

"Essential User Stories in Mobile App Development"

User stories are essential in mobile app development for banks, focusing on what users need and how it brings value.
User stories are brief explanations of business requirements from an end user perspective, forming the basis for agile frameworks like epics and initiatives.
Epics are collections of related user stories, while tasks are used to track work and break down user stories further.
Sprints in Scrum are time-boxed iterations for creating specific modular features within a week or two.
Velocity in Scrum measures the amount of work completed by a team in a Sprint, indicating the speed of progress.
Product owners define project vision, anticipate customer needs, and evaluate progress based on backlog for all product-related questions.
Burn up charts track completed work, while burn down charts show pending deliverables, aiding in understanding team progress.
Estimation in Scrum is based on the difficulty of user stories, using scales like numeric sizing or Fibonacci series.
Risks in Scrum include budget, people, Sprint, product knowledge, and capability risks, requiring continuous assessment and response planning.
Popular tools in Scrum include Jira, Trello, and VersionOne, but selection should align with project requirements and methodologies.

03:27:52

"Scrum Meetings Frequency and Roles Defined"

Frequency of meetings in Scrum must be predefined
Generalist Scrum Master represents the Scrum team in meetings
Chief Scrum Master coordinates and collaborates among all Scrum teams
End of Scrum full course video by Simply Learn
Subscribe to Simply Learn YouTube channel for more videos

Try it yourself — It’s free.