-
-
-#### Agile Development Methodology
-
-The Data Transparency team uses an Agile development/scrum methodology to build, assess, and iterate the project throughout the development lifecycle. Agile is a software development methodology characterized by short build-cycles, an emphasis on working software, and responsiveness to evolving requirements and solutions.
-
-We work in two-week sprints with each sprint focused on completing discrete, time-boxed tasks with clear acceptance criteria. At the end of the sprint, the team participates in an evaluation and review of the work accomplished and then plans for the tasks (“user stories” or “issues”) for the next sprint.
-
-This two-week cadence continues throughout the lifecycle.
-
-In addition, the team participates in a stand-up meetings to review the previous work and to report any challenges, questions, or blockers so they can be addressed and resolved quickly.
-
-The Agile/scrum process is open and transparent: stakeholders can follow the progress of the tasks in the development and publication work streams on our [JIRA](https://federal-spending-transparency.atlassian.net/secure/BrowseProjects.jspa?selectedCategory=all&selectedProjectType=all){:target="_blank"} site.
-
-Operating in the spirit of transparency, we use GitHub repositories for all our code. This external communication platform allows both internal and external stakeholders to monitor the progress of the Data Transparency efforts. To provide feedback on the code, please file an issue on the relevant GitHub repository. You can find a list of all repositories [here](https://github.com/fedspendingtransparency){:target="_blank"}.
-
-#### User-Centered Design Process
-
-The Data Transparency Team strives to have a deep understanding of who will be using the USAspending.gov site and its related data upload features. This understanding is built on town-hall meetings, workshops, and user interviews reaching the public, industry, and federal agencies. Our aim is to understand the users’ context when using these products, their motivations, requirements, and goals. This understanding constantly evolves and informs the development process.
-
-To help make our user research digestible and actionable, we developed a set of “Personas”: snapshots of user types that capture and organize information that can inform design decisions. Examples of our latest personas can be found on the User-Centered Design page. As more research is conducted and designs are tested, they will evolve and become more accurate.
-
-Finally, we test. We have developed a comprehensive plan for conducting recurring usability testing to help us identify potential design concerns. Initially, usability testing focused on agency users. Later, the focus expanded to “data consumers,” including grant recipients, researchers/reporters, and interested citizens.
-
-Usability testing will continue in a regular cadence in sync with the development cycles of our Agile development environment. More information on our user-centered design process can be found [here]({{ site.baseurl }}/user-centered-design/).
diff --git a/data-model.md b/data-model.md
index b826df17..1355eddd 100644
--- a/data-model.md
+++ b/data-model.md
@@ -3,7 +3,7 @@ published: true
permalink: /data-model/
layout: visualization
filename: data-model.md
-title: Data Model
+title: Data Model and Standards
page: data-model
---
@@ -14,3 +14,382 @@ page: data-model
# Governmentwide Spending Data Model
The Governmentwide Spending Data Model (GSDM), formerly the DATA Act Information Model Schema (DAIMS), gives an overall view of the hundreds of distinct data elements used to tell the story of how federal dollars are spent. It includes artifacts that provide technical guidance for federal agencies about what data to report to Treasury including the authoritative sources of the data elements and the submission format. The GSDM also provides clarity on how the public can better understand the inherent complexity of the data. More information can be found on the Fiscal Service [GSDM](https://fiscal.treasury.gov/data-transparency/GSDM-current.html) website.
+
+In the process to develop and mature this data model, initial collaboration with internal and external stakeholders began with a series of white papers and public feedback to gain consensus on the standardization of key spending data elements.
+
+The elements listed below represent the original consensus the federal community reached during the original DATA Act implementation. Since then, the community continues to iterate on these elements to improve standardization and overall clarity. Additional data elements will continue to be added as well, to continue improving transparency reporting. For the current data model element list visit the [GSDM](https://fiscal.treasury.gov/data-transparency/GSDM-current.html) website described above.
+#### Awardee and Recipient Entity Information
+
+This list includes information about recipients and awardees of federal funds. Please note that these elements will be standardized across the different types of awards (grants, contracts, etc.).
+
+Web Site -- Visit USAspending.gov to see the official source of accessible, searchable and reliable spending data for the U.S. government.
-Office Hours Call -- Every First Thursday of the month, Treasury and OMB staff provide updates and take agencies' questions on a conference call.
-Tech Thursdays -- We periodically hold informal working sessions for agencies to engage directly with the Data Transparency Team and ask questions regarding the Governmentwide Spending Data Model, USAspending, and the Data Broker. This is a forum for individuals to meet and collaborate with one another and share best practices. To learn more, contact the Data Transparency Team.
+Data Transparency Office Hours Call -- Periodically, Treasury and OMB staff provide updates and take agencies' questions on a conference call. To learn more, contact the Data Transparency Team.
+Data Transparency Tech Day -- We periodically hold informal working sessions for agencies to engage directly with the Data Transparency Team and ask questions regarding the Governmentwide Spending Data Model, USAspending, and the Data Broker. This is a forum for individuals to meet and collaborate with one another and share best practices. To learn more, contact the Data Transparency Team.
More Resources:
-
-
- Fiscal Service Transparency Site -
- Agency Reporting Resources +
- Government Spending and Data Model +
- Agency Reporting Resources (a PIV card is required for access)
About Federal Spending Transparency
-In May 2014, President Obama signed the Digital Accountability and Transparency Act of 2014 (DATA Act) (P.L. 113-101) into law. The DATA Act made federal spending data more accessible, searchable, and reliable. It not only made it easier to understand how the federal government spends taxpayer dollars but also served as a tool for better oversight, data-centric decision-making, and innovation both inside and outside of government. The U.S. Department of the Treasury and the Office of Management and Budget lead the governmentwide implementation of the DATA Act.
+In May 2014, the U.S. Department of Treasury and the Office of Management and Budget led the government wide implementation of the Digital Accountability and Transparency Act of 2014 (DATA Act) (P.L. 113-101), making federal spending data more accessible, searchable, and reliable. It not only made it easier to understand how the federal government spends taxpayer dollars but also served as a tool for better oversight, data-centric decision-making, and innovation both inside and outside of government.
-This collaboration space is designed to openly share our process for meeting the data transparency requirements of the DATA Act. Our sister site — USAspending.gov — is where you will find the results of this work: data you can search, view, and download. We invite you - the public - to interact with our site and share your feedback and questions on our Community Page!
+This collaboration space is designed to openly share our process for meeting the data transparency requirements of the DATA Act. . Years later, as that implementation has matured, this space is used to memorialize historical documents and provide new resources for updated information. Our sister site — USAspending.gov — is where you will find the results of this work: data you can search, view, and download. We invite you - the public - to interact with our site and share your feedback and questions on our Community Page!
+ +Operating in the spirit of transparency, we use GitHub repositories for all our code. This external communication platform allows both internal and external stakeholders to monitor the progress of the Data Transparency efforts. To provide feedback on the code, please file an issue on the relevant GitHub repository. You can find a list of all repositories here!
+ +Please view this brief video to hear from executive leaders and key stakeholders on how DATA Act leads to better data, better decisions, better government.
+## Agile Development Methodology
-Below are some specific examples of our work. For more about the user-centered design process in general, visit [www.usability.gov](http://www.usability.gov){:target="_blank"}.
+The team applies this cycle using an Agile development/scrum methodology. Agile is a software development methodology characterized by short build-cycles, an emphasis on working software, and responsiveness to evolving requirements and solutions.
+
+We work in two/three-week sprints with each sprint focused on completing discrete, time-boxed tasks with clear acceptance criteria. At the end of the sprint, the team participates in an evaluation and review of the work accomplished and then plans for the tasks (“user stories” or “issues”) for the next sprint.
+The Agile/scrum process is open and transparent: stakeholders can follow the progress of the tasks in the development and publication work streams on our [JIRA](https://federal-spending-transparency.atlassian.net/secure/BrowseProjects.jspa?selectedCategory=all&selectedProjectType=all){:target="_blank"} site.
+
+Below are some specific examples of our work. For more about the user-centered design process in general, visit [www.usability.gov](http://www.usability.gov){:target="_blank"}.
## Learn (User Research)
Through meetings, workshops, analytics, and user interviews, the Data Transparency Team works to learn about users’ needs, including what they want from the data, their technical environments (e.g., browsers, other software used), and their “pain points” with the current system.
-From that, we have developed a set of targeted user types, called “Personas.” Personas are visual encapsulations of research findings that inform the design process. **They capture real user perceptions, experiences, and quotations, which we draw on to build better software.** Photos and personal details, however, are merely representative to help make them more real and relatable.
+From that, we have developed a set of targeted user types, called “Personas.” Personas are visual encapsulations of research findings that inform the design process. **They capture real user perceptions, experiences, and quotations, which we draw on to build better software.** Photos and personal details, however, are merely representative to help make them more real and relatable. These personas can change over time.
#### Below are eight examples of our current personas: