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

Create a self-serve playbook for SaaS/software acquisition at TTS #1586

Open
6 tasks
adborden opened this issue Oct 13, 2021 · 1 comment
Open
6 tasks

Create a self-serve playbook for SaaS/software acquisition at TTS #1586

adborden opened this issue Oct 13, 2021 · 1 comment
Assignees
Labels
g: accepted Issue has been fully groomed.

Comments

@adborden
Copy link
Contributor

adborden commented Oct 13, 2021

Background Information

In order to understand the SaaS/software acquisition process and effectively procure SaaS/software products that I need in order to do my job at TTS, TTS members want a playbook for SaaS/software acquisition within GSA.

Outcome from our recent retrospective and team scope discussions:

User story: write a first draft playbook for software acquisition at TTS. Highlight initial conversations: is there a similar tool that is approved? Compliance takes time and depends on other teams GSA and vendor. Look in the handbook and software concierge for existing work.

We believe that a playbook documenting the process and guiding users will enable self-service for TTS individuals and reduce burden on the TTS team playing a middleman. We believe this playbook strategy could be effective for other areas of responsibility within Tech Portfolio. This story will serve as a test for this hypothesis.

There is already a lot of content to crib off of:

Implementation Steps

  • Write a playbook for SaaS/software acquisition focused on self-service for TTS members that leverages the GSA IT process.
  • The playbook meets this criteria:
    • Outlines the process to provide a clear overview
    • Steps are actionable
    • Expectations of the Tech Portfolio and the role they play (if any) in the process is well defined
  • Run some kind of simple pilot.
  • Update documentation in the handbook to guide folks to this playbook.
  • Identify other areas where the playbook strategy might be effective and write up additional user stories.

Acceptance Criteria

  • WHEN a TTS member searches the handbook for software acquisition
    THEN they are guided to the playbook that outlines the process and provides clear and actionable steps for how to acquire SaaS/software products.
@adborden adborden added the g: initial Issue template needs to be filled out, and/or initiative/timing labels need to be added. label Oct 13, 2021
@adborden adborden self-assigned this Oct 13, 2021
@adborden adborden changed the title [placeholder] Review team scope and responsibilities around SaaS Create a self-serve playbook for SaaS/software acquisition at TTS Oct 13, 2021
@adborden
Copy link
Contributor Author

Handbook updates, this should evolve into the "playbook" https://docs.google.com/document/d/1YqHpxuhJIpN8fIeh8CZHoQbEdLsVcPP-eOQ8oLRJt-k/edit

@adborden adborden assigned JJediny and rocheller123 and unassigned adborden Oct 14, 2021
@adborden adborden added g: accepted Issue has been fully groomed. and removed g: initial Issue template needs to be filled out, and/or initiative/timing labels need to be added. labels Oct 14, 2021
@rocheller123 rocheller123 moved this from In Progress to Waiting/Feedback in TTS Technology Portfolio (DEPRECATED/ARCHIVE) Nov 15, 2021
@JJediny JJediny moved this from Waiting/Feedback to Ready (Sprint Planned) in TTS Technology Portfolio (DEPRECATED/ARCHIVE) Apr 4, 2022
@JJediny JJediny removed this from Ready (Sprint Planned) in TTS Technology Portfolio (DEPRECATED/ARCHIVE) Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
g: accepted Issue has been fully groomed.
Projects
None yet
Development

No branches or pull requests

4 participants