Scrum Framework

Master the heart of Scrum through comprehensive understanding of its framework components. This module provides in-depth coverage of Scrum roles, events, and artifacts - the essential elements that make Scrum work effectively.

The Framework Foundation

The Scrum framework is deliberately lightweight and simple, yet powerful when properly understood and applied. It consists of:

3 Roles (Scrum Team members)
5 Events (including the Sprint itself)
3 Artifacts (with their commitments)

Each element serves a specific purpose in enabling empirical process control and delivering value.

Module Components

👥 Scrum Roles

The people who bring Scrum to life

Deep dive into the three accountabilities within a Scrum Team:

Product Owner - The Value Maximizer:

Single person accountable for maximizing product value
Product Backlog management and prioritization
Stakeholder collaboration and vision communication
Decision-making authority and techniques
Common anti-patterns and how to avoid them
Balancing competing demands effectively
Success metrics and value measurement

Scrum Master - The Servant Leader:

Accountable for Scrum Team effectiveness
Coaching team members and organization
Facilitating Scrum events as needed
Removing impediments vs enabling self-management
Different stances (teacher, coach, mentor, facilitator)
Working with other Scrum Masters
Organizational change agent responsibilities

Developers - The Creators:

All team members creating the product
Cross-functional and self-managing
Quality ownership through Definition of Done
Sprint Backlog management autonomy
Technical practices integration
Collaboration over specialization
Commitment to Sprint Goal

Team Dynamics:

Optimal team size (10 or fewer)
No sub-teams or hierarchies
Collective accountability
Self-management vs self-organization
Trust and psychological safety

📋 Scrum Artifacts

Transparency through key work items

Master the three artifacts and their commitments:

Product Backlog - The Single Source:

Emergent, ordered list of product improvements
Product Owner accountability
Refinement practices and techniques
Commitment: Product Goal
- Long-term objective for Scrum Team
- Future state of the product
- Planning target and focus mechanism

Sprint Backlog - The Plan:

Sprint Goal + selected Product Backlog items + delivery plan
Developers' ownership and real-time updates
Visible representation of work
Commitment: Sprint Goal
- Single objective for the Sprint
- Creates coherence and focus
- Flexibility in implementation

Increment - The Value Delivery:

Concrete stepping stone toward Product Goal
Sum of all completed Product Backlog items
Must meet Definition of Done
Commitment: Definition of Done
- Shared understanding of work completion
- Quality standards enforcement
- Transparency creator

Artifact Transparency:

Inspection enables adaptation
Low transparency leads to poor decisions
Scrum Master helps maximize transparency
Regular validation with stakeholders

📅 Scrum Events

Formal opportunities for inspection and adaptation

Comprehensive coverage of all Scrum events:

The Sprint - The Container:

Fixed-length events of one month or less
Consistency and predictability benefits
No changes endangering Sprint Goal
Quality standards remain constant
Sprint cancellation authority (Product Owner only)

Sprint Planning - The Beginning:

Maximum 8 hours for one-month Sprint
Three topics addressed:
1. Why is this Sprint valuable?
2. What can be Done this Sprint?
3. How will the chosen work get done?
Whole Scrum Team collaboration
Results in Sprint Goal and Sprint Backlog

Daily Scrum - The Sync: