[tylertyler]

The team you are working with has very little experience so a lot of what they will be doing is learning, you need to give time for this but ideally you find ways to point them to standard ways of doing things and have them read rather than needing to reinvent the wheel. Where I work we do a loose form of agile which has lots of resources you can point people to. Below are my answers to your questions.

1. Daily

2. Every other week for an hour along with meeting when things come up.

3. Daily stand ups, every other week planning, retros.

4. Anything people work on that needs to be documented is done as part of their work. Changes to the system assume changes to documentation. Systems that others need to use more require more documentation but we don't put to much pressure on all of this because too much documentation can also be a pain.

5. Some people block off afternoon from meetings, I prefer to do this work in waves, when there is lots to talk about make sure these conversations happen, when everyone understands what needs to be done they are heads down working on it and I do my best to do the same.

6. Higher level meetings with leadership to align on goals get converted into team goals which are then converted into stories by engineering leads, in weekly planning we go over these tickets to make sure everyone is on the same page, sometimes new tickets need to be made for missing work but we try to make sure that everyone has enough work for the next chunk of time. You can check in on the status in standup and if something is off adjust something by adding more people to one ticket or breaking it up.

Another key thing to take into account is how to enable feedback from the people doing the work back up. You must enable the team to influence the goals and the work they are doing, sometimes they see a better way and it is important that they feel heard even if the path isn't changed.