SFC - Scrum Fundamentals
Scrum Processes
Release
Overview
Why Use Scrum?
Key benefits
Scrum is
Scrum Aspects
Organization
defined roles and responsibilities
in a Scrum project
Non-core Roles
not mandatorily
Core Roles
mandatorily required for producing
Scrum Principles
Iterative Development
Business Justification
Value-driven Delivery
Scrum core team
members include
Impacted By
Scrum Master
Implement
designed to deliver significant value quickly
and throughout a project
Empirical Process Control
Product Owner
Conduct Daily Standup
Change
designed to embrace change
Quality
Acceptance Criteria
continuous improvement with repetitive testing optimizes the probability of achieving the expected quality levels in a Scrum project
Stakeholder(s)
Iterative
For large scale Scrum
Collaboration
is for the stakeholders that the project produces
the collaborative benefits
Approach of continuous improvement whereby the team learns from experience and stakeholder engagement to constantly keep the Prioritized Product Backlog updated with any changes in requirements
Awareness
Plan and Estimate
Scrum Team
Sprint generally lasts between one and six weeks
and involves the Scrum Team working
Risk
uncertain event
Continuous Improvement
Early Delivery of High Value
Groom Prioritized Product Backlog
Estimate Users Stories
Produc Owner
Initiate
Time-boxing
Create Sprint Backlog
Retrospect Project
Scrum Guidance Body (SGB)
Divison of the SBOK
Effective
Form Scrum Team
Sprints
Identify Scrum Master and Stakeholders
Apects
Vendors
Large projects may have multiple Scrum Teams working in parallel making it necessary to synchronize and facilitate the flow of information and enhance communication
High Trust Eviroment
Risks that are likely to have a positive impact on the project are referred to as opportunities, whereas threats are risks that could affect the project in a negative manner
Commit User Stories
cross-functional, self-organized, and empowered teams who dividetheir work into short, concentrated work cycles called Sprints
Efficient Develpment Process
Scrum for the enterprise
Maintaining business justification for the project.
Coordinate program or portfolio components
Product Owner is primarily responsible
for business justification
set of documents and/or a group of experts who are typically involved with defining objectives related to quality, government regulations, security, and other key organizational parameters
Value-based Prioritization
Cost
Guides, facilitates, and teaches Scrum practices
Develop Epic(s)
Scrum Master
deliver maximum business value,
from early in the project and continuing throughout
Fast
Scrum for large projects
Collective Ownership
Faster Problem Resolution
Applicable
7 describe the five aspects that are important
considerations for all Scrum projects
The Voice of the Customer
Conduct and coordinate sprints
Create and groom program or portfolio backlog
Ship Deliverables
Principles
Articulation
Create Project Vision
delineates the Product Owner’s and organization’s responsibilities related to iterative development
Sprint Reviw Meetings
Sustainable Pace
Ensures that Scrum processes are being followed
expand on the six principles which form the foundation on which
Scrum is based
Review and Retrospect
Responsible for articulating customer requirements
Motivation
Scope
Conduct Release Planning
Create large projects component
Sprint Planning Meetings
Portfolios, programs, and/or projects in any industry
Projects of any size or complexity
Review and update scrum guidance body
Inspection
change by using short, iterative Sprints that incorporate customer feedback on each Sprint’s deliverables
Adaptability
Products, services, or any other results to be delivered to stakeholders
Create program or portfolio components
Processes
Self-Organization
Create Deliverables
Quality
stakeholders change their mind about what they want and need throughout a project (sometimes referred
to as “requirements churn")
customers, users, and sponsors
Customer Centric
Facilitator who ensures that the Scrum Team
Prepare large projects release
external individuals or organizations, provide products and/or services that are not within the core competencies of the project organization.
Transparency
Create User Stories
Retrospect Sprint
Appropriation
Scrum attempts to start delivering results
as early in the project as possible.
High Velocity
Effective Deriverables
Continuous Delivery of Value
Create Prioritized Product Backlogs
Flexible
Responsible for achieving maximum business value
Any changes to the requirements reflect changes in
the internal and external business environment and allow the team to continually work and adapt
Resources
Organizational Capabilities
Demonstrate and Validate Sprint
Clears impediments for the team
Continuous Feedback
Transparency
Daily Standup Meetings
influence the project throughout the
project’s development
Adaptative
Innovative Environment
Estimate Tasks
Identify Tasks
nineteen fundamental Scrum processes
and their associated inputs, tools, and outputs
Time
Defined by the Project Vision Statement
Adaptation
important quality-related tasks (e.g., development, testing, and documentation) are completed as part of the same Sprint by the same team
Retrispect program or portfolio releases