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.
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.
[ ] 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.
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:
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
Acceptance Criteria