playbook VS open-case-filing-system

I'm sure there might be because several years ago the U.S. created the U.S. Digital Service with the premise being recruiting professionals (yeah mostly from corporate but not only) to spend time in the government and help modernize many of its aspects and offerings...for the benefit of the citizens, etc. Here's one example of their playbooks: https://playbook.cio.gov/

...While not exactly like the Singapore page linked in this post, alot of the intent with the USDS - as i understand it - is alos to be quite transparent with the hope of any other government agencies/orgs such as state/province level, city level, etc. benefiting from their ideas and hopefully broadening the benefit at all levels. Here is the main site, but of course (as the above playbook link denotes), there are plenty of other related sites that might help better answer your question: https://www.usds.gov/mission

https://playbook.cio.gov/#play4

Do [lawmakers and aides] make good "Product Owners", stakeholders, app feedback capability utilizers? GitLab has Service Desk: you can email into the service desk email without having an account as necessary to create and follow up on [software] issues in GitHub/BitBucket/GitLab/Gitea project management sytems.

> That's changing at the federal level. They know they've got a problem. Why shouldn't federal software be as easy to use as the best web software? If you've ever tried to use it you will quickly learn that isn't the case.

"PLAY 3: Make it simple and intuitive" https://playbook.cio.gov/#play3

> Some sites will only work with IE and no other browser. Developers in two years can make a huge difference for making the government be more agile and operate better.

US Web Design Standards

> I've worked with state government as a volunteer advisor. They're still developing everything with waterfall. Only contracting out to big firms, even if it's a small project. Lawmakers and aides sit in a room and write down what is to be done.

The US Digital Services Playbook likely needs few modifications for use at state and local levels? https://github.com/usds/playbook#readme

"PLAY 1: Understand what people need" https://playbook.cio.gov/#play1

"PLAY 4: Build the service using agile and iterative practices"

There is no reason this app should NOT be opensourced. They should be defaulting to open per Play 13 of the US Digital Service handbook > https://playbook.cio.gov/#play13.

Not only that, but the entire process is fairly transparent. For instance the code for this website is available here

https://github.com/usds/playbook

Along with full commit history.

I’m a software engineer that works for the federal government, specifically the United States District Court. I do believe in the mission of making justice for all. There is a myth perpetrated by those in the private sector that government is behind, slow, and not capable. I assure you we are using Rust, Clojure, and Next.jj’s in our projects too. We just aren’t as loud because of privacy concerns. Federal employees operate just like startups. The federal court software factory in the judiciary is the equivalent to 18F. I’m the co-founder of FCSF and we are just getting started. Open source and government are a match made in heaven and I look forward to your contributions to our projects. We code for the people.

https://github.com/federal-courts-software-factory/open-case...