This message was deleted.

To me, even if things are moving fast, the requirements come ahead of time from product....it seems the needs should be forecastable as a roadmap by what engineering wants....

I agree with Timothy. It’s the same problem with any Product Team :) What I do as Platform Owner is constant Feedback gathering with proactive methodologies (like VSM, Maturity Assesments etc). It gives me some clue on where Teams are heading before a „requirement” comes up. Also, I am part of Company strategy comitee, so I can forecast the future demand on Platform Services

Thanks folks, it was quite insightful and helpful

@Krzysztof H. what are the methodologies for platform product? Is there a maturity assessment you use for platform?

I personally use my own assessment -> but, a nice one (and the one I actually started with) is defined in Appendix G of "Engineering DevOps" by Marc Hornbeek