102
edits
Changes
Jump to navigation
Jump to search
Line 12:
Line 12: − + Line 24:
Line 24: + + + Line 34:
Line 37: − + − + − + − + − + − + + + + + + + + + + + + + + + + + + + + + + + + + +
CSPS Digital Academy Innovation Services - Services d'innovation de l'Académie du numérique de L'ÉFPC/How We Work (view source)
Revision as of 07:52, 25 July 2019
, 07:52, 25 July 2019Final draft
== Roles/Responsibilities ==
== Roles/Responsibilities ==
[[File:document-3268750_640.jpg|right|20%]]
=== 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.
=== Scrum Master ===
=== Scrum Master ===
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.
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.
[[#top| [ Top ]]]
<br clear=all>
== Sprints ==
== Sprints ==
** 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 2 - 4 hr retrospective will be held which the development team are the only ones required to attend. This will include constructive conversation around:
* A 2 - 4 hr retrospective will be held which the development team are the only ones 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
What can be improved during the next sprint
** What can be improved during the next sprint
[[#top| [ Top ]]]
== Definition of Done ==
[[File:approval-correct-diverse-1282270.jpg|right|20%]]
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
[[#top| [ Top ]]]
<br clear=all>
== 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
* Aury to investigate other tools
[[#top| [ Top ]]]
<!-- French Starts here -->
<!-- French Starts here -->
