diff --git a/source/contributor-guide/index.rst b/source/contributor-guide/index.rst
index 8800c32f..ab50ef17 100644
--- a/source/contributor-guide/index.rst
+++ b/source/contributor-guide/index.rst
@@ -1,59 +1,55 @@
 .. _contributor-guide:
 
 =================
 Contributor Guide
 =================
 
 Kolab Groupware development largely follows an iterative and incremental
 agile software development metholodogy also known as `Scrum`_.
 
 In summary, the development process is divided into stages, with different
 teams participating in getting tasks to the next stage of the process.
 
 Kolab Groupware is a collaboration suite consisting of many components,
 each of them separate software development projects, some of them
 dependent on third-party software development projects, and some of them
 separate altogether.
 
 .. _contributor-guide-casual-contributions:
 
 Casual Contributions
 ====================
 
 The following guides are intended for casual contributors and contributions,
 such as a one-time 5-line patch for that one itch to scratch.
 
 .. toctree::
     :maxdepth: 1
 
     translations
     bug-reporting-casual
     documentation/index
     packaging/casual
     feature-requests/index
     testing
 
 .. _contributor-guide-structured-contributions:
 
 Structured Contributions
 ========================
 
 The following guides set you up for regular, structured contributions to Kolab,
 such as continued development and participation in sprints.
 
 .. toctree::
     :maxdepth: 1
 
     getting-started
     setup-development-environment
     peer-review
+    bug-reporting-structured
     docker-containers
     continuous-integration
     packaging
-    bug-reporting-structured
-
-.. toctree::
-    :hidden:
-    :maxdepth: 1
-
     scrum
+
diff --git a/source/contributor-guide/scrum.rst b/source/contributor-guide/scrum.rst
index 5a64a991..64cc562b 100644
--- a/source/contributor-guide/scrum.rst
+++ b/source/contributor-guide/scrum.rst
@@ -1,17 +1,20 @@
 =====
 SCRUM
 =====
 
-Our agile development process is time-boxed with sprints.
+Our agile development process resolves around sprints; time-boxed team efforts.
+
+The following documentation aides in facilitating that process.
 
 .. toctree::
+    :hidden:
     :maxdepth: 1
 
     scrum/sprints
+    scrum/during-the-sprint
 
 .. toctree::
     :maxdepth: 1
 
     scrum/start-of-sprint-checklist
-    scrum/during-the-sprint
     scrum/end-of-sprint-checklist
diff --git a/source/contributor-guide/scrum/end-of-sprint-checklist.rst b/source/contributor-guide/scrum/end-of-sprint-checklist.rst
index 18227327..65d7eb86 100644
--- a/source/contributor-guide/scrum/end-of-sprint-checklist.rst
+++ b/source/contributor-guide/scrum/end-of-sprint-checklist.rst
@@ -1,33 +1,43 @@
 =======================
 End of Sprint Checklist
 =======================
 
-*   The `current sprint`_ must be archived after Friday, 17:00 CET.
+At or near the end of a sprint:
 
-*   The `current sprint`_ must have its additional ``#sprint_current``
+*   The `current sprint`_ must be archived after Friday, 17:00 Europe/Zurich.
+
+*   The `current sprint`_ must have its additional ``sprint_current``
     hashtag removed.
 
 *   Tickets that remain open in the `current sprint`_ must be moved forward
     on to the `next sprint`_.
 
     .. NOTE::
 
         The column for these tickets in the `current sprint`_ should be
         reflected in the `next sprint`_, which requires manual intervention.
 
+        Click the downward facing arrow on each of the relevant columns, and
+        choose *Batch Edit Tasks...*.
+
+        Associate the project tag for the next sprint.
+
 *   The `next sprint`_ becomes the current sprint, and thus:
 
-    *   Remove the additional hashtag ``#sprint_next``,
+    *   Remove the additional hashtag ``sprint_next``,
 
-    *   Add the additional hashtag ``#sprint_curret``.
+    *   Add the additional hashtag ``sprint_current``.
 
 *   The sprint after the next sprint needs to be created;
 
     *   The sprint runs from a Monday 09:00 AM to the following Friday 05:00
         PM.
 
-    *   Use an additional hashtag of ``#sprint_next``.
+    *   Ensure the dates selected for the Monday and the Friday are those for
+        the week number of the sprint (as opposed to the defaults).
+
+    *   Use an additional hashtag of ``sprint_next``.
 
 *   Verify the (now) `current sprint`_ (but actually next week's) actually has
     sufficient tickets in its backlog, because idling is for jet engines with
     reverse thrusters deployed while in flight.