diff --git a/content/news/2024/11/2024-11-26-broadening-public-participation-and-community-engagement-with-the-federal-government.md b/content/news/2024/11/2024-11-26-broadening-public-participation-and-community-engagement-with-the-federal-government.md new file mode 100644 index 0000000000..1845ae4541 --- /dev/null +++ b/content/news/2024/11/2024-11-26-broadening-public-participation-and-community-engagement-with-the-federal-government.md @@ -0,0 +1,34 @@ +--- +# Originally published at the following URL +source_url: https://www.performance.gov/blog/2024-public-participation-federal-government +source: performancegov +date: 2024-10-29 00:00:00 -0500 +title: "Broadening Public Participation and Community Engagement With the Federal Government" +deck: "Government works best when it incorporates transparent engagement and + feedback from the public. The White House Office of Management and Budget + (OMB) is enhancing public participation in federal decision-making through + draft guidance and a proposed toolkit. These resources aim to standardize best + practices, improve accessibility, and ensure underserved communities have + meaningful opportunities to contribute. By prioritizing transparency and + collaboration, OMB seeks to create politics that reflect the voices and needs + of the public." +summary: "Government works best when it incorporates transparent engagement and + feedback from the public. The White House Office of Management and Budget + (OMB) is enhancing public participation in federal decision-making through + draft guidance and a proposed toolkit. These resources aim to standardize best + practices, improve accessibility, and ensure underserved communities have + meaningful opportunities to contribute. By prioritizing transparency and + collaboration, OMB seeks to create politics that reflect the voices and needs + of the public." +# See all topics at https://digital.gov/topics +topics: + - best-practices + - accessibility + - communication + - digital-service-delivery +slug: broadening-public-participation-and-community-engagement-with-the-federal-government +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 +--- diff --git a/content/news/2024/11/2024-11-26-ensuring-effective-and-timely-usability-research.md b/content/news/2024/11/2024-11-26-ensuring-effective-and-timely-usability-research.md new file mode 100644 index 0000000000..76f95a0a82 --- /dev/null +++ b/content/news/2024/11/2024-11-26-ensuring-effective-and-timely-usability-research.md @@ -0,0 +1,32 @@ +--- +# Originally published at the following URL +source_url: https://www.whitehouse.gov/omb/briefing-room/2024/11/21/ensuring-effective-and-timely-usability-research/ +source: whitehouse +date: 2024-11-21 00:00:00 -0500 +title: "Ensuring Effective and Timely Usability Research" +deck: "Usability reflects how easily a user can accomplish their goals while + using a product or service. The Office of Information and Regulatory Affairs + (OIRA) has issued new guidance to streamline usability testing for federal + forms, websites, and services, helping agencies conduct usability tests in a + more quick and efficient manner that is consistent with the Paperwork + Reduction Act (PRA). By enabling faster, more effective testing, OIRA aims to + enhance public interactions with the government and ensure equitable access to + federal resources." +summary: "Usability reflects how easily a user can accomplish their goals while + using a product or service. The Office of Information and Regulatory Affairs + (OIRA) has issued new guidance to streamline usability testing for federal + forms, websites, and services, helping agencies conduct usability tests in a + more quick and efficient manner that is consistent with the Paperwork + Reduction Act (PRA). By enabling faster, more effective testing, OIRA aims to + enhance public interactions with the government and ensure equitable access to + federal resources." +# See all topics at https://digital.gov/topics +topics: + - accessibility + - communication +slug: ensuring-effective-and-timely-usability-research +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 +--- diff --git a/content/news/2024/11/2024-11-26-navigating-digital-acquisitions.md b/content/news/2024/11/2024-11-26-navigating-digital-acquisitions.md new file mode 100644 index 0000000000..8fc0a8ae53 --- /dev/null +++ b/content/news/2024/11/2024-11-26-navigating-digital-acquisitions.md @@ -0,0 +1,108 @@ +--- +date: 2024-11-26 00:00:00 -0500 +title: "Navigating digital acquisitions" +deck: "How to adopt an agile approach for modernizing websites" +summary: "Learn the best practices for agile acquisitions—from building and buying solutions, to overcoming common roadblocks." + +# See all authors at https://digital.gov/authors +authors: + - frances-carden + - ashley-owens + +# See all topics at https://digital.gov/topics +topics: + - application-programming-interface + - acquisition + - digital-service-delivery + - best-practices + - content-strategy + - usability + +slug: navigating-digital-acquisitions + +primary_image: agile-project-development-flashvector-istock-getty-images-2149784445-2160477593 + +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 + +--- + +Many of us have heard the term “agile acquisition,” but what does it look like in practice, and why is it better for digital modernizations? + +Agile [acquisitions](https://digital.gov/topics/acquisition/) are structured to reduce risks while ensuring that each solution meets a user’s complex needs throughout the web modernization process. Contracts often focus on the technical system behind the website. You may see these types of contracts involved in website modernization approaches. Typically, they begin by gathering requirements. However, if we are to change the user experience we must begin the process another way. During this phase, figuring out the problem you are trying to solve and the product (website) vision followed by user research is key — you want to ensure the assumed audience and problem is correct. User research is especially important for web modernization projects because websites are a primary way that the public interacts with the federal government. + +## Build versus buy + +Once you’ve completed user research, you face two potential avenues for procurement. You can decide either to build or buy something. The user research can help de-risk this decision. By surveying the market against user needs and pain points, you can better decide if there are existing solutions that either solve most of the user needs or if you will need to custom-build to satisfy the user needs. + +### Building in digital modernizations + +If you decide to custom create your modern website, there are a few actions you can take to ensure success. First, structure your work statement for agile collaboration by using a statement of objectives. A statement of objectives states the overall performance goals of a project and is often used in solicitations to give vendors flexibility to propose creative approaches. This is sometimes confused with a statement of work, which outlines the details of a project, including tasks, timelines, deliverables, and success criteria. A statement of work is best suited if you have decided to purchase an existing solution (such as commercial off-the-shelf, low-code, or no-code platforms). When considering a third option of a “blend” of customization and integration of existing solutions then a Performance Work Statement is often best suited. + +{{< ring title="Definitions">}} +A statement of work (SOW) is the portion of a contract that establishes and defines all non-specification requirements for a contractor's efforts either directly or with the use of specific cited documents. + +A performance work statement (PWS) is a statement of work for performance-based acquisitions that describes the required results in clear, specific and objective terms with measurable outcomes. + +A statement of objectives (SOO) is a government-prepared document incorporated into the solicitation that states the overall performance objectives. It is used in solicitations when the government intends to provide the maximum flexibility to each offeror to propose an innovative approach. That portion of a contract that establishes a broad description of the government’s required performance objectives. + +[Explore more definitions on the “ACQuipedia” by the Defense Acquisition University](https://www.dau.edu/acquipedia) +{{< /ring >}} + +Consider using a [time and materials](https://guides.18f.gov/derisking-government-tech/buying-development-services/#time-and-materials-type-contract) contract type for custom development, which gives the government flexibility to control the amount of work via user stories provided through an empowered product owner. The government product owner controls the user story backlog (a prioritized list of work to be done), which constrains the cost but allows the government to easily pivot when a new user need arises. On the other hand, consider using a firm-fixed contract type for existing solutions, and a hybrid for a blend. + +Next, ask potential vendors to showcase similar work they’ve done in the past by requesting access to code repositories that your team could analyze. You will want some experts on your team (like a software engineer or developer)— or at least informed decision makers who are able to read code repositories — to perform this code review and validate whether the code and repositories demonstrate best practices. For existing solutions, consider requesting sandbox access to have a handful of users perform usability testing for major tasks/functionality to evaluate whether potential solutions are viable and meet your needs. + +After awarding the contract, these teammates will judge work quality based on a [Quality Assurance Surveillance Plan](https://guides.18f.gov/derisking-government-tech/buying-development-services/#quality-indicators-defined-in-a-quality-assurance-surveillance-plan), including accessibility requirements. They’ll also track the vendor’s progress on the build of your website through [fundamental agile activities and meetings](https://guides.18f.gov/agile/agile-fundamentals/) like backlog refinement and sprint planning. While these surveillance plans are best suited for custom development, there are elements you can use for your existing solution, including accessibility, usability testing, and user research. + +### Buying in digital modernizations + +As stated, there may already be a product on the market that could meet your team’s needs. + +In that case, you might opt for the second procurement option: buy something. This usually means buying [commercial off-the-shelf](https://18f.gsa.gov/2019/03/26/when-to-use-COTS/) products. When you buy a product off the shelf, it’s important to understand the difference between configuration and modification: + +* **Configuration** involves using a solution’s built-in settings and tools to change its features. +* **Modification** (sometimes called customization), involves actually changing the solution’s core code to change its features. This is more complex and typically requires specialized development skills. + +While you’ll configure anything you buy to your agency’s requirements, avoid going into a purchase with plans to make dramatic modifications. Buying off the shelf and modifying requires a lot of time and money. Plus, customization of existing solutions can cause further vendor lock-in. This is why it is important to ensure the solution meets user needs before purchasing it. + +The process for selecting products you may want to buy begins with defining your problem, product vision, and conducting user research to understand the needs and pain points the product is intended to solve for. When buying a solution, use the research to conduct market research differently by using: + +* A [statement of work (PDF, 130 KB, 21 pages)](https://www.gsa.gov/system/files/SOW_Application.Services.and.Component.Framework.pdf) as your work statement +* Usability testing and scorecards (such as the [Accessibility Conformance Report and Voluntary Product Accessibility Template](https://www.section508.gov/sell/how-to-create-acr-with-vpat/)) to gauge how well a product meets your needs for function and accessibility + +Instead of receiving demos to evaluate a product’s applicability to your need, performing [usability testing](https://digital.gov/event/2018/06/14/usability-testing-with-steve-krug/) with real users can offer insight into whether a potential solution meets your needs. Ask potential users to perform their regular work with the tool to determine in a hands-on way whether it operates and meets their daily needs well. Finally, [firm-fixed-price](https://www.acquisition.gov/far/subpart-16.2) contracts are typically used when purchasing commercial products with detailed and definite specifications and quantities. These types of contracts provide maximum incentive for the contractor to control costs. + +When buying commercial off-the-shelf products, consider the Federal Risk and Authorization Management Program, commonly known as [FedRAMP](https://www.fedramp.gov/). This program was created to provide standardized security processes and requirements allowing agencies to rapidly adopt cloud service offerings. Many commercial products are not compliant with federal security requirements. + +Browse the [FedRAMP Marketplace](https://marketplace.fedramp.gov/products) to find authorized services. Also, consider whether this requirement will decrease competition as advised in the [FedRAMP frequently asked questions](https://www.fedramp.gov/faqs/). + +Budget is a common challenge to agile acquisitions. If you have a smaller budget, a minimum viable product (MVP) is a good place to start and build agency buy-in. This is useful whether you decide to buy or build. + +{{< box >}}**What is a minimum viable product?** + +A minimum viable product, or MVP, is a product with enough features to attract early-adopter customers and validate a product idea early in the product development lifecycle. +{{< /box >}} + +To develop an MVP, conduct an assessment of key technical requirements and user needs, including the price and budgetary constraints. This assessment will help stakeholders focus on the requirements they truly must have in a solution. Use these requirements to develop an MVP. As your agency’s leadership sees the visual representation of the product and reviews the honest and accurate calculations, you might receive additional funds. Throughout this process, it is important not to be overly optimistic, to overpromise, or to pack your [sprints](https://guides.18f.gov/agile/agile-fundamentals/) with more work than can be done. + +## What can I do next? + +Regardless of your decision to build or buy, factor long-term maintenance into your budgets and plans. Develop an understanding of what it will take to maintain your solution over time and plan your budget accordingly. Think about sustaining your solutions throughout its entire life cycle. Also, consider the amount of scalability you will require in the long-term. + +For more information on how to jump start your approach, check out the [18F De-risking Guide](https://guides.18f.gov/derisking-government-tech/). + +You can also join a [Digital.gov community of practice](https://digital.gov/communities/) to connect with fellow web and digital practitioners in government who are working to create better online experiences for the public. + +{{< note >}}This blog post was inspired by the fourth session of the [Spring 2024 Digital.gov Community Summit: Delivering a digital-first public experience](https://digital.gov/event/2024/03/13/spring-2024-community-summit/), which focused on navigating digital acquisitions using an agile approach. These topics included acquiring a website, how to conduct market research on possible solutions, and planning processes, hiring strategies, how to leverage contractors, as well as pricing and budgeting. + +**This session’s panelists included**: + +* Session moderator, **Ashley Owens** – Senior digital acquisition strategist, General Services Administration (GSA) +* **Justen Proctor** – Senior contracting officer, GSA +* **Andrew Nielsen** – Director of Government-wide IT Accessibility Program, GSA +* **Laura Larimore** – Senior digital strategist, Department of State (DOS) +* **Anthony Burley** – Senior project manager, Court Services and Offender Supervision Agency (CSOSA) +{{< /note >}} diff --git a/content/news/2024/11/2024-11-26-publishing-federal-sales-data-how-we-used-design-studios-and-user-testing-to-develop-a-user-centered-dataset.md b/content/news/2024/11/2024-11-26-publishing-federal-sales-data-how-we-used-design-studios-and-user-testing-to-develop-a-user-centered-dataset.md new file mode 100644 index 0000000000..edac036184 --- /dev/null +++ b/content/news/2024/11/2024-11-26-publishing-federal-sales-data-how-we-used-design-studios-and-user-testing-to-develop-a-user-centered-dataset.md @@ -0,0 +1,33 @@ +--- +# Originally published at the following URL +source_url: https://blog-nrrd.doi.gov/Publishing-Federal-Sales-Data/ +source: doi-revenuedata +date: 2024-11-19 00:00:00 -0500 +title: "Publishing federal sales data: how we used design studios and user testing + to develop a user-centered dataset" +deck: "The Open Data, Design, and Development team at the Office of Natural + Resource and Revenue (ONRR) successfully added federal sales data to the + Natural Resources Revenue Data (NRRD) platform using design studios and user + testing to create a user-centered dataset. By involving subject matter experts + and refining prototypes through feedback, the team delivered the project ahead + of schedule while meeting user needs. Future plans included additional + usability testing and expanding stakeholder engagement." +summary: "The Open Data, Design, and Development team at the Office of Natural + Resource and Revenue (ONRR) successfully added federal sales data to the + Natural Resources Revenue Data (NRRD) platform using design studios and user + testing to create a user-centered dataset. By involving subject matter experts + and refining prototypes through feedback, the team delivered the project ahead + of schedule while meeting user needs. Future plans included additional + usability testing and expanding stakeholder engagement." +# See all topics at https://digital.gov/topics +topics: + - accessibility + - human-centered-design + - content-strategy + - data-visualization +slug: publishing-federal-sales-data-how-we-used-design-studios-and-user-testing-to-develop-a-user-centered-dataset +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 +--- diff --git a/content/news/2024/11/2024-11-26-three-ways-to-write-fearless-spreadsheet-formulas.md b/content/news/2024/11/2024-11-26-three-ways-to-write-fearless-spreadsheet-formulas.md new file mode 100644 index 0000000000..7b55a87793 --- /dev/null +++ b/content/news/2024/11/2024-11-26-three-ways-to-write-fearless-spreadsheet-formulas.md @@ -0,0 +1,33 @@ +--- +# Originally published at the following URL +source_url: https://18f.gsa.gov/2024/11/05/three-ways-to-write-fearless-spreadsheet-formulas/ +source: 18f +date: 2024-11-05 00:00:00 -0500 +title: "Three ways to write fearless spreadsheet formulas" +deck: "Spreadsheet formulas can be intimidating, especially given their critical + role in government operations. Applying simple programming principles, 18F + created a resource for making formulas clearer, easier to read, and less + error-prone. 18F introduces three key techniques: using the LET function to + name variables and organize code logically, adding comments to clarify complex + formulas, and leveraging the LAMBDA function to break down problems into + manageable parts. Together, these methods transform spreadsheets from sources + of anxiety into tools of clarity and confidence." +summary: "Spreadsheet formulas can be intimidating, especially given their + critical role in government operations. Applying simple programming + principles, 18F created a resource for making formulas clearer, easier to + read, and less error-prone. 18F introduces three key techniques: using the LET + function to name variables and organize code logically, adding comments to + clarify complex formulas, and leveraging the LAMBDA function to break down + problems into manageable parts. Together, these methods transform spreadsheets + from sources of anxiety into tools of clarity and confidence." +# See all topics at https://digital.gov/topics +topics: + - analytics + - data-visualization + - digital-service-delivery +slug: three-ways-to-write-fearless-spreadsheet-formulas +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 +--- diff --git a/content/news/2024/11/2024-11-26-transition-post-3-managing-electronic-messages-and-social-media-accounts.md b/content/news/2024/11/2024-11-26-transition-post-3-managing-electronic-messages-and-social-media-accounts.md new file mode 100644 index 0000000000..809d6df414 --- /dev/null +++ b/content/news/2024/11/2024-11-26-transition-post-3-managing-electronic-messages-and-social-media-accounts.md @@ -0,0 +1,29 @@ +--- +# Originally published at the following URL +source_url: https://records-express.blogs.archives.gov/2024/11/08/transition-post-3-managing-electronic-messages-and-social-media-accounts/ +source: nara +date: 2024-11-08 00:00:00 -0500 +title: "Transition Post 3: Managing Electronic Messages and Social Media Accounts" +deck: "The National Archives and Records Administration (NARA) released a new + blog on the management of federal records and transitions for federal + agencies. Shedding light on the usage of agency-managed communication + platforms and social media accounts, agencies are given instructions on how to + best comply with the requirements outlined in the Federal Records Act." +summary: "The National Archives and Records Administration (NARA) released a new + blog on the management of federal records and transitions for federal + agencies. Shedding light on the usage of agency-managed communication + platforms and social media accounts, agencies are given instructions on how to + best comply with the requirements outlined in the Federal Records Act." +# See all topics at https://digital.gov/topics +topics: + - best-practices + - communication + - digital-service-delivery + - cloud-and-infrastructure + - governance +slug: transition-post-3-managing-electronic-messages-and-social-media-accounts +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 +--- diff --git a/content/news/2024/11/2024-11-26-tts-made-a-lasting-impact-with-civic-tech-in-fy24.md b/content/news/2024/11/2024-11-26-tts-made-a-lasting-impact-with-civic-tech-in-fy24.md new file mode 100644 index 0000000000..00050ed9f0 --- /dev/null +++ b/content/news/2024/11/2024-11-26-tts-made-a-lasting-impact-with-civic-tech-in-fy24.md @@ -0,0 +1,26 @@ +--- +# Originally published at the following URL +source_url: https://www.gsa.gov/blog/2024/11/21/tts-made-a-lasting-impact-with-civic-tech-in-fy24 +source: gsa +date: 2024-11-21 00:00:00 -0500 +title: "TTS made a lasting impact with civic tech in FY24" +deck: "The Technology Transformation Services (TTS) made significant strides to + prioritize and improve federal digital services in FY 2024. From expanding + Login.gov to over 72 million users, launching tools like Notify.gov, or + redesigning Vote.gov in 19 languages, explore how TTS continues to set the + standard for impactful civic tech innovation." +summary: "The Technology Transformation Services (TTS) made significant strides + to prioritize and improve federal digital services in FY 2024. From expanding + Login.gov to over 72 million users, launching tools like Notify.gov, or + redesigning Vote.gov in 19 languages, explore how TTS continues to set the + standard for impactful civic tech innovation." +# See all topics at https://digital.gov/topics +topics: + - accessibility + - digital-service-delivery +slug: tts-made-a-lasting-impact-with-civic-tech-in-fy24 +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +weight: 1 +--- diff --git a/content/resources/introduction-to-federal-web-standards.md b/content/resources/introduction-to-federal-web-standards.md new file mode 100644 index 0000000000..b0feb61f32 --- /dev/null +++ b/content/resources/introduction-to-federal-web-standards.md @@ -0,0 +1,86 @@ +--- +date: 2024-11-26 10:12:00 -0500 +title: "An introduction to federal website standards" +deck: "Understand how and why to use the federal website standards" +summary: "The federal website standards help agencies provide high-quality, consistent digital experiences for everyone. They cover common visual technical elements and reflect user experience best practices." + +# See all topics at https://digital.gov/topics +topics: + - digital-service-delivery + - content-strategy + - design + - governance + - product-and-project-management + +# See all authors at https://digital.gov/authors +authors: + - michelle-rago + +slug: introduction-to-federal-web-standards +primary_image: "hands-puzzle-pieces-girafchik123-istock-getty-images-2091035051" + +# Controls how this page appears across the site +# 0 -- hidden +# 1 -- visible +# 2 -- highlighted +weight: 1 + +--- + +## What are the federal website standards? + +Federal agencies are required to comply with website standards per the 21st Century Integrated Digital Experience Act (21st Century IDEA). + +The federal website standards align with 21st Century IDEA, OMB Memo M-23-22, Delivering a Digital-First Public Experience, and other relevant policy requirements and best practices. The standards cover common visual and technical elements and reflect user experience best practices. + +{{< ring title="Understand the policy framework">}} + +[Explore the requirements for delivering a digital-first public experience in 21st Century IDEA and M-23-22](https://digital.gov/resources/delivering-digital-first-public-experience/) + +{{< /ring >}} + +The standards website includes pending standards that will be required after a specific period of time and standards that are in development so you can contribute to the process. Each standard includes acceptance criteria that specify how to comply with the standard. + +Visit [standards.digital.gov](https://standards.digital.gov/) to learn more about the federal website standards. + +## Why are the federal website standards important? + +Most people interact with the federal government online. There are about [2 billion visits to federal websites](https://analytics.usa.gov/) by the public every month. It is critical that government websites and digital services are effective and easy to use. + +The federal website standards help agencies provide high-quality, consistent digital experiences for everyone. And, increased standardization and cross-government collaboration can reduce implementation costs for all agencies. + +## How are standards developed? + +GSA’s [Technology Transformation Services](https://tts.gsa.gov/) manages standards development and publication through the Federal Website Standards program. + +The standards are developed through an open and iterative process involving federal agencies, the public, and other stakeholders and are published incrementally in the following four stages: + +* **Research:** The standard is being researched with the public, federal agencies, and other stakeholders. +* **Draft:** The standard has been drafted and is being shared with federal agencies and other stakeholders for feedback and iteration. +* **Pending:** The standard has been finalized. It will be required after a specified time period following its move to the pending status. Federal agencies can begin working to comply with pending standards. +* **Required:** Federal agencies are required to comply with this standard. + +Visit the standards website to read more about [how standards are developed](https://standards.digital.gov/about/). + +## What can I do next? + +As a federal web practitioner, you can take the following actions: + +* Review the standards at [standards.digital.gov/standards](http://standards.digital.gov/standards). +* Consider how the standards apply to your websites and digital services that are intended for use by the public. +* Plan to evaluate your compliance with the [pending standards](https://standards.digital.gov/standards/#:~:text=at%20this%20time.-,Pending,-Pending%20standards%20are). +* Share this information with digital teams in your agency. + +You can also browse related resources: + +* Familiarize yourself with [U.S. Web Design System components](https://designsystem.digital.gov/components/overview/). +* Explore topical guides, blogs, and events on Digital.gov: + * [Digital service delivery](https://digital.gov/topics/digital-service-delivery/) + * [Governance](https://digital.gov/topics/governance/) + * [Information architecture](https://digital.gov/topics/information-architecture/) + +### Get involved + +To share your feedback on the federal website standards, email GSA’s standards team at [website.standards@gsa.gov](mailto:website.standards@gsa.gov) or join a [discussion on GitHub](https://github.com/GSA-TTS/federal-website-standards/discussions). + +You can also join Digital.gov’s [Web Managers Community](https://digital.gov/communities/web-content-managers/) to learn more about how other government web practitioners implement governance strategies and manage their content. diff --git a/data/images/agile-project-development-flashvector-istock-getty-images-2149784445-2160477593.yml b/data/images/agile-project-development-flashvector-istock-getty-images-2149784445-2160477593.yml new file mode 100644 index 0000000000..1de32c5415 --- /dev/null +++ b/data/images/agile-project-development-flashvector-istock-getty-images-2149784445-2160477593.yml @@ -0,0 +1,21 @@ + + # https://s3.amazonaws.com/digitalgov/agile-project-development-flashvector-istock-getty-images-2149784445-2160477593.png + # Image shortcode: {{< img src="agile-project-development-flashvector-istock-getty-images-2149784445-2160477593" >}}' + date : 2024-11-26 22:00:16 -0400 + uid : agile-project-development-flashvector-istock-getty-images-2149784445-2160477593 + width : 1200 + height : 630 + format : png + + # REQUIRED alternative text for accessibility. + # Keep within 150 characters. https://capitalizemytitle.com/character-counter/ will count characters. + alt : "Illusttration with three figures around agile, cost, and metrics icons for product development." + + # Caption text appears below the image; usually the attribution for stock images. + # Must be different from the alt text. + caption : "Flashvector/iStock via Getty Images" + + # Credit text appears after the caption text, separated by an m-dash. + # Example https://digital.gov/2023/12/08/making-gsa-public-art-collection-more-accessible/ + credit : "" + diff --git a/data/images/hands-puzzle-pieces-girafchik123-istock-getty-images-2091035051.yml b/data/images/hands-puzzle-pieces-girafchik123-istock-getty-images-2091035051.yml new file mode 100644 index 0000000000..23aa5c3e9c --- /dev/null +++ b/data/images/hands-puzzle-pieces-girafchik123-istock-getty-images-2091035051.yml @@ -0,0 +1,21 @@ + + # https://s3.amazonaws.com/digitalgov/hands-puzzle-pieces-girafchik123-istock-getty-images-2091035051.png + # Image shortcode: {{< img src="hands-puzzle-pieces-girafchik123-istock-getty-images-2091035051" >}}' + date : 2024-11-25 20:53:41 -0400 + uid : hands-puzzle-pieces-girafchik123-istock-getty-images-2091035051 + width : 1200 + height : 630 + format : png + + # REQUIRED alternative text for accessibility. + # Keep within 150 characters. https://capitalizemytitle.com/character-counter/ will count characters. + alt : "Illustration of two hands putting together multi-colored puzzle pieces." + + # Caption text appears below the image; usually the attribution for stock images. + # Must be different from the alt text. + caption : "" + + # Credit text appears after the caption text, separated by an m-dash. + # Example https://digital.gov/2023/12/08/making-gsa-public-art-collection-more-accessible/ + credit : "girafchik123/iStock via Getty Images" + diff --git a/data/job_board.yml b/data/job_board.yml index aca8ecd4dd..6bb2fcdd8b 100644 --- a/data/job_board.yml +++ b/data/job_board.yml @@ -8,14 +8,13 @@ - - title: Community Outreach Specialist department: Department of Homeland Security location: Anywhere in the U.S. (remote job) description: > 6-month non-reimbursable assignment with the possibility of extension. Office of the Citizenship and Immigration Services Ombudsman (CIS Ombudsman) Community Outreach Specialist Series Requested: 0301 Security Clearance: None Virtual/Remote: Yes Only current, full-time federal employees are eligible. Resumes are reviewed every 30 days until selection/closing date. This is a Detail, not a Developmental Rotation. Supervisory approval form must be signed. open_date: 2024-09-03 - close_date: 2024-11-29 + close_date: 2024-12-18 apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/807704100 cop_topics: - Communicators @@ -43,17 +42,6 @@ cop_topics: - Communicators -- title: Management and Program Analyst - department: Department of Homeland Security - location: Anywhere in the U.S. (remote job) - description: > - This position is located in External Affairs Directorate, Office of Access and Information Services, Digital Services Division. As an Management and Program Analyst, you will provide analysis, program/product support, and advice to branch and division leadership on division products and features. - open_date: 2024-11-13 - close_date: 2024-11-22 - apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/818686500 - cop_topics: - - User Experience - - title: Visual Information Specialist department: Department of the Treasury location: Location Negotiable After Selection @@ -158,31 +146,6 @@ cop_topics: - Communicators -- title: Program Specialist (Direct Hire) - department: National Aeronautics and Space Administration - location: Multiple Locations - description: > - The Office of the Chief Information Officer (OCIO) at NASA Headquarters is currently seeking a highly qualified candidate to serve as an Internal Communications Specialist. This position is a critical part of the OCIO Customer Engagement Office, responsible for coordinating across OCIO to improve the effectiveness of communications and outreach products and activities aimed at internal stakeholders. - open_date: 2024-11-20 - close_date: 2024-11-22 - apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/819497300 - cop_topics: - - Communicators - - Plain Language - - User Experience - -- title: Program Analyst - department: Department of Veterans Affairs - location: Multiple Locations - description: > - The incumbent reports to the Media Manager and serves as the Web Operations Manager working closely with the Enterprise Support Service (ESS) Executive Leadership Team (ELT) and the Healthcare Environment and Facilities Program (HEFP) Content Management Team (CMT). The incumbent oversees all strategic and operational website initiatives, website content management and integration of functional website processes utilizing new and current information technology systems and applications. - open_date: 2024-11-20 - close_date: 2024-11-26 - apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/819845200 - cop_topics: - - Web Analytics - - Web Managers - - title: Division Chief of Product Management, GS-0301-15, FPL 15 (DE) department: Department of Education location: Washington, District of Columbia @@ -206,3 +169,98 @@ cop_topics: - User Experience - Web Managers + +- title: Associate Chief Information Officer for Application and Digital Solutions + department: Department of Transportation + location: Washington, District of Columbia + description: > + The Chief Information Officer (CIO) leads the Office of the Chief Information Officer (OCIO) organization and serves as the principal advisor to the Secretary of Transportation and DOT Operating Administrations on matters involving information technology (IT), information assurance - cybersecurity, privacy, and records management; portfolio management; IT infrastructure and operations; IT innovation and emerging technologies; enterprise date management; and applications and digital solutions. + open_date: 2024-11-05 + close_date: 2024-12-05 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/817601500 + cop_topics: + - Web Managers + +- title: Digital Communications Strategist (Customer Experience) + department: Department of Commerce + location: Alexandria, Virginia + description: > + This position is located in the Office of the Chief Communications Officer (OCCO), United States Patent and Trademark Office (USPTO). OCCO is responsible for all aspects of USPTO's public affairs and communication activities which include media relations, internal communication, graphic design, social media, brand management, blogs and special initiatives, photography and video, writing and editing, digital strategy and governance, and oversite of web content on USPTO.gov. + open_date: 2024-11-25 + close_date: 2024-12-06 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/820782100 + cop_topics: + - Web Analytics + - Web Managers + +- title: Digital Communications Strategist (Customer Experience) + department: Department of Commerce + location: Alexandria, Virginia + description: > + This position is located in the Office of the Chief Communications Officer (OCCO), United States Patent and Trademark Office (USPTO). OCCO is responsible for all aspects of USPTO's public affairs and communication activities which include media relations, internal communication, graphic design, social media, brand management, blogs and special initiatives, photography and video, writing and editing, digital strategy and governance, and oversite of web content on USPTO.gov. + open_date: 2024-11-25 + close_date: 2024-12-06 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/820781900 + cop_topics: + - User Experience + - Web Analytics + - Web Managers + +- title: Director of Communications and Outreach, AD-0301-00 (Senior Manager) (Excepted Service) + department: Department of Education + location: Washington, District of Columbia + description: > + The Director Communication and Outreach is located in Principal Deputy Chief Operating Officer (PDCOO) in Washington, DC. This position is a key leader at FSA, reporting to the Principal Deputy Chief Operating Officer, and is responsible for advising senior staff on proposals and issues involving controversy, intensive outside interest, or significant long-range effects on the programs. + open_date: 2024-11-25 + close_date: 2024-12-08 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/820791300 + cop_topics: + - Communicators + +- title: Digital Communications Specialist + department: Department of Commerce + location: Alexandria, Virginia + description: > + This position is located in the Web, Marketing, and Communications Division (WMC), Office of Patent Information Resources (OPIR), Office of Information Technology for Patents (OITP), Office of the Commissioner for Patents, U.S. Patent and Trademark Office (USPTO). Web, Marketing, and Communications Division (WMC) provides marketing and outreach services to facilitate greater understanding and knowledge of policy development and implementation of the various programs and applications. + open_date: 2024-11-25 + close_date: 2024-12-10 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/820912300 + cop_topics: + - Communicators + - Web Managers + +- title: Information Technology Specialist (INET) + department: Department of Commerce + location: Alexandria, Virginia + description: > + This position is located in the Web, Marketing, and Communications Division (WMC), Office of Patent Information Resources (OPIR), Office of Information Technology for Patents (OITP), Office of the Commissioner for Patents, U.S. Patent and Trademark Office (USPTO). Web, Marketing, and Communications Division (WMC) provides marketing and outreach services to facilitate greater understanding and knowledge of policy development and implementation of the various programs and applications. + open_date: 2024-11-25 + close_date: 2024-12-10 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/820907900 + cop_topics: + - Communicators + - Web Managers + +- title: Information Technology Specialist (INET) + department: Department of Commerce + location: Alexandria, Virginia + description: > + This position is located in the Web, Marketing, and Communications Division (WMC), Office of Patent Information Resources (OPIR), Office of Information Technology for Patents (OITP), Office of the Commissioner for Patents, U.S. Patent and Trademark Office (USPTO). Web, Marketing, and Communications Division (WMC) provides marketing and outreach services to facilitate greater understanding and knowledge of policy development and implementation of the various programs and applications. + open_date: 2024-11-20 + close_date: 2024-12-10 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/820911000 + cop_topics: + - Communicators + - Web Managers + +- title: Customer Experience Strategist + department: Department of Homeland Security + location: Multiple Locations + description: > + The Office of Inspector General (OIG) is an independent office whose mission is to promote excellence, integrity, and accountability throughout the Department of Homeland Security (DHS). In our dynamic environment, the OIG conducts investigations, audits, evaluations, and inspections to enhance program effectiveness and efficiency and to detect and prevent waste, fraud, and mismanagement in DHS programs and operations. + open_date: 2024-11-25 + close_date: 2024-12-04 + apply_link: https://www.usajobs.gov:443/GetJob/ViewDetails/820794100 + cop_topics: + - User Experience + - Web Managers \ No newline at end of file