I am a SAFe rookie. Everyone in our company knows, and I am not shy to tell. I have set out to write this book about scaling agile to change this. So at the time of you reading this, I may no longer be the rookie that I was when I wrote these lines. But it does not matter much. At any time in the foreseeable future, there will be people knowing more about the topic than I do. And there is a specific strength in this situation. I can write this book from an angle that suits most of the intended audience of this book. So I hope that you'll like that.
If you don't know stuff inside out and have little experience, it's a good idea to ask experts and specialists. That's why I have invited central people from the SAFe and scaling agile community to talk to me about their findings, common pitfalls, and tips that they have for SAFe beginners like me to get in the know.
Those interviews are diverse and not structured. But I have prepared for all of them individually to try to get the most out of them. All interviewees received the questions upfront and had the chance to review the write-ups afterward.
I would like you to contact me about a SAFe interview if you have something interesting to share. Here are some questions that I ask in interviews:
If you have answers to these questions, please do not hesitate to contact me via the form on this page. Also if these questions do not match your situation, please contact me nevertheless. I have talked to SAFe methodology sceptics just as well and would love to present our readers a broad and balanced view.
Publicly documented Interviews
Most of the interviews we did will eventually become public. But the process involves editing, proofing, and approving by the interviewee. So a conversation with a SAFe expert can only become public after all this.
If you know someone whom we should interview or if you are interested in becoming an interviewee yourself, please use the form on the right to contact us.
This is a work in progress book project. All research and preparations are public. Learn more.