consolidate how we share out

[afeld]

Background information

There are a number of avenues for how we share news from the Tech Portfolio:

• Weekly by Tues 2pm: Slides for the TTS Business Weekly
  • Audience is TTS leadership, but I've been cross-posting into #infrastructure
• Every week: Solutions SMT
• Every other Wednesday: TTS Bi-Weekly Collaboration
• Every other Thursday: Sprint Review
• Monthly: TTS Newsletter
• Every other week: Sol Sentinel
• Monthly: (18F) Engineering Eagle
• Ad-hoc announcements in Slack and/or to tts@gsa.gov
• All-Hands (TTS or Solutions)

That seems like too many 😄

cc https://github.com/18F/tts-tech-portfolio/issues/243

User stories

• As a member of TTS, I want information from the Tech Portfolio about changes that affect me.
• As a member of the Tech Portfolio, I want to ensure updates are seen by the relevant folks and that time spent on them is high-value.

Implementation Steps

Initial tasks

• [x] Think of how to solve the problem
• [x] Come up with an idea to solve the problem
• [ ] Explore solutions for the problem

Tech Portfolio related tasks

• [x] Set up form for Tech Portfolio Members can provide updates for the activity they're working on
  • [x] Create a mock-up form
  • [x] Write up instructions for form
  • [x] Share form with team members

Audience related Tasks

• [x] Determine who the audience is
• [x] Spitball at which information which audience might need/want to see

Platform related Tasks

• [x] Create a team hub as a front facing portal
  • [ ] General
    • [ ] Navigation
    • [x] Shortcuts
    • [x] Quicklinks
    • [ ] Open Questions
    • [x] Announcements
    • [x] Feedback
    • [ ] Pulse Check
  • [ ] Individuals related
    • [x] Availability
  • [ ] Team
    • [x] pictures
    • [x] calendar Meetings
      • [ ] Action Items
      • [ ] Good News
      • [ ] Minutes
    • [ ] Initiatives
    • [ ] Overall Status
    • [ ] Initiative Owner
• [x] Create a sheet that form responses will feed into
  • [ ] Make design decisions
    • [ ] Initiative Sheet
    • [ ] Initiative Report
    • [ ] Initiative Dashboard
      • [ ] OKRs
      • [ ] Initiative Scope
      • [ ] Initiative Status
      • [ ] Initiative Documents
      • [ ] Initiative Risk
      • [ ] Initiative Eisenhower
      • [ ] Number of issues by status
      • [ ] Number of issues by progress
• [x] Create reports from sheets that will be displayed on dashboard
• [x] Create a central dashboard
• [x] Create a dashboard per audience group

Acceptance criteria

• We have documented what kinds of updates are shared through each mechanism

---

The assignee should add some checkboxes as a "sketch" of the steps to complete, which may evolve.

[its-a-lisa-at-work]

One of the things I think about for every Sprint Review -- is it'd be nice if every issue we had had a short description that was an easy copy/paste when needed and didn't take any rework for the purpose of status update or having to ask someone what was happening.

[its-a-lisa-at-work]

Made some progress tonight.

Have created a workspace in Smartsheet and have a TTS Updates folder; we can update the information in one sheet and then have different dashboards for the various different meetings. Still building it out; but shouldn't take more than another 2hrs at most.

[its-a-lisa-at-work]

Considering this task done and we can open up another task if necessary.