Resources for Recent SAFe Graduates

This page is specifically designed for those people having completed the SAFe Program Consultant course.  It will be useful for anyone, however, who is attempting to implement SAFe at an organization or even someone considering SAFe and having questions about how to implement it.  For more information on SAFe check out our SAFe Resources page.

Note: Many of these pages are accessible only if you register.

This site is organzied around particular issues, but check out our webinars on SAFe

Across the Value Stream

SAFe is based on Lean-Thinking and Agile methods.  An Agile Developers Guide to Lean Software Development is a good start on understanding Lean.  Pay particular attention to how mapping a value stream can often be used in conjunction with 5-whys to both identify where a challenge is and to fix it.

A cornerstone concept of Lean Software Development is to eliminate delays in value realization, workflow and feedback. These two chapters provide deeper insight into why this is so important:

Get a handout on How to do value stream mapping.

Portfolio Level

Minimum Business Increments (MBIs).  We have been using MBIs (or their equivalent) for over a decade.  If there is one practice that is essential, most useful and defines our approach, it is this.  You can think of MBIs as MVPs for established companies, only better.

Team Level

Leanban. We have used Kanban at the shared services level since we started doing SAFe.  We have also used Kanban at the team level when it was proscribed.  However, the origins of both of these approaches not only have different mindsets but are not the same as the Lean mindset we use. We created Leanban which incorporates the best practices of both Scrum and Kanban as appropriate and provides a consistent team-level and shared services level approach while enabling appropriate tailoring for the context of the people using it.

Scrum Pocket Guide. We have long implemented Scrum under the context of Lean.  We wrote this Lean-Agile Pocket Guide for Scrum Teams to help guide your way.


Acceptance Test-Driven Development is one of the most useful practices in Lean-Agile.  See our ATDD resources page.

What to do for groups < 50 people. See Using SAFe in SmaMid-Level Organizations.

How to be a Change Agent and/or Coach

The concepts of trim tabs and pick-up sticks is essential if you are going to effectively change a person or organization.

The Fundamental Attribution Error. [from wikipeida] In social psychology, the fundamental attribution error, also known as the correspondence bias or attribution effect, is the tendency for people to place an undue emphasis on internal characteristics (personality) to explain someone else's behavior in a given situation rather than considering the situation's external factors. It does not explain interpretations of one's own behavior, where situational factors are more easily recognized and can thus be taken into consideration.  Click here for a personal blog on this. 

For more information on SAFe check out our SAFe Resources page.