A description of the work

When the FFS team revised the De-risking Guide, we talked with various state employees in procurement, digital services, tech. Nearing the end of the time available to write the guide, those conversations were indicating significant interest in no-code/low-code software among state governments. The team ended up writing a "A cautionary note on no-code and low-code software" in order to encourage readers to be wary of that solution, but we didn't have time to address it at length.

Context: When the FFS Team revised the De-risking Guide, it kept a list of backlog items for possibly addressing in future iterations. As the project lead during close-out, I transferred that list to the Guides repo.

Point of contact on this issue

Amelia Wong

Reproduction steps (if necessary)

No response

Skills Needed

• Any Human
• Design
• Content
• Engineering
• Acquisition
• Product
• Other

Does this need to happen in the next 2 weeks?

• Yes
• No

How much time do you anticipate this work taking?

A few weeks

Acceptance Criteria

This ticket would involve:

• assessing the utility of the content about no-code/low-code
• having conversations with relevant 18F staff (acq; engineers; product) to decide if more should be said
• if no, you're done.
• if yes, figuring out what should be said with relevant 18F staff input
• writing/editing content
• notifying TTS Outreach of changes to see if new content requires going through GSA concurrence
• if needed, going through GSA concurrence
• publishing