*Introduction to SAFe and Scrum*
SAFe (Scaled Agile Framework) is a framework for scaling Agile principles and methods to large
organizations. It provides a set of organization and workflow patterns intended to guide
enterprises in scaling lean and agile practices beyond small teams. Scrum, on the other hand, is
one of the most widely used Agile methodologies, primarily designed for small teams to deliver
working software in short iterations.
*Key Principles of SAFe:*
1. *Lean-Agile Mindset:* SAFe promotes a culture of continuous learning and improvement,
emphasizing the importance of agility and Lean principles.
2. *Value Delivery:* SAFe focuses on delivering value to the customer, aligning the work of all
teams with the larger business objectives.
3. *Organized Around Value:* SAFe organizes work into value streams and agile release trains
to optimize the flow of value.
4. *Cross-Functional Teams:* SAFe encourages cross-functional teams that include all the skills
necessary to deliver value.
5. *Cadence and Synchronization:* SAFe uses fixed-length iterations, time-boxed planning, and
regular inspect-and-adapt practices to maintain a consistent delivery pace.
*Scrum in SAFe:*
Scrum is often integrated into SAFe practices, especially at the team level. SAFe recognizes the
value of Scrum's principles and ceremonies for delivering value. Here's how Scrum fits into
SAFe:
1. *Scrum Teams:* In SAFe, Agile Release Trains (ARTs) are composed of multiple Scrum teams
working in sync. Each Scrum team follows the Scrum framework, with its roles (Scrum Master,
Product Owner, Development Team), events (Sprint, Daily Standup, Sprint Review, Sprint
Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment).
2. *SAFe Roles:* While Scrum roles remain largely the same in SAFe, they also include
additional roles such as Release Train Engineer (RTE) and Product Owner/Product Manager,
which are responsible for coordinating multiple Scrum teams and prioritizing work at a higher
level.
3. *Scrum of Scrums:* To ensure coordination among multiple Scrum teams, SAFe incorporates
the concept of Scrum of Scrums, where representatives from each team meet to discuss and
resolve cross-team dependencies.
4. *PI Planning:* SAFe introduces Program Increment (PI) planning, a higher-level planning
event that aligns multiple Scrum teams to a common mission and vision for a fixed period,
typically 8-12 weeks.
5. *Inspect and Adapt (I&A):* Similar to Scrum's Sprint Retrospective, SAFe includes Inspect and
Adapt (I&A) workshops at the end of each Program Increment, where teams reflect on their
work, identify areas for improvement, and adapt their processes.
*Final Thoughts:*
Understanding the principles and practices of both SAFe and Scrum is crucial for success in
organizations adopting SAFe. Remember to refer to the latest SAFe documentation and
materials provided by Scaled Agile, Inc., to ensure you have the most up-to-date and accurate
information for your exam preparation.