My workplace has several groups that have little to no software development process. They use source control, and lightly use an issue tracking system, depending on the project. Teams are not regularly creating unit tests and running them in a CI server and not performing code reviews. This varies from project to project. It's a large company and there's no basic framework for doing software development.
I get push back from management about that "their hands are tied" to some degree with the billable customers, and that it's up to individual software developers to do this. I don't entirely agree, but I'm thinking that I should create such a process.
I'm not sure that I should define a "software lifecycle document", e.g. describing Waterfall, Agile, etc. But, I think describing using tools, e.g. "must use issue tracking", "run unit tests on a CI server", and other "best practices".
What would I call this document? Have others struggled with trying to get software teams on board with best practices? How do you overcome this?