102
edits
Changes
Jump to navigation
Jump to search
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 13:01, 24 July 2019
, 13:01, 24 July 2019draft content
<multilang>
@en|__NOTOC__
__NOEDITSECTION__
{{underconstruction}}
<!--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>}}
<div style="font-size: 200%">'''DIS - How We Work'''</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>
<br>
{{DISnavbar}}
== 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 final say on development decisions for the product.
=== 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.
== 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 2 - 4 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
** 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 includes a 15 minute scrum starting at 10am via Zoom. The development team are the only ones required to attend the daily scrum. If people aren’t able to attend, they will post a summary in Slack prior to 10am. A daily scrum 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 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 didn’t work this sprint
What can be improved during the next sprint
<!-- French Starts here -->
@fr|__NOTOC__
__NOEDITSECTION__
{{underconstruction}}
<!--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>}}
Services d'Innovation Numérique (SIN)
</multilang>
@en|__NOTOC__
__NOEDITSECTION__
{{underconstruction}}
<!--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>}}
<div style="font-size: 200%">'''DIS - How We Work'''</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>
<br>
{{DISnavbar}}
== 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 final say on development decisions for the product.
=== 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.
== 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 2 - 4 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
** 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 includes a 15 minute scrum starting at 10am via Zoom. The development team are the only ones required to attend the daily scrum. If people aren’t able to attend, they will post a summary in Slack prior to 10am. A daily scrum 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 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 didn’t work this sprint
What can be improved during the next sprint
<!-- French Starts here -->
@fr|__NOTOC__
__NOEDITSECTION__
{{underconstruction}}
<!--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>}}
Services d'Innovation Numérique (SIN)
</multilang>
