10.2 Feedback from Coach Louise Lockie - SFDO-Community-Sprints/The-Technical-Collective GitHub Wiki

Louise’s Technical Expert Feedback

Onboarding

  • What are my roles and responsibilities?
    • At what point does a technical coach step in
    • What are my actions / responsibilities ?
    • What am I agreeing to?
    • Do I need to clean up after admins?
  • What guidelines do I need to give to the jr admin?
    • Best practices documentation

Project management/project plan

  • Create a roles/responsibilities and promises/expectations for the Project Manager
    • Can the technical expert sometimes be the PM?
  • How do we best manage the collaboration of admins?
    • Do we have them working in separate sandboxes?
    • Do we have them testing each others’ work?
    • How do we split the build?
  • How are we going to work with a third party?
    • Creating promises / expectations for the third party persona
    • Need access for jr admin/coaches to stakeholders
    • Sourcing projects needs to still be eligible for free licenses
    • Clear time frames
    • Requirement to stick to the TCC structure
    • What are the check-in points?
    • Summary notes on the Slack channel
    • Pinning summaries in the Slack channel to ensure they are easily visible
    • Major update points
    • Ensuring they are working in the context of one of our defined roles in the way that we expect that role to function.

Documentation updates

  • What to do when you’re getting a project? Build in a sandbox, not prod No admin access for non-admin users
  • How to manage meetings? Agenda and scheduling Who are the participants? Where is the meeting taking place? Who is responsible for syncing calendars? Who is writing the agenda? Who is leading? Who is taking notes? Need to share in Slack channel after meeting for visibility. At the end of meeting: What are the next steps? Who owns the next steps to keep the project moving? Who sending the meeting summary? How do we document?

Everything has to be linked into the main google doc Options to create technical documentation or user-friendly playbooks, but they need to be linked in. Give examples of documentation to go off of and show what good looks like.