> - They have a big appetite for adding complexity to systems > - They also have a big appetite for adding work to their own plates This is actually in part a

> - They have a big appetite for adding complexity to systems > - They also have a big appetite for adding work to their own plates This is actually in part a management issue, and process issue. Whoever is managing the team's work shouldn't allow developers to go rogue and start doing whatever they want. Everything is a card. Everything is prioritised. If the work isn't going through a sanity check and being thought about in the context of everything else then the developer has gone rogue. Once you have everything being carded up properly (requirements, acceptance criteria etc) then quality control happens during card show-casing / pull-request review. If someone has gone beyond the requirements, don't let it fly during pull-request review. Separate pull-requests for separate cards - no combining them all into one, no working on multiple cards at a time. Stick to the process and be an anal card and process nazi about it. Don't let things slip. > - Their code has no consistent style This is a team standards issue. You need to get together as a team and together agree on a consistent style. People's code who breaks the standard shouldn't make it past pull-request review. You can also introduce linting tools to help enforce the standard. Assuming you have them, get the team lead and PM in a room together to discuss how to put all of this together. You might find that one of the bigger issues here aren't the team members themselves but whoever is leading the team.