Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TTS Tech Operations - Cloud Service Provider - Future State (Slide Deck) #1685

Open
6 of 10 tasks
JJediny opened this issue May 16, 2024 · 4 comments
Open
6 of 10 tasks
Assignees

Comments

@JJediny
Copy link
Member

JJediny commented May 16, 2024

Acceptance Criteria

  • Covers all planned work the Tech Operations Engineering division will participate in
    • Delineates our work from GSA IT, Devtools, Cloud.gov
    • Describes areas of collaboration with others TTS/GSA offices
    • Describes scope constraints and wont fix
  • Internal Team review
  • TTS Program review
  • GSA IT review
  • Cloud.gov review
@JJediny JJediny self-assigned this May 16, 2024
@JJediny
Copy link
Member Author

JJediny commented May 17, 2024

Need to develop acceptance criteria for audience

  • TTS Leadership/Programs

@JJediny JJediny assigned MichaelSides and nateprice18f and unassigned JJediny May 22, 2024
@MichaelSides
Copy link

Question @JJediny
From your perspective, should this be limited to our engineering team or be inclusive of all TTS Tech Ops? This can obviously be a major topic of discussion when we schedule the internal meeting with Tech Ops, but would like us to nail down scope prior. I see value in it being all inclusive.

@MichaelSides
Copy link

Describes scope constraints and wont fix: Not sure that this is clearly conveyed. Part of this is pending role and responsibility definitions/clarification at the division level. Possibly add a slide to relay this constraint/challenge?

@JJediny
Copy link
Member Author

JJediny commented Jun 5, 2024

Question @JJediny From your perspective, should this be limited to our engineering team or be inclusive of all TTS Tech Ops? This can obviously be a major topic of discussion when we schedule the internal meeting with Tech Ops, but would like us to nail down scope prior. I see value in it being all inclusive.

~All-inclusive with the technical details presented for those tech-savy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants