This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
generated from 18F/.github
-
Notifications
You must be signed in to change notification settings - Fork 2
Topline observations
Allison Norman edited this page Apr 22, 2021
·
1 revision
As we continue to learn more about users, the current technology and acquisition landscape, and about USFS, we have documented our observations. This is a high-level summary of what’s stood out to us after the research and conversations we’ve had so far with Forest Service civil servants and contractors. We’d like to share these early observations to help bring you along in what we’re learning as our research progresses. We still have more research to do so some of these ideas may change as we learn more.
- The current system relies heavily on people to make sure everything is done right.
- People spend a lot of effort searching for basic information they can trust.
- It’s easy to make errors, and errors are incredibly time and labor intensive to diagnose and fix.
- The design of the current tool matches the structure of the database, but not users’ mental model.
- G&A users don’t trust NRM to give them what they actually want.
- There is a high cost in licenses and support to run the legacy system.
- The data involved is manageable in size.
- The G&A application has been evolved multiple times successfully in the past.
- The modernization process that is currently underway is very risky, but it may deliver some benefits.
- It isn’t possible to run the current Oracle ADF application on the NextGen database.
- The FS OCIO may not be ready for modern architectures.
- Until the NRM Grants and Agreements development team starts using GitHub as intended, they will see little benefit, and may even make things harder for themselves.
- The Department of Agriculture IT Support Services (DAITSS) Blanket Purchase Agreement (BPA) may be required for software development services.
- The vendor pool will be limited if the DAITSS BPA is required.
- Any path forward requires collaboration among NRM, CIO, OG&A, and the USDA OCFO. These groups will need to align on a shared goal.
- There seem to be different ideas on who actually has the authority to make decisions, who will own the long-term vision and who can lead toward a shared goal.
NRM-Grants-Agreements Path Analysis
Home
How we work
Tech
- Platform and Technologies
- Architecture diagram
- Architecture Decision Records (GitHub)
- Release Engineering Process
Design
- Our design approach
- Visual styles
- Design tools
- Timeline of design activities
- Design debt
- Additional design resources
User research