Difference between revisions of "CSPS Digital Academy Innovation Services - Services d'innovation de l'Académie du numérique de L'ÉFPC/How We Work"
Cory.dignard (talk | contribs) m (added image alt tags for accessibility) |
m (Genevieve.lemieux moved page CSPS Digital Academy Innovation Services - Services d'innovation de l'Académie du numérique de L'ÉFPCSIN/How We Work to [[CSPS Digital Academy Innovation Services - Services d'innovation de l'Académie du numérique...) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
<!--The following line of code hides the page title--> | <!--The following line of code hides the page title--> | ||
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}} | {{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}} | ||
| − | <div style="font-size: 200%">''' | + | <div style="font-size: 200%">'''CSPS Digital Academy, Innovation Services - How We Work'''</div> |
{{DISnavbar}} | {{DISnavbar}} | ||
<div style="font-size: 125%">The way we work is loosely based on the [https://agilemanifesto.org/ Agile Principles] and [https://www.scrumguides.org/ SCRUM framework]. This document will be continually updated based on feedback from the sprint retrospectives.</div> | <div style="font-size: 125%">The way we work is loosely based on the [https://agilemanifesto.org/ Agile Principles] and [https://www.scrumguides.org/ SCRUM framework]. This document will be continually updated based on feedback from the sprint retrospectives.</div> | ||
== Roles/Responsibilities == | == Roles/Responsibilities == | ||
| − | [[File:document-3268750_640.jpg|right|20%| | + | [[File:document-3268750_640.jpg|right|20%|notebook with image of bar graph and second page with icons for people with arrows connecting]] |
=== Product Owner === | === Product Owner === | ||
Each product/project will be assigned a product owner who will be responsible for managing the product backlog, and have final say on the direction of the product. In the absence of a product owner, this role will be fulfilled by the lead developer. | Each product/project will be assigned a product owner who will be responsible for managing the product backlog, and have final say on the direction of the product. In the absence of a product owner, this role will be fulfilled by the lead developer. | ||
| Line 17: | Line 17: | ||
=== Lead Developer === | === Lead Developer === | ||
| − | The person who will have final say on development decisions for the product. | + | The person who will have the final say on development decisions for the product. |
=== Scrum Master === | === Scrum Master === | ||
| Line 27: | Line 27: | ||
== Sprints == | == Sprints == | ||
* Have a defined start and end date lasting 3 weeks, ending on a Friday. When one sprint ends, the next one immediately begins. | * Have a defined start and end date lasting 3 weeks, ending on a Friday. When one sprint ends, the next one immediately begins. | ||
| − | * It begins with a 1 hour sprint planning meeting, which includes all developers, the scrum master and product owner(s). Short planning meetings may be necessary for specific products/projects to make better use of everyone's time. These are the guidelines on amount of effort for unplanned work during a Sprint | + | * It begins with a 1 hour sprint planning meeting, which includes all developers, the scrum master and product owner(s). Short planning meetings may be necessary for specific products/projects to make better use of everyone's time. These are the guidelines on the amount of effort for unplanned work during a Sprint |
** 20% for being humans (admin work, content switching, bathroom breaks, etc) | ** 20% for being humans (admin work, content switching, bathroom breaks, etc) | ||
** 15% for skills development, learning, training and R&D activities | ** 15% for skills development, learning, training and R&D activities | ||
** 15% for special requests | ** 15% for special requests | ||
| − | * Each day of the sprint everyone on the team posts a status update by | + | * Each day of the sprint everyone on the team posts a status update by 10 am in the team's Slack channel. A daily status update answers these questions: |
** What did I work on yesterday | ** What did I work on yesterday | ||
** What am I working on today | ** What am I working on today | ||
** What do I need help with | ** What do I need help with | ||
* At the end of the sprint a 1 hr sprint review will be held. Short review meetings may be necessary for specific products/projects to make better use of everyone's time. The sprint goals will be evaluated against the definition of done. | * At the end of the sprint a 1 hr sprint review will be held. Short review meetings may be necessary for specific products/projects to make better use of everyone's time. The sprint goals will be evaluated against the definition of done. | ||
| − | * A 1 hr retrospective will be held | + | * A 1 hr retrospective will be held where the development team is the only one required to attend. This will include constructive conversation around: |
** What worked this sprint | ** What worked this sprint | ||
** What didn’t work this sprint | ** What didn’t work this sprint | ||
| Line 44: | Line 44: | ||
== Definition of Done == | == Definition of Done == | ||
| − | [[File:approval-correct-diverse-1282270.jpg|right|20%| | + | [[File:approval-correct-diverse-1282270.jpg|right|20%|four people holding signs with a green checkmark over their face]] |
The following list details what defines an increment of work as being done. Depending on the increment of work, some or none of these will need to be completed. Any questions, ask the lead developer assigned to the Product/Project. | The following list details what defines an increment of work as being done. Depending on the increment of work, some or none of these will need to be completed. Any questions, ask the lead developer assigned to the Product/Project. | ||
* Accessibility requirements met | * Accessibility requirements met | ||
| Line 64: | Line 64: | ||
* GitHub Issues | * GitHub Issues | ||
* GitHub Projects | * GitHub Projects | ||
| − | * Trello | + | * Trello |
[[#top| [ Top ]]] | [[#top| [ Top ]]] | ||
| Line 73: | Line 73: | ||
<!--The following line of code hides the page title--> | <!--The following line of code hides the page title--> | ||
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}} | {{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}} | ||
| − | <div style="font-size: 200%">''' | + | <div style="font-size: 200%">'''Services d'innovation de l'Académie du numérique de l'ÉFPC - Comment nous travaillons'''</div> |
{{DISnavbarFR}} | {{DISnavbarFR}} | ||
<div style="font-size: 125%">Notre façon de travailler est vaguement basée sur les principes suivants [https://agilemanifesto.org/iso/fr/manifesto.html Principes Agiles] et [https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-French.pdf SCRUM]. Ce document sera continuellement mis à jour en fonction des rétrospectives du sprint.</div> | <div style="font-size: 125%">Notre façon de travailler est vaguement basée sur les principes suivants [https://agilemanifesto.org/iso/fr/manifesto.html Principes Agiles] et [https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-French.pdf SCRUM]. Ce document sera continuellement mis à jour en fonction des rétrospectives du sprint.</div> | ||
== Rôles/Responsabilités == | == Rôles/Responsabilités == | ||
| − | [[File:document-3268750_640.jpg|right|20%| | + | [[File:document-3268750_640.jpg|right|20%|carnet de notes avec image du diagramme à barres et deuxième page avec icônes pour les personnes avec des flèches de connexion]] |
=== Propriétaire du produit === | === Propriétaire du produit === | ||
Chaque produit/projet se verra attribuer un propriétaire de produit qui sera responsable de la gestion de l'arriéré de produits et aura le dernier mot sur l'orientation du produit. En l'absence d'un propriétaire de produit, ce rôle sera rempli par le développeur principal. | Chaque produit/projet se verra attribuer un propriétaire de produit qui sera responsable de la gestion de l'arriéré de produits et aura le dernier mot sur l'orientation du produit. En l'absence d'un propriétaire de produit, ce rôle sera rempli par le développeur principal. | ||
| Line 100: | Line 100: | ||
** 15% pour les activités de développement des compétences, d'apprentissage, de formation et de R&D | ** 15% pour les activités de développement des compétences, d'apprentissage, de formation et de R&D | ||
** 15% pour les demandes spéciales | ** 15% pour les demandes spéciales | ||
| − | * Chaque jour du sprint, tous les membres de l'équipe publient une mise à jour de leur statut avant 10h dans le canal Slack | + | * Chaque jour du sprint, tous les membres de l'équipe publient une mise à jour de leur statut avant 10h dans le canal Slack de l'équipe. Une mise à jour quotidienne de l'état d'avancement répond à ces questions : |
** Sur quoi j'ai travaillé hier | ** Sur quoi j'ai travaillé hier | ||
** Sur quoi je travaille aujourd'hui | ** Sur quoi je travaille aujourd'hui | ||
| Line 113: | Line 113: | ||
== Définition de Fait == | == Définition de Fait == | ||
| − | [[File:approval-correct-diverse-1282270.jpg|right|20%| | + | [[File:approval-correct-diverse-1282270.jpg|right|20%|quatre personnes tenant des pancartes avec une coche verte sur le visage]] |
La liste suivante décrit en détail ce qui définit un accroissement du travail comme étant effectué. Selon l'augmentation du travail, certains ou aucun d'entre eux n'auront besoin d'être complétés. Si vous avez des questions, posez-les au développeur principal affecté au produit/projet. | La liste suivante décrit en détail ce qui définit un accroissement du travail comme étant effectué. Selon l'augmentation du travail, certains ou aucun d'entre eux n'auront besoin d'être complétés. Si vous avez des questions, posez-les au développeur principal affecté au produit/projet. | ||
* Exigences en matière d'accessibilité satisfaites | * Exigences en matière d'accessibilité satisfaites | ||
| Line 133: | Line 133: | ||
* GitHub Issues | * GitHub Issues | ||
* GitHub Projects | * GitHub Projects | ||
| − | * Trello | + | * Trello |
[[#top| [ Haut de page ]]] | [[#top| [ Haut de page ]]] | ||
</multilang> | </multilang> | ||
Latest revision as of 10:16, 8 January 2020
CSPS Digital Academy, Innovation Services - How We Work
| Home | Our Team | Our Product Development Cycle |
How We Work | Contact Us |
The way we work is loosely based on the Agile Principles and SCRUM framework. This document will be continually updated based on feedback from the sprint retrospectives.
Roles/Responsibilities
Product Owner
Each product/project will be assigned a product owner who will be responsible for managing the product backlog, and have final say on the direction of the product. In the absence of a product owner, this role will be fulfilled by the lead developer.
Development team
This includes anyone with the necessary skill sets to complete an increment of work as part of a sprint. This may include programmers, designers and advisors.
Lead Developer
The person who will have the final say on development decisions for the product.
Scrum Master
This person ensures the various sprint meetings happen and run efficiently. They assist the Product Owner and/or Development team to overcome obstacles during a sprint when asked. They provide mentoring, guidance and training on the Agile Principles and SCRUM framework as required.
Sprints
- Have a defined start and end date lasting 3 weeks, ending on a Friday. When one sprint ends, the next one immediately begins.
- It begins with a 1 hour sprint planning meeting, which includes all developers, the scrum master and product owner(s). Short planning meetings may be necessary for specific products/projects to make better use of everyone's time. These are the guidelines on the amount of effort for unplanned work during a Sprint
- 20% for being humans (admin work, content switching, bathroom breaks, etc)
- 15% for skills development, learning, training and R&D activities
- 15% for special requests
- Each day of the sprint everyone on the team posts a status update by 10 am in the team's Slack channel. A daily status update answers these questions:
- What did I work on yesterday
- What am I working on today
- What do I need help with
- At the end of the sprint a 1 hr sprint review will be held. Short review meetings may be necessary for specific products/projects to make better use of everyone's time. The sprint goals will be evaluated against the definition of done.
- A 1 hr retrospective will be held where the development team is the only one required to attend. This will include constructive conversation around:
- What worked this sprint
- What didn’t work this sprint
- What can be improved during the next sprint
Definition of Done
The following list details what defines an increment of work as being done. Depending on the increment of work, some or none of these will need to be completed. Any questions, ask the lead developer assigned to the Product/Project.
- Accessibility requirements met
- Compatible on required devices
- Well documented code
- Minimum required documents
- Support plan in place
- Automated testing passed
- Integration review
- Code review
- Official Language (OL) compliance
- Corporate branding compliance
Tools we will use to manage our work
These are the tools we will use to manage our product and sprint backlogs, for release and/or sprint purposes, and daily tasking.
- GitHub Issues
- GitHub Projects
- Trello