You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 21, 2020. It is now read-only.
Make a project tracker applying core project management streams as events | Développer un système de suivi des projets qui intègre les principaux volets de la gestion de projets au titre d’événements (« Event sourcing »)
#1
Fixed Price: $9,999.00 Closing Date: Monday, April 23, 2018
Opportunity Description
The Problem: Projects are reviewed upon completion. Independent of outcome (successful or not successful) this review is critical to continuously learn and improve. These reviews are currently conducted through a series of data collection exercises that are both quantitative and qualitative, varying in collection formats (in person interviews, system querying, document reviews, etc.). Is it possible to design a system to collect and manage project transactional data that can be used to determine (in post) the probable point of failure, in respect to time, by examining every critical transaction that occurs throughout the lifecycle of a project?
The Business: Professional institutions have developed extensive practices to apply project management standards within organizations. Treasury Board of Canada Secretariat has adopted these approaches to create guidelines for Government of Canada departments and agencies to leverage accordingly by assessing organizational project management capacity and risk levels.
The business of managing projects is well documented.
The domain of project management is common across all business platforms. The following is a simplified overview of an operational business process for managing projects:
Create a project
Write a project proposal
Obtain approval to move forward with project
Write a project plan
Begin capturing requirements/user stories
Build/buy solution
Test
Repeat steps 4-7 as needed
Train
Deploy
Review project
Close project
Within each of these 12 steps, there are a number of transactions that occur to complete the project.
Acceptance Criteria
Build a model of the domain;
Build an event sourced system that implements the domain model;
Build a UI that receives events (from event store) and issues commands to the main system through API;
Documentation of the domain and systems
How to Apply
Go to the Opportunity Page, click the Apply button above and submit your proposal by 17:00 PST on Monday, April 23, 2018.
We plan to assign this opportunity by Monday, May 14, 2018 with work to start on Tuesday, May 15, 2018.
Proposal Evaluation Criteria
Confirmation that you are eligible to work in Canada
Confirmation that you can meet all of the Acceptance Criteria by (end of day) May 28, 2018
Your Approach for meeting each of the Acceptance Criteria (60 points)
Your Experience working with relevant agile projects and work with Event Store - please provide links to your previous work on GitHub or other repositories (40 points)
Prix fixe : 9 999,00 $ Date de clôture : le lundi 23 avril 2018
Description de l'opportunité
Problème: Une fois terminés, les projets sont examinés, et peu importe leur issue (positive ou non), les examens sont d’une importance cruciale pour approfondir nos connaissances et toujours faire mieux. Pour le moment, on procède à ces examens en faisant plusieurs collectes de données à la fois quantitatives et qualitatives, selon divers formats de collecte (rencontres en personne, recherches dans le système, examens de documents, etc.). Or, serait-il possible de concevoir un système de collecte et de gestion de données que l’on pourrait utiliser pour cerner les points de défaillances probables (à venir), en fonction du temps, en examinant chaque transaction critique exécutée tout au long du cycle de vie d’un projet?
Milieu opérationnel: Des institutions professionnelles ont élaboré de nombreuses pratiques visant à appliquer les normes de gestion de projet dans les organisations. Le Secrétariat du Conseil du Trésor a adopté ces approches pour établir des lignes directrices à l’intention des ministères et des agences du gouvernement fédéral à utiliser selon les besoins, en évaluant la capacité de gestion de projets et les niveaux de risques.
Les processus de gestion de projets sont bien documentés.
Le domaine qui englobe la gestion des projets est commun à toutes les plates-formes professionnelles. Voici une vue d’ensemble simplifiée d’un processus opérationnel de gestion de projets en entreprise :
Conception du projet
Formulation de la proposition
Approbation de la proposition
Élaboration du plan
Saisie des exigences et des récits des utilisateurs
Élaboration ou adoption de solutions
Essai
Répétition des étapes 4-7, au besoin
Formation
Déploiement
Examen du projet
Clôture du projet
La réalisation de chacune des 12 étapes requiert plusieurs transactions.
Critères d'acceptation
Concevoir un modèle de domaine.
Concevoir un système à approvisionnement en événements (« Event sourcing ») qui met en œuvre le modèle de domaine.
Développer une interface pour recevoir les événements (provenant du magasin d’événements) et envoyer les commandes au système principal par l’interface de programmation.
Produire la documentation portant sur le domaine et les systèmes.
Comment présenter une proposition
Accédez à la page de possibilité, cliquez sur le bouton Appliquer ci-dessus et soumettez votre proposition avant 17:00 PST sur le lundi 23 avril 2018.
Nous prévoyons d'attribuer cette opportunité par le lundi 14 mai 2018 avec le travail pour commencer le mardi 15 mai 2018.
Critères d'évaluation de la proposition
Votre admissibilité confirmée à travailler au Canada
Votre capacité confirmée à satisfaire aux critères d’acceptation avant le 28 mai 2018
Votre approche pour satisfaire aux critères d’acceptation (60 points)
Votre expérience du travail sur des projets complexes pertinents et avec des magasins d’événements –ajoutez des liens vers vos réalisations sur GitHub ou d’autres dépôts (40 points)
The text was updated successfully, but these errors were encountered:
This is an impossible request. There's no way that anyone could implement this system within the time constraints.
I've implemented several event-sourced, change-radiating single page web applications in my 20 year career. This is easily a multi-month project. Items 2-3 alone would each take 2-3 months for a highly skilled developer. There's no way a single developer could accomplish this within the specified time frame (11 days).
Having staffed projects like this before, I'd recommend a team of 6 developers to even come close to implementing this project on time. Even so, if I were to put such a team on this project, there's NO WAY that I could pay them for 9999$. I have access to a decently sized pool of offshore developers with significantly lower salary expectations than Canadians. Even with those lower costs, I could only afford to staff a maximum of 2 on the project for a single month.
Clearly, based on the fixed price, this is intended to be a project for a single developer. That's the only way to make this remotely affordable for the implementor. As I said above, I know for a fact that it's impossible for a single developer to complete this project within the constraints. Therefore, I must assume that it is intended that the project be an integration exercise on the implementing side. You hope to find free software that satisfies most of the constraints. Assuming that there exists free software for the backend portion of the project that meets the technical requirements (event sourced with a domain-driven data model), you are still left to implement the UI expected in (3) and the domain model expected in (1). Even this reduced set of implementation tasks cannot be completed in 11 days. You might receive a rough prototype, but nothing production-ready.
Summary: I think no one has responded to this procurement request because:
it's clearly impossible to complete on time, within budget
there is not much depth to the requirements, therefore high risk on the implementor's side (for very little in return)
I design and staff projects like this all of the time. If you'd like help getting a true measure of this project's scope, let me know.
Me, I'd need a profit of $10,000 just to be able to afford the 3-4 days required to write this proposal.
Afterall, I won't get every single contract, so in order to be able to afford to deal with the uncertainty of writing proposals, one has to make 20% on any project that one does get.
Since this is government, even if the project was doable in the allotted time, the government would change the criteria half-way through (cf. Pheonix) rendering the project impossible to complete, leaving the contractor in a position where they either go out of business, or they deliver a project that can't work (cf. Pheonix).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Fixed Price: $9,999.00
Closing Date: Monday, April 23, 2018
Opportunity Description
The Problem: Projects are reviewed upon completion. Independent of outcome (successful or not successful) this review is critical to continuously learn and improve. These reviews are currently conducted through a series of data collection exercises that are both quantitative and qualitative, varying in collection formats (in person interviews, system querying, document reviews, etc.). Is it possible to design a system to collect and manage project transactional data that can be used to determine (in post) the probable point of failure, in respect to time, by examining every critical transaction that occurs throughout the lifecycle of a project?
The Business: Professional institutions have developed extensive practices to apply project management standards within organizations. Treasury Board of Canada Secretariat has adopted these approaches to create guidelines for Government of Canada departments and agencies to leverage accordingly by assessing organizational project management capacity and risk levels.
The business of managing projects is well documented.
The domain of project management is common across all business platforms. The following is a simplified overview of an operational business process for managing projects:
Within each of these 12 steps, there are a number of transactions that occur to complete the project.
Acceptance Criteria
How to Apply
Go to the Opportunity Page, click the Apply button above and submit your proposal by 17:00 PST on Monday, April 23, 2018.
We plan to assign this opportunity by Monday, May 14, 2018 with work to start on Tuesday, May 15, 2018.
Proposal Evaluation Criteria
Prix fixe : 9 999,00 $
Date de clôture : le lundi 23 avril 2018
Description de l'opportunité
Problème: Une fois terminés, les projets sont examinés, et peu importe leur issue (positive ou non), les examens sont d’une importance cruciale pour approfondir nos connaissances et toujours faire mieux. Pour le moment, on procède à ces examens en faisant plusieurs collectes de données à la fois quantitatives et qualitatives, selon divers formats de collecte (rencontres en personne, recherches dans le système, examens de documents, etc.). Or, serait-il possible de concevoir un système de collecte et de gestion de données que l’on pourrait utiliser pour cerner les points de défaillances probables (à venir), en fonction du temps, en examinant chaque transaction critique exécutée tout au long du cycle de vie d’un projet?
Milieu opérationnel: Des institutions professionnelles ont élaboré de nombreuses pratiques visant à appliquer les normes de gestion de projet dans les organisations. Le Secrétariat du Conseil du Trésor a adopté ces approches pour établir des lignes directrices à l’intention des ministères et des agences du gouvernement fédéral à utiliser selon les besoins, en évaluant la capacité de gestion de projets et les niveaux de risques.
Les processus de gestion de projets sont bien documentés.
Le domaine qui englobe la gestion des projets est commun à toutes les plates-formes professionnelles. Voici une vue d’ensemble simplifiée d’un processus opérationnel de gestion de projets en entreprise :
La réalisation de chacune des 12 étapes requiert plusieurs transactions.
Critères d'acceptation
Comment présenter une proposition
Accédez à la page de possibilité, cliquez sur le bouton Appliquer ci-dessus et soumettez votre proposition avant 17:00 PST sur le lundi 23 avril 2018.
Nous prévoyons d'attribuer cette opportunité par le lundi 14 mai 2018 avec le travail pour commencer le mardi 15 mai 2018.
Critères d'évaluation de la proposition
The text was updated successfully, but these errors were encountered: