A defined, repeatable process frees people from spending energy thinking about solved problems, and an automated one makes this even easier. While not all development steps can be easily automated, some can, and documentation is an essential first step. Automate what makes sense and you'll have reliable processes.
Some teams get around bottlenecks by taking a “better to ask forgiveness than permission” approach. This may be expedient, but it doesn’t provide a path to changing the organizational dynamic, and it can lead to wrong decisions when wider input is advisable. A more agile way is to take an “I intend to” approach.
When things go wrong, it can be helpful to understand what happened and who was involved. However, all too often organizations (and the managers within) confuse responsibility with assigning blame. The former is essential for improvement. The latter works against an effective, collaborative, productive culture.
Building good habits is an important part of an effective Scrum team. Habits are a form of automation: The more basic processes we can automate, the more we can focus our energy on hard things. The Scrum process, with its focus on rituals, helps us by providing a framework for collaboration and making it second nature.
Scrum is a fairly minimal agile process framework that you can adapt to work best for your team. But adaptation works best once the team has internalized the principles and values of the Scrum process, and that takes practice. In other words: Before you start to adapt Scrum, first try fully adopting the framework.
Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items.
On any team, there are bound to be some differences. But even though work styles may differ from what you expect, they may not be problematic simply because they are different. Before making assumptions about what a teammate is doing or why, just ask to find out. Their differences may bring a helpful new perspective.