It is revised monthly
SAFe is not versioned the way ITIL or PRINCE2 are. The framework team publishes updates in the first week of every month — new and revised articles, new glossary terms, renamed concepts — with larger announcements at the annual summit.
Why it is like this
Continuous revision keeps the framework close to practice and lets it absorb things like AI without waiting years for an edition. The trade is that "what SAFe says" has no stable referent: it is a date, not a version number.
Not to be confused with
A versioned standard you can cite once. Citing SAFe responsibly means naming the date you read it — which is why every page on this site carries one, and why this topic will go stale faster than any other here.
In practice
Compare the neighbours: ITIL 4 dates from 2019 and PRINCE2 7 from 2023. SAFe may have changed since you started reading this card.
Source: What's new in SAFe? — the framework's own change log — "updated during the first week of each month". Read on .
SAFe® and Scaled Agile Framework® are registered trade marks of Scaled Agile, Inc. ytyk.org is not affiliated with, endorsed by or licensed by Scaled Agile, Inc. These cards are independent commentary written in our own words; no SAFe text, graphic or Big Picture is reproduced here.
Predict Check yourself
How should you cite a SAFe claim so that a reader can check it a year from now?
Show the answer
By naming the article or glossary term and the date you read it — the framework is revised monthly and has no stable version to cite.
A date is the only thing that stays true. It is also why this topic carries a louder staleness warning than the regulations do.