SAFe Enterprise Backlog Structure and Management
Good news is that SAFe is an effective, freely-revealed, and (deep) knowledge repository for Lean-Agile development at enterprise scale.
Bad news is that, given the just-in-time and just-for-me random access nature of the knowledge base, it has a hard time ‘telling its own story.’ In other words, even with the Big Picture, it isn’t always obvious how the various pieces and parts work together to create the full system that makes SAFe actually work. One of those critical areas is how the system description artifacts—Stories, Features, Capabilities, and Epics—work together to align the portfolio to a common purpose. Not to mention who-does-what-and-when to make sure the various backlogs are always shipshape.
New SAFe SPCT and now SAFe Contributor, Charlene M. Cuenca of Icon Technology, (congratulations Charlene!) took the time to put this story together. She uses it in her trainings and we asked her to share it with us. She has now done so in the form of the new Advanced Topic article SAFe Enterprise Backlog Structure and Management. (Note: you can also access it from the handy new ‘Advanced Topic’ widget on the home page. And yes, for those who notice such things, we changed the name ‘Guidance Articles’ to ‘Advanced Topics’.)
Here’s an intro in the author’s own words:
“To achieve successful program execution, organizations need an efficient system that defines the backlogs of the value to be delivered, the roles that manage them, and the proper timelines for refinement at every level of SAFe … this article illustrates how to connect the levels to enable ‘continuous Program Increment (PI) readiness.”
An here’s an image to give you a further idea of the value she provides in this article.
But in order to learn more, you’ll need to read the article.
Thanks Charlene and stay SAFe!
– Dean and the Framework Team