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.

Sign up for GitHub

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

Update Roadmap-and-Backlog.md #991

Merged
merged 4 commits into from
Jun 11, 2021
Merged

Update Roadmap-and-Backlog.md #991

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dac194b
Update Roadmap-and-Backlog.md
kniz-raft Jun 2, 2021
371dc79
Update Roadmap-and-Backlog.md
kniz-raft Jun 3, 2021
637c17f
Merge branch 'raft-tdp-main' into kniz-raft-patch-1
andrew-jameson Jun 11, 2021
06bbb5b
Merge branch 'raft-tdp-main' into kniz-raft-patch-1
andrew-jameson Jun 11, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions docs/Product-Strategy/Roadmap-and-Backlog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
_updated May 2021_
_updated June 2021_
# Product Roadmap
Our [roadmap](https://app.mural.co/t/officeoffamilyassistance2744/m/officeoffamilyassistance2744/1617994644349/6047bad9ed365b22986e52f5d9f01aac32286ae9) :lock:represents our latest thinking about the order in which we’ll tackle the various pieces of the overarching problem.

Expand All @@ -14,19 +14,20 @@ Value Delivered: Get approval for the authority to operate and create a producti
| User can log in using login.gov | Complete
| Users with appropriate privileges can manage users | Complete
| Users can upload data files by section and quarter | Complete
| Users with appropriate privileges can download files that were previously uploaded | In Progress
|Create production environment | Will happen after ATO
| Users with appropriate privileges can download files that were previously uploaded | In Review
|Create production environment | In Progress

## Release 1 (fka OFA MVP) Scope
Value Delivered: ACF employees can use a secure method to log into the system; this would require a PIV card.
Value Delivered: ACF employees can use a secure method to log into the system; this would require a PIV/CAC card.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to mention anything about the implementation of secret key prevention? it's definitely valuable in that this is providing reassurance about the security of TDP, but I understand if we want to focus primarily on user-facing outcomes.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, absolutely. I'll add some language in.


Our first release to production will include the functionality built for ATO (above) and also include a secure way for ACF employees to access the system, we're currently looking into integrating with HHS AMS/ACF AMS or additional options within login.gov. It is important these measures are put into place before sensitive production data is uploaded to the system.
Our first release to production will include the functionality built for ATO (above) and also include a secure way for ACF employees to access the system, we're currently looking into integrating with HHS AMS/ACF AMS, NextGenXMS or additional options within login.gov. It is important these measures are put into place before sensitive production data is uploaded to the system.

The team is also investigating options for optimizing permission management and strategy as a part of this release.
| Outcome | Status |
| -------- | ------- |
| Privileged ACF users are required to login with PIV/CAC credentials | Researching
| Permissions Configuration | Researching
| Permissions Configuration | Ready to be started
| Secret key leakage prevention | Ready to be started


## Release 2 (fka Tribal MVP) Scope
Expand All @@ -44,6 +45,9 @@ _Risks:_ The users that would be on-boarded to this process, would potentially h
| Files successfully transferred to ACF server | Not Started
| Files uploaded by STT user(s) are successfully entered into the existing TDRS system | Not Started

## Release 3 (fka STT MVP)
Value Delivered: Create a database that will parse data, communicate error messages to the user that are easier to read and act upon. The scope of this release is still being defined, but the team agrees that the priority for focusing on processing data is the next right step.

## Potential future work
In addition to the work mentioned above, we are looking forward in our research plans to develop functionality that will serve the rest of our users that includes (but is not limited to) data cleansing and validation, additional user access management tools, and/or user interface enhancements based on usability testing.
## Backlog
Expand Down