GithubHelp home page GithubHelp logo

canada-ca / micro-acquisition Goto Github PK

View Code? Open in Web Editor NEW
7.0 7.0 6.0 1.75 MB

Micro-acquisition Pilot - Pilote Micro-acquisition

Home Page: http://micro-acquisition.alpha.canada.ca/

License: MIT License

HTML 96.74% CSS 2.95% Ruby 0.31%

micro-acquisition's Introduction

(Français)

Micro-acquisition pilot

The Micro-acquisition pilot ran from June 2021 to May 2022. It was led by Employment and Social Development Canada (ESDC) in a partnership between the Innovation, Information and Technology Branch (IITB) and the Chief Financial Officer Branch (CFOB).

Driven by the results of the red tape reduction report, the Gartner Procurement 2020 report, and the knowledge that while Digital Standards require open first working in the open by default, very little code developed in ESDC was being licensed as open source and shared openly, we felt there was an opportunity to use procurement as a lever.

We also felt strongly that there is a lot of coding talent that remains untapped by the Federal Public Service and that by simplifying low dollar value procurement of code, we could not only increase access to that talent but enable distribution of GC contract dollars to those who might normally face barriers.

We worked to understand those barriers and smash them along the way – can we pay for code using PayPal to get money into coders hands fast and not require them to wait 30 days or have a point of sale system? Heck yes we can!

We also feel really proud and glad of the partnership forged between IITB and CFOB as part of this pilot proving not only that we can but that we must work together across branches when designing any type of service or system.

Ultimately this pilot didn’t meet many of its target success metrics. We thought we would do 10 procurements via Micro-Acquisition. In the end we only posted one opportunity and while a supplier was selected, the opportunity was terminated for non-delivery and no payment was made.

Change initiatives are hard. We faced a number of challenges finding clients who had the need to procure small chunks of coding work at ESDC, we didn't put enough effort into change management and faced push back from ESDC union reps when they learned about it midway through the pilot.

But that is not to say this wasn’t a worthwhile effort. The lessons learned from experiments like this are of equal value to meeting success metrics. We learned a lot over the course of this pilot.

To learn more, read our closeout blog post and report. We have also saved several artifacts to this repo for others to re-use including the business case, our processes, client user guide etc.

Micro-acquisition website

When the website was live it was located here: https://micro-acquisition.alpha.canada.ca/en/index.html

Repo status

This repository is no longer maintained.

License

Unless otherwise noted, the source code of this project is covered under Crown Copyright, Government of Canada, and is distributed under the MIT License.

The Canada wordmark and related graphics associated with this distribution are protected under trademark law and copyright law. No permission is granted to use them outside the parameters of the Government of Canada's corporate identity program. For more information, see Federal identity requirements.


Le pilote de micro-acquisition

Le Projet pilote sur la microacquisition s’est déroulé de juin 2021 à mai 2022. EDSC l’a dirigé dans le cadre d’un partenariat entre la Direction générale de l’innovation, de l’information et de la technologie (DGIIT) et la Direction générale de la Dirigeante principale des finances (DGDPF).

Compte tenu des résultats du Rapport sur la réduction de la paperasse (en anglais), du rapport Gartner sur l’approvisionnement paru en 2020 et du fait que les normes numériques nécessitent en premier lieu le travail en mode ouvert par défaut, très peu de codes élaborés à EDSC étaient autorisés en vertu d’une licence de source ouverte et échangés ouvertement; nous estimions donc qu’il y avait là une occasion de recourir à l’approvisionnement comme levier.

Nous étions également convaincus qu’il y a une abondance de talents en codage qui demeurent inexploités par la fonction publique fédérale et que la simplification de l’acquisition de codes de faible valeur nous donnerait un accès élargi à ces talents, tout en permettant la répartition des fonds contractuels du GC à ceux qui risquent habituellement de se buter à des obstacles.

Nous nous sommes efforcés de comprendre ces obstacles et de les surmonter en cours de route : pouvons-nous payer un code à l’aide de PayPal pour verser rapidement les fonds aux codeurs sans les contraindre à attendre 30 jours ou à recourir à un système de point de vente? Certainement que nous le pouvons!

De plus, nous tirons fierté et satisfaction du partenariat établi entre la DGIIT et la DGDPF dans le cadre de ce projet pilote, ce qui montre que la collaboration entre directions générales à la conception des services ou systèmes, quels qu’ils soient, est possible, mais surtout nécessaire.

