I think trying to do a big bang deployment of scrum in a slow organisation bureaucratic organisation is probably a bad idea. Probably best idea is something us

I think trying to do a big bang deployment of scrum in a slow organisation bureaucratic organisation is probably a bad idea. Probably best idea is something using kanban. Map the existing process using kanban. Find bottle necks, and fix the process. Start changing bits to it. Start using TDD, maybe user stories, maybe add "sprint" planning meetings. You might not be implementing "true agile", but its better than complete disaster trying to enforce everything suddenly. Also this comment he stated in the comments makes me uncomfortable. "being uncomfortable committing to an outcome that’s time-boxed" " sticking to a 5-to-9 mentality " You shouldn't really being "commiting" to a time box. Its a guess, not a commitment. You use velocity to get better at the guess. If you miss, oh well lets get better at it next time by adjusting the story points in a sprint. He makes sound like he expecting people to work overtime to meet a commitment. This is not recommended in scrum. You should have a normal work time mentality and work requirements should fit into normal hours. If you miss the "guess", you should adjust the next sprint to not include as much. If you work overtime to meet the commitment, you re-enforce the idea that it is ok to commit a overloaded amount of work to a sprint. Bad. Bad. Bad. That can be abused.