My premise: some scrum team members might not know their organization's end-to-end process flow for delivery.
My question: how do you the PM deal with this potential problem?
I'm aware this is not a problem unique to scrum teams but I am wondering how it's dealt with on a scrum project. On a waterfall project, it could be dealt with by planning out ad nauseam all of the delivery steps.
A trivial example is a new developer fresh off the streets who's not done big-scale development before. How does he/she know it starts with requirements, then design, then development, unit test, integration test, acceptance test, production release, repeated over and over again.
A more practical example, if your organization expects peer reviews, or solution design documents, or legal/security/privacy reviews, or special release processes to be followed, etc, etc, etc, how does the PM ensure that the team knows and follows the process?
Maybe it's not the PM's responsibility, perhaps it's the responsibility of the Scrum Master to address? Saving Changes...
