Paul Craig recently wrote a blog post on the massive amount of compliance documentation his team produced to launch a small public website in a Canadian government department. It’s a must-read lens into the current shape of public sector tech work in Canada. We have a public service executive class that isn’t equipped to lead technology initiatives. We’ve got widespread adoption of digital government words, but not digital government implementation. And we’ve got a political class tha...| sboots.ca
Delivering good services to the public, in the internet era, depends on designing and developing good software. Although there are about 17,000 IT professionals in the Canadian government (and an estimated 60,000 contractors and consultants), there are very few senior developers within the public service. Here are a few reasons why.| sboots.ca
“Agile” gets mentioned enough in digital government work that can sometimes seem like it applies to everything: is anything not agile? But there’s a deeper meaning behind it that’s easy to miss: adding agile practices without removing established, “waterfall” processes that slow a team down is a recipe for frustration. Being agile means choosing one approach over another, and deliberately prioritizing what you spend your time on.| sboots.ca
A strategy for agile teams in enterprise orgs.| federal-field-notes.ca
All carts, no horses.| federal-field-notes.ca
When you can’t see the forest or the trees.| federal-field-notes.ca
Last week, Kathryn May published an article in Policy Options titled “Speaking truth to power discouraged in public service”, based on a recent report from the Institute on Governance. It lines up with a consistent observation: public servants are frequently unable to provide fearless advice to the more senior public servants above them, let alone to political leaders and ministers several steps further removed. That has important consequences for the effectiveness of our public service w...| sboots.ca
In early 2022, the President of Shared Services Canada (SSC) announced that he was retiring. In what has accidentally become a tradition, below are some suggestions for the next president to take on the role: start moving to zero trust networking and away from perimeter defence; enable the rapid, secure adoption of third-party software-as-a-service tools at scale; and incrementally make SSC services optional instead of mandatory.| sboots.ca
Leah Lockhart captures in a profound way why government systems and software tend to be so bad. Bad government software – the user-hostile, complicated, enterprise systems that public servants everywhere are accustomed to – trains public servants to have low expectations of government software systems. Then, as they progress over time into leadership roles, they make IT decisions based on the low expectations they were trained to expect.| sboots.ca
If you work in government IT, you’ve probably heard this before: “We’ve got one standard database product.” “We’ve standardized on this programming language.” “This software is our standard for case management systems,” and so on. There are a number of important downsides, though, to standardization efforts: one size all ends up fitting nothing well, they act as a placeholder for more informed technical discussions, and they end up being a barrier to continual change.| sboots.ca