Au bout du compte, de nombreux paramètres ciblés de réussite du projet pilote n’ont pas été atteints. Nous pensions pouvoir procéder à 10 approvisionnements par microacquisition. Or, nous n’avons affiché qu’une occasion et, bien qu’un fournisseur ait été sélectionné, celle-ci a été résiliée pour cause de non-livraison et aucun paiement n’a été effectué.

Les initiatives porteuses de changement sont laborieuses. Nous avons fait face à plusieurs obstacles lorsqu’il a fallu trouver des clients qui avaient besoin d’un travail de codage par petits lots à EDSC. Nous n’avons pas déployé suffisamment d'efforts dans la gestion du changement. Nous nous sommes heurtés aux réticences des représentants syndicaux d’EDSC lorsqu’ils ont pris connaissance du pilote à mi-chemin.

Cela dit, il ne faudrait pas en déduire qu’une telle intervention n’en valait pas la peine. Bien que nous n'ayons pas trouvé de clients pour le micro-procurement de code à l'ESDC, nous avons reçu un certain nombre de demandes d'autres ministères, ce qui nous fait penser que cette initiative pourrait être couronnée de succès ailleurs.

En fin de compte, les leçons tirées de telles expériences valent tout autant que l’atteinte des paramètres de réussite. Durant le Projet pilote, nous avons beaucoup appris. Pour en savoir plus, lisez notre article de blog et notre rapport de clôture. Nous avons également sauvegardé plusieurs documents dans ce dépôt afin que d'autres puissent les réutiliser, notamment l'analyse de rentabilité, nos processus, le guide de l'utilisateur, etc.

Site Web micro-acquisition

Lorsque le site web était en ligne, il était situé ici : https://micro-acquisition.alpha.canada.ca/fr/index.html

Quel est ce projet?

Voir https://sara-sabr.github.io/ITStrategy/pilote-de-micro-acquisition.html

Statut du repo

Ce dépôt n'est plus maintenu.

Licence

Sauf indication contraire, le code source de ce projet est protégé par le droit d'auteur de la Couronne du gouvernement du Canada et distribué sous la licence MIT.

Le mot-symbole « Canada » et les éléments graphiques connexes liés à cette distribution sont protégés en vertu des lois portant sur les marques de commerce et le droit d'auteur. Aucune autorisation n'est accordée pour leur utilisation à l'extérieur des paramètres du programme de coordination de l'image de marque du gouvernement du Canada. Pour obtenir davantage de renseignements à ce sujet, veuillez consulter les Exigences pour l'image de marque.

micro-acquisition's People

Contributors

dependabot[bot] avatar elminaiusifova avatar nschonni avatar rachelmuston avatar smellems avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

micro-acquisition's Issues

change the closing date format to long form?

Currently the closing date is in Y-m-d format. But will users get confused if a date is 2021-05-07? Will they know that this is May 7 and not July 5? jobs.gc.ca uses long date format eg. "Closing date: 7 May 2021 - 23:59, Pacific Time

Update header.html in _includes

Adjust text in the blue banner at the top of each page as follows:

Current text: "This is website is part of a pilot and ......"

New text: "This website is part of a pilot and ......"

Supplier guide

  • add text about "if you are unsuccessful, you can request to be debriefed as to why by contacting [email protected]"
  • add text about "you do not need to tell us every single bit of experience you have for this skill...you are not being graded... this is pass or fail. One piece of experience is a pass, 10 pieces of experience is a pass" (fix the wording)
  • Adjust wording around the use of the template invoice
  • Add text about "If you forget to include information about yourself and the eligibility criteria you will be given the opportunity to provide this (you wont be automatically failed), if you forget to include something for one of the evaluation criteria you cannot revise after the deadline.
  • Add text "once you have signed the terms and conditions you will be provided with client information
  • Add text about when supplier can start work..make sure to check the details (Leigh had wording for this)
  • Add text about if code is not immediately accepted, client will work with supplier....try to get your code in before the deadline to allow for this
  • Add text about "status changes to closed once the deadline to apply has passed"

Add text to the Client User Guide - ESDC only

Adjust the first paragraph as follows:
Current:
"First, thank you for considering being part of this pilot and enabling small businesses and freelancers across the country to access GC contract dollars. We think you will find some fantastic talent!"
Change to:
"To be a client of this pilot you must be an ESDC or Service Canada employee.
Thank you for considering being part of this pilot and enabling small businesses and freelancers across the country to access GC contract dollars. We think you will find some fantastic talent!"

