Trailing2Dots
* When a project is declared "finished" break the team apart and spread them about the company. Because the original dev never see the code again, why should they care.
* When a project is late, and it always is, pull out the original schedule rammed down our throats when the project was first started. Then it's easy to see who to blame.
* Have legal (YES!) decide rules for agile. True: they decided on 1 week deliverables, demanded complete documentation per week, insisted on a waterfall approach to design and dev. "When you've done it, you don't have to revisit the past!"
* Documentation was in charge of dev: "They read the docs and know what needs to be done:. I never figured out who "they" were.
* Create a lengthy, complex paper trail for deliverables.
True story of one company - now extinct. They had about a 50% turnover rate.
Eventually I was enrolled in courses aimed primarily at professional therapists. They certainly welcomed me as they need people to practice with as they themselves are learning new techniques.
This series has enormously transformed both my professional and personal life. Highly recommended.