SCALED AGILE FRAMEWORK

(SAFe): GENERAL OVERVIEW

SCALED AGILE FRAMEWORK (SAFe): OVERVIEW

Portfolio Backlog
Portfolio
Epic
Program
Lean
Portfolio Management $
Management Office
Enterprise
Architect
Stakeholders

1..n

ART Backlog
8 -12 week
Planning Interval (PI)
Release
ART

Fits In
Feature 1..n
Product RTE
PI
Mgmt

System Architect

2-week Iteration 1..n

Team Backlog
Agile Team

Product Scrum Master/

1..n
Owner Team Coach Fits In Story
Iteration
Test
Dev / Tester Case
SAFe Lean- Agile Principles
1. Take an economic view
2. Apply systems thinking
3. Assume variability; preserve options
4. Build incrementally with fast, integrated learning cycles
5. Base milestones on objective evaluation of working systems
6. Make value flow without interruptions
7. Apply cadence, synchronize with cross-domain planning
8. Unlock the intrinsic motivation of knowledge workers
9. Decentralize decision-making
10. Organize around value
SAFE CORE VALUES

1. Alignment
2. Transparency
3. Respect for People
4. Relentless Improvement
THE AGILE TEAM IN SAFE
AGILE TEAM
Agile Team...
… Functions as the basic building block of the SAFe Enterprise
… A cross-functional, self-organizing team of 5 to 10 people that
defines, builds, tests, and delivers Solution functionality
SCRUM MASTER
… Uses SAFe Scrum or SAFe Team Kanban for Team Agility PRODUCT OWNER DEVELOPERS /TEAM COACH
… consists of 2 specialty roles (one Scrum Master, one Product (1 PERSON) (N PEOPLE) (1 PERSON)
Owner), and Developers
… Product Owner defines Stories along with other team
members and prioritizes the Team Backlog
… Scrum Master / Team Coach: Is a servant leader and coach for
the team. This role instills the agreed-to Agile process, removes
impediments to progress
… accountable for creating a valuable, useful Increment every
Iteration
… no sub-teams or hierarchies
… cross-functional : the members have all the skills necessary to
create value each Iteration
… self-managing : they internally decide who does what, when,
and how.
… small enough to stay nimble and big enough to
complete significant work within a Iteration.
5
USE OF SCRUM FRAMEWORK AT AGILE TEAM LEVEL

Team
Sync

Stories Release

Increment (DoD)
from PI Scrum

Increments
Planning Master/Team
Coach Developer

Iteration planning
Iteration review

Iteration
Iteration
backlog
Product Owner backlog
(Iteration
(Iteration
goal)
Team Iteration
goal)
Backlog Retrospective

6
Navigating Scaled Agile
Framework(SAFe ) Big Picture

7
Scaled Agile Framework(SAFe ) Big Picture

End of this Section

Product’s Owner Responsibilities in
(Scaled Agile Framework) SAFe

9
Product’s Owner Responsibilities in (Scaled Agile Framework) SAFe

FEEDBACK CUSTOMER

Product Owner
VISION & ROADMAP
AGILE TEAM

TEAM BACKLOG 10
Product’s Owner Responsibilities in (Scaled Agile Framework) SAFe

End of this Section

Product Management’s Responsibilities
in (Scaled Agile Framework) SAFe

12
Product Management’s Responsibilities in (Scaled Agile Framework) SAFe

MARKETS &
VALUE USERS

Product
Management CUSTOMER
ART BACKLOG

VISION, STRATEGY
& ROADMAP
13
Product Management’s Responsibilities in (Scaled Agile
Framework) SAFe

End of this Section

Agile Team in (Scaled Agile Framework)
SAFe & its Responsibilities

15
Agile Team in (Scaled Agile Framework) SAFe

AGILE TEAM

SCRUM MASTER
PRODUCT OWNER DEVELOPERS /TEAM COACH
(1 PERSON) (N PEOPLE) (1 PERSON)

16
Agile Team’s Responsibilities in (Scaled Agile Framework) SAFe

CUSTOMER
IMPROVE

Agile
Team PLAN

FEEDBACK

VALUE

17
Agile Team in (Scaled Agile Framework) SAFe & its Responsibilities

End of this Section

Scrum Master / Team Coach’s Responsibilities
in (Scaled Agile Framework) SAFe

19
Scrum Master/ Team Coach Responsibilities in (Scaled Agile Framework) SAFe

ART PI PLANNING
PERFORMANCE

Scrum Master/
ITERATION
Team Coach
TEAM EXECUTION

Backlog To Do In Progress Done

FLOW 20
Scrum Master / Team Coach’s Responsibilities in (Scaled Agile Framework) SAFe

End of this Section

SAFe Requirements

22
SAFe Requirements
Epic Enabler
Epic: An Epic is a high-level work body for a
significant Solution development initiative.

Portfolio Backlog
Feature: A Feature is a service satisfying a
stakeholder need and can be delivered within a 1..n
single Program Increment (PI). Feature
1..n

Feature

Feature
Story: A Story or User Story is an end-user Enabler
Enabler
perspective description a small piece of desired ART Backlog Enabler
functionality, focusing on user needs.
1..n
1..n
Story
Enabler
Enabler: Enablers are activities supporting
extension of the Architectural Runway, Story Enabler
deployment pipeline implementation, and other Story
exploratory or infrastructure work.
Team Backlog
SAFe Requirements

End of this Section

Thanks

https://www.youtube.com/@AgileEnterpriseCoach

https://www.linkedin.com/in/vipesh-singla/

singlavipesh@gmail.com

25