Changes

<!--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%">'''DIS - How We Work'''</div>

<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>

=== 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 ===

== 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 10am in the Slack dis_standup channel. Every Wednesday everyone on the team joins a 15 minute scrum starting at 10am via Zoom. A daily status update answers these questions:

* 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 which the development team are the only ones required to attend. This will include constructive conversation around:

* 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

== Definition of Done ==

== Definition of Done ==

[[File:approval-correct-diverse-1282270.jpg|right|20%|four people holding signs with a green check mark over their face]]

[[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

* GitHub Issues

* GitHub Issues

* GitHub Projects

* GitHub Projects

* Trello (DOL and Busrides)

* Trello

[[#top| [ Top ]]]

[[#top| [ Top ]]]

<!--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%">'''SIN - Comment nous travaillons'''</div>

<div style="font-size: 200%">'''Services d'innovation de l'Académie 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>

** 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 dis_standup. Tous les mercredis, tous les membres de l'équipe se joignent à une mêlée de 15 minutes à partir de 10h via Zoom. Une mise à jour quotidienne de l'état d'avancement répond à ces questions :

* 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

* GitHub Issues

* GitHub Issues

* GitHub Projects

* GitHub Projects

* Trello (DOL and Busrides)

* Trello

[[#top| [ Haut de page ]]]

[[#top| [ Haut de page ]]]

</multilang>

</multilang>