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 principle describes how time is considered a limiting constraint in Scrum and used to help effectively manage project planning and execution. Time-boxed elements in Scrum include Sprints, Daily Standup Meetings, Sprint Planning Meetings, Sprint Review Meetings, and Retrospect Sprint Meetings.
- 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.
- Scrum vs. Traditional Project Management: This section highlights the key differences between the Scrum principles and traditional project management (Waterfall model) principles and explains how Scrum works better in today’s fast-changing world.
-
Aspects:
This section describes the five aspects that are important considerations for all Scrum projects.
- Organization: This aspect focuses on various facets of a Scrum project organization as well as core and non-core roles and how to form high performance Scrum Teams.
- 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: This aspect focuses on defining quality as it relates to projects and to present the Scrum approach to achieve the required levels of quality.
- Change: This aspect focuses on the importance of change in any project, regardless of its method or framework and expands on how Scrum development processes are designed to embrace change.
- Risk: This aspect focuses on management of risks in a Scrum environment by considering various tools that facilitate the management of risks.
-
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:
- Initiate Phase: This phase includes the processes related to initiation of a project: Create Project Vision, Identify Scrum Master and Stakeholder(s), Form Scrum Team, Develop Epic(s), Create Prioritized Product Backlog, and Conduct Release Planning.
- Plan & Estimate: This session deals with the processes related to planning and estimating tasks such as Create User Stories; Approve, Estimate, and Commit User Stories; Create Tasks; Estimate Tasks; and Create Sprint Backlog.
- 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.
|