Later this month, collective bargaining agreement negotiations are starting for the Economics and Social Science Services group (the EC classification) that I’m a member of. CAPE Local #527 represent! With these negotiations on the horizon, here are some things I’d like to see as part of the conversation: less pay, more time off; a better experience for new public servants; and permanent remote work options & access to modern tools.| sboots.ca
Monday is election day! Back in December 2019, I wrote a set of suggestions for the next GC Chief Information Officer. In the same tradition, here are some suggestions for the next Minister of Digital Government. Digital government work – and public service reform, which is what it ultimately is – isn’t really a newsworthy election topic. It’s near and dear to my heart, though, and I’d love to see more conversations about it from public servants, politicians, and the public alike. W...| sboots.ca
A couple weeks ago, I was able to tune in to FWD50, an annual Canadian digital government conference. One of the themes from the first day onwards was this concept, that government institutions are tech companies without realizing it. Just like “every company is a software company”, public sector institutions need to think differently about how they work, and what leadership they have, in order to be successful today.| sboots.ca
Building digital services and IT systems in a government environment is complicated. The federal government in particular has a lot of rules to navigate, and it’s easy for these to overwhelm people and siphon their time away from designing and building user-friendly software. This short guide was written for an audience that’s used to building digital products in the private sector, to better understand what’s new and different in a government context. Enjoy!| sboots.ca
When I rejoined the federal government in 2016, our team’s desks were around the corner from a large team working on a financial management transformation project – the walls of their area covered in mesmerizing, plotter-printed posters. This was my first introduction to enterprise architecture. If you haven’t worked in government IT, it can be hard to describe, but if you’ve seen business capability models, target state architectures, TOGAF frameworks, or architecture review committe...| sboots.ca
If you’re working on IT or service delivery projects in public sector organizations, I have one very specific rule for you to follow: avoid vendor lock-in. To do that, you should own your data, own your front-end interfaces, own your software source code, and avoid long-term contracts. This post dives into why vendor lock-in is a problem, and how those strategies can help prevent it.| sboots.ca
Lee Berthiaume from the Canadian Press wrote a fascinating article last week, based on an internal Department of National Defence report on IT support. The report describes DND’s IT processes and systems as “out-of-date and poorly supported”, and blamed “onerous levels of oversight”. This is a persistent problem across federal government departments.| sboots.ca
One of the long-held norms of government IT is the perceived benefit of “commercial, off the shelf” software solutions. In government environments, being able to buy ready-to-go software products to meet government IT needs is appealing. In many cases, though, extensive customization requirements means that COTS purchases don’t live up to their promise. They’re marketed as a car and they turn out to be boxes of car parts: lots of time-consuming assembly required. Here’s a rule of th...| sboots.ca