Add hover-over function to hyperlink

Opportunity page
The hyperlink on the header of the opportunity is not clear. Looks static and not clickable. Add hover-over function to each

Adjust text in Supplier Guide re: evaluation criteria

Add the following as a bullet to the 'Ready to Apply?' section "the following text "I affirm that <fill in the blank with either: 1. I am Canadian and/or First Nations, Métis, Inuit or 2. I have all the relevant work permits to work in Canada>

In the 'After applying' section replace this text: "If multiple suppliers pass the evaluation" with "If multiple suppliers pass the evaluation criteria"

How this works page

-separate how this works for supplier vs. how this works for client (include links to guides from here)

Fix typos

Client User guide:
Step 2: “If demand is greater (that) than this we might not be....”

Client guidelines.

Step 8
“Once the code is accepted, the supplier sends (and) an invoice, and the supplier is paid by credit card.”

Step 9.
Remove div.

Add a link to the Terms and Conditions page to the Supplier user guide

Rename the Terms page to not confuse users with the canada.ca terms and conditions link in the footer.
change the filename from terms.html and termes.html to IP_form.html and forme_PI.html (actually verify the translation before making that change).

Add text as follows in the 'After Applying' section:
Current:
You will be advised via email if you have (or have not) been selected.

Change to:
You will be advised via email if you have (or have not) been selected. If you have been selected you will be asked to sign this Intellectual property form.

Change the closing date for all opportunities to 23.59 Eastern Time

change the times for the closing_date and delivery_date each of the English and French opportunities.
E.g. a closing_date value of: 2020-10-20T23:59:59-07:00 would change to 2020-10-20T23:59:59-05:00 (I think? Is that right @smellems?)

Also the yml file needs to change in data
Under 'Opportunities' add:
easternTime:
en: Eastern time
fr: heure du ?

And then the opportunitiesTable.html file will need to be updated. Replace each reference to pacificTime data element to easternTime. e.g.
Current:

{{ post.title }}

{%- if closeXML > nowXML -%}
{{ site.data.i18n.general.opportunities.open[page.lang] }}
{{ site.data.i18n.general.opportunities.closing[page.lang] }}: {{ post.closing_date | date: "%Y-%m-%d %H:%M" }}, {{ site.data.i18n.general.opportunities.pacificTime[page.lang] }} 

New:

{{ post.title }}

{%- if closeXML > nowXML -%}
{{ site.data.i18n.general.opportunities.open[page.lang] }}
{{ site.data.i18n.general.opportunities.closing[page.lang] }}: {{ post.closing_date | date: "%Y-%m-%d %H:%M" }}, {{ site.data.i18n.general.opportunities.easternTime[page.lang] }} 

Update opportunities.html

Remove reference to Talent Cloud

Old text..."....with the Government of Canada include: Buy and Sell, Talent Cloud and Jobs.gc.ca"
New text.."....with the Government of Canada include: Buy and Sell and Jobs.gc.ca"

Add a link to the twitter account

Need to create the twitter accounts.
Write and add some text like "follow to be the first to hear when new opportunities are posted"

Update supplier guide text

Current text "Note that having a credit card does not mean you are able to accept payment by credit card. Learn about how to get set up to accept credit cards using a payment system add a link to some info about this - is there an open source option? and get set up to accept payment via PayPal."

Change to "Learn about how to get set up to accept credit cards using a payment system add a link to some info about this - is there an open source option? and get set up to accept payment via PayPal. Note that simply having a credit card does not mean you are able to accept payment by credit card. "

Set up the twitter bot

  • bot should tweet a bilingual message every time a new opportunity is posted or when an opportunity has been updated.
    (need to create a twitter account and write the generic tweet text)

Create and add the opportunity template

Add a link to this page from the Client User Guide page. The look and feel of the opportunity post page needs to be finalized (or mostly finalized) before the template can be created.

Adjust the supplier guide text

Make changes as follows:
In the Ready to Apply section:

  1. remove the 3 written affirmation bullets and replace with text that says 'by applying to an opportunity, you agree that you can complete the work by the completion date in the opportunity statement and that you agree to be paid by credit card or PayPal.
  2. Remove the bullet that starts with 'a text description of your experience' and replace with 'responses to all of the Evaluation Criteria for the opportunity you are applying for

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.