Free Instructor-led Virtual Training for SFC™ Certification

Course Overview

Scrum Fundamentals Certified (SFC™) course is tailored to help anyone interested to know more about Scrum; learn about key concepts in Scrum as defined in the SBOK™ Guide; and to get a basic understanding of how Scrum framework works in delivering successful projects.

The purpose of the Scrum Fundamentals Certified exam is to confirm you have basic understanding of the Scrum framework. On passing the exam, you will be accredited as "Scrum Fundamentals Certified".

Sessions

Topics

Introduction to Scrum and SCRUMstudy

(1 hour)

Introduction: This session gives an overview of Scrum which is an adaptive, iterative, and flexible framework designed to deliver significant value quickly and throughout a project. This session also discusses the Scrum framework as defined in the SBOK™ Guide. The Scrum framework is structured in such a way that it supports product and service development in all types of industries and in any type of project, irrespective of its complexity. This session looks into details of a Scrum flow which starts with the creation of a Project Vision and how a Product Owner then develops a Prioritized Product Backlog which contains a prioritized list of User Stories with their respective Acceptance Criteria. The user stories are delivered through iterative product development cycles called Sprints.

SCRUMstudy Scrum Certifications and Training: This session briefly talks about VMEdu/SCRUMstudy and what certifications are offered by SCRUMstudy.

Scrum Fundamentals Certified Certification Training

(4 hours)

Scrum Framework based on the SBOK™ Guide: In this session, we will discuss the purpose of the SBOK Guide™ with its framework.

Purpose of the SBOK™ Guide: The SBOK™ Guide was developed as a means to create a necessary guide for organizations and project management practitioners who want to implement Scrum.

Framework of the SBOK™ Guide: The SBOK™ Guide is broadly divided into the three areas of: Principles, Aspects and Processes.

Principles: This topic discusses the six Scrum principles which are the foundation on which the Scrum framework is based.

Introduction: This topic discusses what principles are and why it is mandatory for every Scrum project to follow Scrum principles.

Roles Guide: This section outlines which section or subsection is most relevant for each of the core Scrum roles of Product Owner, Scrum Master, and Scrum Team.

Empirical Process Control: This section describes the first principle of Scrum, and the three main ideas of transparency, inspection, and adaptation.

Self-organization: This section highlights the second principle of Scrum, which focuses on today’s workers, who deliver significantly greater value when self-organized and this results in better team buy-in and shared ownership; and an innovative and creative environment which is more conducive for growth.

Collaboration: This section emphasizes the third principle of Scrum where product development is a shared value-creation process that needs all stakeholders working and interacting together to deliver the greatest value. It also focuses on the core dimensions of collaborative work: awareness, articulation, and appropriation.

Value-based Prioritization: This section presents the fourth principle of Scrum, which highlights the Scrum framework’s drive to deliver maximum business value in a minimum time span.

Time-boxing: This section explains the fifth principle of Scrum which treats time as a limiting constraint. It also covers the Sprint, Daily Standup Meeting, and the various other Sprint-related meetings such as the Sprint Planning Meeting and Sprint Review Meeting, all of which are Time-boxed.

Iterative Development: This section addresses the sixth principle of Scrum which emphasizes that iterative development helps to better manage changes and build products that satisfy customer needs.

Aspects: This section describes the five aspects that are important considerations for all Scrum projects.

Organization: Understanding defined roles and responsibilities in a Scrum project is very important for ensuring the successful implementation of Scrum. This topic also briefly discusses core roles such as Scrum Master, Product Owner and Scrum Team and non-core roles such as Stakeholders and Vendors.

Business Justification: Business justification in Scrum is based on the concept of Value-driven Delivery. It is important for an organization to perform a proper business assessment prior to starting any project. This helps key decision makers understand the business need for a change or for a new product or service, the justification for moving forward with a project, and its viability.

Quality: In Scrum, quality is defined as the ability of the completed product or deliverables to meet the Acceptance Criteria and achieve the business value expected by the customer. This topic also looks into the differences between Acceptance Criteria and Done Criteria and how these impact the velocity of a Scrum team.

Change: Scrum projects welcome change by using short, iterative Sprints that incorporate customer feedback on each Sprint’s deliverables. This enables the customer to regularly interact with the Scrum Team members, view deliverables as they are ready, and change requirements if needed earlier in the Sprint.

Risk: Managing risk must be done proactively, and it is an iterative process that should begin at project initiation and continue throughout the project’s lifecycle. In a Scrum project, risks are managed through Risk Prioritized Product Backlog.

Phases: Scrum processes address the specific activities and flow of a Scrum project. In total there are nineteen fundamental Scrum processes that apply to all projects. These processes are grouped into five phases. They are:

Implement: This phase is related to the execution of tasks and activities for creating a project's product. The processes covered in this session include creating the various deliverables, conducting Daily Standup Meetings, and grooming (i.e., reviewing, fine-tuning, and regularly updating) the Product Backlog at regular intervals.

Review & Retrospect: The Review and Retrospect phase is concerned with reviewing the deliverables created, and determining ways to improve practices and methods used for project execution.

Release: The Release phase deals with handover of Accepted Deliverables to the customer and identifying, documenting, and internalizing the lessons learned during the project.