SAFe+General+Overview+v0.1+14-04-2024-Entire+Course+pack.pdf

SCALED AGILE FRAMEWORK

1. SCALED AGILE FRAMEWORK
(SAFe): GENERAL OVERVIEW

2. $
Product
Owner
Dev / Tester
Scrum Master/
Team Coach Story
Feature
1..n
Product
Mgmt
RTE
System Architect
Team Backlog
ART Backlog
Epic
1..n
2-week Iteration
8 -12 week
Planning Interval (PI)
Fits In
Iteration
Fits In
PI
Agile Team
ART
Portfolio
Test
Case
1..n
Lean
Portfolio
Management
Enterprise
Architect
Program
Management
Office
Stakeholders
Portfolio Backlog
Release
1..n
SCALED AGILE FRAMEWORK (SAFe): OVERVIEW

3. 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

4. SAFE COREVALUES
1.Alignment
2.Transparency
3.Respect for People
4.Relentless Improvement

5. 5
THE AGILETEAM IN SAFE
AGILETEAM
AgileTeam...
…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
…Uses SAFe Scrum orSAFe TeamKanban for Team Agility
…consists of 2 specialty roles (one Scrum Master, one Product
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.
PRODUCT OWNER
(1 PERSON)
SCRUM MASTER
/TEAM COACH
(1 PERSON)
DEVELOPERS
(N PEOPLE)

6. USE OF SCRUM FRAMEWORK AT AGILE TEAM LEVEL
6
Iterationreview
Developer
Iterationplanning
Team
Sync
Team
Backlog
Iteration
backlog
(Iteration
goal)
Release
Increment (DoD)
Increments
Iteration
Retrospective
Iteration
backlog
(Iteration
goal)
Stories
from PI
Planning
Product Owner
Scrum
Master/Team
Coach

7. 7
Navigating Scaled Agile
Framework(SAFe ) Big Picture

8. Scaled Agile Framework(SAFe ) Big Picture
End of this Section

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

10. Product’s Owner Responsibilities in (Scaled Agile Framework) SAFe
10TEAM BACKLOG
AGILE TEAM
Product Owner
CUSTOMERFEEDBACK
VISION & ROADMAP

11. Product’s Owner Responsibilities in (Scaled Agile Framework) SAFe
End of this Section

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

13. Product Management’s Responsibilities in (Scaled Agile Framework) SAFe
13
Product
Management CUSTOMER
VALUE
VISION, STRATEGY
& ROADMAP
ART BACKLOG
MARKETS &
USERS

14. Product Management’s Responsibilities in (Scaled Agile
Framework) SAFe
End of this Section

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

16. Agile Team in (Scaled Agile Framework) SAFe
16
AGILETEAM
PRODUCT OWNER
(1 PERSON)
SCRUM MASTER
/TEAM COACH
(1 PERSON)
DEVELOPERS
(N PEOPLE)

17. Agile Team’s Responsibilities in (Scaled Agile Framework) SAFe
17
Agile
Team
CUSTOMER
VALUE
PLAN
FEEDBACK
IMPROVE

18. Agile Team in (Scaled Agile Framework) SAFe & its Responsibilities
End of this Section

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

20. Scrum Master/ Team Coach Responsibilities in (Scaled Agile Framework) SAFe
20
Scrum Master/
Team Coach
PI PLANNINGART
PERFORMANCE
ITERATION
EXECUTION
BacklogTo DoIn ProgressDone
FLOW
TEAM

21. Scrum Master / Team Coach’s Responsibilities in (Scaled Agile Framework) SAFe
End of this Section

22. 22
SAFe Requirements

23. SAFe Requirements
Epic: An Epic is a high-level work body for a
significant Solution development initiative.
Feature: A Feature is a service satisfying a
stakeholder need and can be delivered within a
single Program Increment (PI).
Story: A Story or User Story is an end-user
perspective description a small piece of desired
functionality, focusing on user needs.
Enabler: Enablers are activities supporting
extension of the Architectural Runway,
deployment pipeline implementation, and other
exploratory or infrastructure work.
Story
Enabler
1..n
Team Backlog
ART Backlog
Epic
1..n
Portfolio Backlog
Story
Story
Feature
Feature
Feature
Enabler
Enabler
1..n
Enabler
1..n
Enabler
Enabler

24. SAFe Requirements
End of this Section

25. 25
Thanks
https://www.linkedin.com/in/vipesh-singla/
[email protected]
https://www.youtube.com/@AgileEnterpriseCoach