gaybro8777/tts-tech-portfolio

Home of the TTS Technology Portfolio team

Pull Request Status

Overview

TTS Tech Portfolio oversee/manage/coordinate everything technology-related that cuts across TTS, or anything technology-related that will affect TTS from the outside.

How we operate

• We work in the open, with rare exceptions
• We follow the Amazon model of reversible decisions
• We try to minimize toil and having to be reactionary for TTS and especially ourselves
• We optimize for team member happiness and productivity
• Kanban-ish and Scrum-y
• Sooner is better than later, later (or never) is better than sooner
  • Try and deliver value quickly and learn from it, while seeing what we can defer to free up time for things that are more pressing.
• Write things down
• Discussions → action items
• We practice documentation-driven development
  • While documentation (e.g. the Handbook) is generally the thing being updated (rather than a README), this should be done incrementally, and thus will be closer to README-Driven Development as it's defined in that post.
  • This applies to building/modifying process just like it applies to building software.

See also:

• Workflow
• Technical standards

Exceptions to working in the open

• When the information needs to remain confidential... for security reasons
• When the information needs to remain confidential... for contractual reasons
• When the information needs to remain confidential... for personnel reasons

Times when it is best to use reversible decisions

• When talking about something takes longer than just doing something
• When we are either accountable or repsonsible for the procedure or outcome
• When we pair it with radiating intent
• When the decision can actually be reversed

Feedback

We're open and excited to hear (anonymous) feedback to hear how we're doing!

Continuous Integration

Secret	Description
GH_PROJECT_WORKFLOW_TOKEN	GitHub personal access token with read,read:org,write:org scope.

License

See LICENSE