I'm afraid this is going to be a long post. In the first few days on my job, I would really like to get some feedback that I'm not making horrible mistakes. The final point, and what I really want to hear some comments on, is in the last paragraph where I ask about the urgency of starting O3s.
The group I'm managing is a software development team of 4 (3 developers and a tester).
As a bystander, I've observed that the team has plenty of room for improvement so they can continue to meet the top management team's expectations.
However, in the first week especially, I don't want to jump to any conclusions. Consequently, I don't plan on making any immediate changes. That all seems OK. Does everyone agree?
On the other hand, as a MT "disciple", I'm anxious to start doing at least O3s. However, there is one developer - the guy who has been there the longest (Chief Architect, created the original product, has acted as a team lead for the rest of the group), - who is really resistant to change. That includes, from what he's said, meetings, documentation, process, structure, notes, long conversations, and really anything else that he didn't come up with.
I can deal with that and it doesn't need to be a quick process. But my question now is whether anyone thinks that waiting on O3s as long as a month or two is OK? Or should I foist them on the group in the first couple weeks?