<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Matthew Garvey on Medium]]></title>
        <description><![CDATA[Stories by Matthew Garvey on Medium]]></description>
        <link>https://medium.com/@matthewgarvey?source=rss-f2bc83d48db5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C53eel9Mugyb5k-Yhda-4Q.png</url>
            <title>Stories by Matthew Garvey on Medium</title>
            <link>https://medium.com/@matthewgarvey?source=rss-f2bc83d48db5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:08:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@matthewgarvey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Operate at the Speed of Business with B3’s Rapid Low Code/No Code Engagement Model]]></title>
            <link>https://medium.com/operate-at-the-speed-of-business-with-b3s-rapid/operate-at-the-speed-of-business-with-b3s-rapid-low-code-no-code-engagement-model-e6390f917181?source=rss-f2bc83d48db5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6390f917181</guid>
            <dc:creator><![CDATA[Matthew Garvey]]></dc:creator>
            <pubDate>Tue, 29 Mar 2022 15:56:25 GMT</pubDate>
            <atom:updated>2022-03-29T17:03:22.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*9Fjwt-oZ6F6mv9wq6dq76g.jpeg" /></figure><p><strong>Summary</strong>: For the business to operate at cloud speed, meaning fast, agile and secure, it is important to create a flexible, practical, and cooperative engagement model with IT to acquire new SaaS and PaaS capabilities</p><p>Government IT processes tend to be both weighty and designed for distrust. When spending billions of dollars on an enterprise-wide, electronic health record system, it makes sense to spend months accounting for every possible contingency. When buying a SaaS product on the open market, 150-page procurement checklists, although well-intentioned, drive government employees to simply do it themselves. Though more efficient from a business perspective, “doing it themselves” translates to untold shadow IT projects with shared or transferred files, including removable media, email accounts, and consumer cloud accounts creating a very real security risk.</p><p>From the IT perspective, approval processes for software, applications, and devices exist for a reason, they keep their agencies safe and compliant. To the business, they are there to get a job done and if they find a low-cost or free application that would increase their productivity, why not take advantage of it? To them, government IT procurement is unreasonably long and ineffective. Also, because it is not their job to consider risk and compliance, the business isn’t as focused on the risk in using the same applications or cloud accounts that seemed secure enough for their personal lives.</p><p>Since the most prevalent forms of shadow IT are SaaS and PaaS there is an opportunity to leverage the unique aspects of these technologies to help bridge the gap. The key is to pinpoint the optimal level of business autonomy and IT oversight.</p><p><strong>Simplified processes and automation allow discovery and governance to operate at cloud speed</strong></p><p>To operate at cloud speed, it is important to create a flexible, practical, and cooperative model to acquire appropriate new SaaS and PaaS capabilities and steer inappropriate ones to better solutions. B3’s Rapid Engagement Model, outlined below, establishes a repeatable method for business and IT to agree on ease of access, acceptable use, and continuous monitoring.</p><p>1. <strong>Proactively create a critical mass of turnkey SaaS and PaaS offerings</strong>: Start by identifying enterprise-level functional categories that most closely reflect the mission and operations of the agency (i.e., project management, telehealth, research, training, etc.) Once the functional categories are identified, leverage existing research on best of breed SaaS and PaaS products (e.g., Gartner Magic Quadrant) as it relates to these categories and create a short list of 3–4 for each category. Since most agencies have an existing set of cloud products in production already, include them in the list if they fit the same criteria used to vet the others. After compiling short lists for each functional category, validate whether the product is either FedRAMP authorized or in process by using the FedRAMP marketplace (<a href="https://marketplace.fedramp.gov/#!/products">https://marketplace.fedramp.gov/#!/products</a>). If the product is authorized or in process keep it on the list, if not, strike it since the approval process is consuming. Lastly, engage the vendors of each product, explaining the goal of creating turnkey access for agency employees to their respective products (the product POC can be found by drilling down on the product on the FedRAMP website).</p><p>2. <strong>Design and implement a lightweight engagement and governance model</strong>: At a minimum, four basic guidelines should be established to serve as the model’s baseline:</p><p>1) <strong><em>Collaboratively create and memorialize the governance model</em></strong>: The business and IT should collaborate to establish a foundational directive on acceptable uses for SaaS and PaaS and how they should be controlled. Begin with identifying a list of products that are preapproved for specific uses, or forms of data without additional assessment. Once complete, define the variable levels of risk assessment rigor to be applied to the remainder, in which the level of analysis is proportional to the data or use-case criticality. This risk-based and pragmatic approach ensures that strategically important use cases are well-analyzed, without unnecessarily reducing the ability to quickly deploy.</p><p>2) <strong><em>Make sure the SaaS and PaaS request process is simple and intuitive</em></strong>: Business stakeholders should engage IT with SaaS and PaaS requests through a simple and efficient process. Ideally, create a web-based catalog of the product offerings from step 1, outlining the functionality, appropriate types of use case and procurement path for each product in plain English. An example of what B3 created for the Department of Veterans Affairs can be found at <a href="https://www.oit.va.gov/marketplace/">https://www.oit.va.gov/marketplace/</a></p><p>3) <strong><em>Define stakeholder roles and responsibilities across the product lifecycle</em></strong>: Since most roles and responsibilities persist across all SaaS and PaaS products, create a template that defines the common controls and functions, and if necessary, tailor it at the product level. Key responsibilities to include in the template include usage monitoring, policy enforcement, customer support not provided by the vendor, and IT administrative functions (i.e., user provisioning, license management, etc.)</p><p>4) <strong><em>Asssess risk and priority when triaging customer requests</em></strong>: Since there is significant variety in usage, capabilities and security controls with SaaS and PaaS, a single approach to triaging customer requests does not work. A recommended action to automate and simplify the assessment of risk and priority of each requst is to includes a self-service questionnaire that provides an initial risk score based on the type of data, number of users, need for external access and so on. Low scores can be automatically approved; higher scores require assessment by a security architect and/or approval by a governance team.</p><p>3. <strong>Perform a lean analysis of alternatives where appropriate</strong>: When using SaaS and PaaS to address business challenges, the focus is often on immediate functional requirements, discounting if a given product is the best solution or prone to longer-term issues (i.e., product or company maturity, licensing models, financial stability, etc.) Embedding a technologist in the request triage process to assess technical fit-for-purpose and alternatives as appropriate can protect against unanticipated customization or integration costs, etc. that may lead to a low value or failed implementation.</p><p>4. <strong>Provide consultative support when procuring the product</strong>: Acquisition challenges with cloud-based products can be daunting, even for those specializing in it. Supporting customers throughout the procurement lifecycle is a terrific way to endear them and deepen the partnership. Failure to do can expose the agency to operational and financial risk. Establishing criteria for the customer to easily self-navigate, including having them document accepted risks, assumptions, business benefits, mitigating factors and mitigation plans before signing the contract is key.</p><p><strong>Closing thoughts</strong></p><p>Governance, approval, and provisioning processes for SaaS and PaaS that are too slow and ineffective lead directly to shadow IT. Our model has been successfully deployed at the Department of Veterans Affairs since 2017 and currently supports 200+ SaaS and PaaS implementations serving 10M + veterans, employees, contractors, and other constituents. Leveraging this model, agencies can break down the silos and transition IT from the perception of a culture of no and bureaucracy to a partner and enabler while simultaneously unleashing the pent-up value of the business to technology.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6390f917181" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operate-at-the-speed-of-business-with-b3s-rapid/operate-at-the-speed-of-business-with-b3s-rapid-low-code-no-code-engagement-model-e6390f917181">Operate at the Speed of Business with B3’s Rapid Low Code/No Code Engagement Model</a> was originally published in <a href="https://medium.com/operate-at-the-speed-of-business-with-b3s-rapid">Operate at the Speed of Business with B3’s Rapid Low Code/No Code Engagement Model</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Democratize IT Responsibly with Citizen Development]]></title>
            <link>https://medium.com/@matthewgarvey/democratize-it-responsibly-with-citizen-development-a25a2aac74ac?source=rss-f2bc83d48db5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a25a2aac74ac</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[legacy-modernization]]></category>
            <category><![CDATA[citizen-developer]]></category>
            <category><![CDATA[citizen-development]]></category>
            <dc:creator><![CDATA[Matthew Garvey]]></dc:creator>
            <pubDate>Tue, 19 Oct 2021 17:34:55 GMT</pubDate>
            <atom:updated>2021-10-19T17:34:55.093Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*IrG9nbqskGSGnzyhlzlNKQ.jpeg" /></figure><p><strong>Executive Summary</strong></p><p>With telework here to stay, federal agencies are investing into digital solutions to support newly remote workforces, deliver data management and analytics, cybersecurity, and other needs. While federal executives are eager to innovate, reduce technical debt, and improve delivery, the labor market for trained software professionals is as competitive as any point in the last 20 years. Low code/no code application platforms (LC/NC) have emerged as a viable solution, offering a technology environment that lowers the technical barriers to entry. LC/NC empowers non-programmers, referred to as citizen developers, with the ability to experiment with new solutions to improve business efficiency, value, and agility. When agencies empower citizen developers with LC/NC, it frees up coveted engineering talent to tackle the complex enterprise-level obstacles that stand in the way of large-scale modernization.</p><p>Fortunately, the federal workforce outside of traditional IT departments includes a pool of untapped digital skills, capacity, and ambition. These assets can be leveraged as a force multiplier to advance digital transformation, but only if IT can find a way to effectively encourage, enable, and empower broad-based participation from business partners. In most cases, federal IT departments resist ceding solution delivery leadership to their business partners. The result is backlogged requests that cause frustrated internal customers to either miss crucial opportunities or pursue their digital ambitions through shadow IT efforts. While these leaders acknowledge that the traditional approach is unsustainable, the alternative of a decentralized, free-for-all technology environment makes the flawed (but known) approach appear to be the lesser of two evils.</p><p>Instead of ignoring it and risk driving it further into the shadows, federal IT departments should promote responsible citizen development. LC/NC platforms in the hands of a citizen developer can automate tasks (notifications, approvals), workflows (end-to-end processes) and reasoning (analytics, chatbots) but these non-programmers aren’t schooled in how to engineer systems for maximum reuse, address non-functional requirements or adequately comply with federal regulations. Establishing a citizen development-focused Center of Excellence (CoE) that provides training, maintains policies and guidelines and coordinates across existing IT infrastructure can help ensure sustainable behaviors and practices that shorten time to value, ensure acceptable total cost of ownership (TCO) and mitigate risks.</p><p><strong>B3’s Model for a Successful Citizen Development CoE</strong></p><p>An effective CoE empowers citizen developers to create, maintain and deploy automations and applications that support business processes in a secure, resilient, and scalable way. Outlined below, B3’s CoE model is practical by design and importantly, proven. We’ve been leading Citizen Development efforts since 2017, efficiently modernizing entire portfolios while mitigating the very real risks of shadow IT.</p><p>1. <em>Select the right technologies for citizen development</em>: Not every application is right for citizen development. LC/NC are becoming increasingly ubiquitous, but they aren’t created equal when it comes to key aspects for citizen development like UI simplicity and ease of configuration. There’s also robust robotic process automation (RPA) tools and intelligent business process management suites (iBMPS) that can be successfully leveraged by citizen developers. It’s about striking the right balance between areas that IT needs to control and where the business would benefit from more freedom and flexibility.</p><p>2. <em>Define the model and staff the CoE organization:</em> Centralized accountability for citizen development within the IT department is critical. The CoE should provide governance, support, and quality control. This CoE should be sufficiently staffed so that it can own the governance strategy and be responsible for monitoring and ensuring that all citizen development activities follow the regulations of other parts of the organization, and integrations with other systems in use.</p><p>3. <em>Develop a targeted training program</em>: The training program should introduce citizen developers to basic concepts, expectations and how citizen development fits into the agency. The initial training should provide access to agency or vendor training on the platform and include relevant/approved data lists and connected systems. Continuous training thereafter will ensure the ecosystem is receiving the support that they need to be successful.</p><p>4. <em>Assume responsibility for managing the platforms and apps that Citizen Developers use/build</em>: The CoE must assume responsibility for maintaining/updating the LC/NC platforms, applications, systems, etc. that citizen developers use to build, independently and in coordination with the organization’s existing IT portfolio. Without centralized ownership, shadow IT projects will continue to perpetuate and applications in production will experience persistent sustainment issues.</p><p><strong>Conclusion</strong></p><p>Today, there is an explosion of use cases across every federal agency along with the potential to unlock substantial value. Responsible citizen development means moving past supply and demand constraints, erratic budget cycles and adversity to risk, unleashing this pent-up value and truly democratizing IT. Our model’s key to success is a thorough, yet flexible CoE that balances business empowerment with clear and strategic governance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a25a2aac74ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>