Guest User

Untitled

a guest
Apr 26th, 2018
64
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.06 KB | None | 0 0
  1. ## Process - Armani, Infrastructure and Bootcamp
  2.  
  3. ### What practices are working? (processes, meetings, artifacts, agreements within the team including work with stakeholders)
  4.  
  5. * Bootcamp's dailies are working well, they don't go too technical, they use 1:1 calls instead to get help on tickets.
  6. * Armani: Meetings (Pre-planning, daily, planning, retro). They stick to the agenda, have the right people, use MYGA as the agenda, have well-written cards and outcomes (of Retros) are used constructively.
  7. * Armani: Including PM as part of the team. They are aligned well.
  8. * Infra dailies are working well. Good perspective on what's going on, despite unforeseen cards that pop up every day.
  9. * Bootcamp's weekly retros are working well, constructive improvements
  10. * Armani: Each team has the flexibility to set up their own process, depending on their stakeholder, team experience and demands on the team (high predictability, etc.). They have the ​flexibility to use Retro outcomes as they see fit, what's best for that team.
  11.  
  12. ### What practices are not working?
  13.  
  14. * Armani: Tuesday's TL/PM sync up meeting is pointless and only serves Taso. It doesn't help to alleviate cross-team issues.
  15. * Armani: The weekly report, nobody reads it, too much work. How about a channel instead to announce initiatives where people can engage and ask questions? Jonatas: people can then subscribe to initiatives they are interested in.
  16. * Bootcamp's Reminder: would love to have a PM that can create general (not team-specific) feature tickets for the developers in Bootcamp. Actually, anyone to create a ticket in YouTrack and tag it for Bootcamp to work on. Right now they only have technical tickets.
  17. * Armani: Processes (bureaucracy to remove functionality, some dependency​ from other teams). Especially when working with Analytics; lots of blockers when working with them. Jonatas' suggestion is to have 1 analytics and 1 infrastructure person on each team, and function like a guild instead. He also said that reaching out and working with people 1:1 (instead of in a channel) can help.
  18.  
  19. ### Suggestions
Add Comment
Please, Sign In to add comment