moved agile planning to worksheet 3

rpi · Feb 1, 2018 · 0d19439510d3c011c6930bfbdb2517b9776c730e · 0d19439
1 parent ddfd4e4
commit 0d19439510d3c011c6930bfbdb2517b9776c730e
Show file tree

Hide file tree

Showing 3 changed files with 64 additions and 60 deletions.
diff --git a/02 Agile Planning.md b/02 Agile Planning.md
@@ -56,6 +56,8 @@ Now work with your client to apply **MoSCoW** rules so that these requirements a
 
 Can you identify the _functional_ and _non-functional_ requirements in these user stories?
 
+----
+
 ## Agile Roadmap
 
 This activity should be carried out with the client. At the end of each step take a photograph of your roadmap, this will be useful when writing up your reflective report.

diff --git a/03 Architecture.md b/03 Architecture.md
@@ -112,4 +112,65 @@ Here is a typical `.git/config` file:
 The main way you should use to work with Git are the _shell commands_ you enter using the _terminal_. Whilst you should be comfortable using these commands you might want to use a more graphical tool for day-to-day Git operations. There are many options however you should investigate:
 
 - Code editor Git integration: most modern code editors such as [Visual Studio Code](https://code.visualstudio.com) either come preconfigured with Git integration or it can be added as a plugin. These tools, whilst ideal for basic git work don't have the capability to run the more powerful commands.
-- Standalone Git tools: whilst there are a lot of these, many (such as the one available from GitHub) are not easy to use and you may cause issues with your repository. One of the ones recommended is [GitKraken](https://www.gitkraken.com) which although has a cost attached is free for academic use.
+- Standalone Git tools: whilst there are a lot of these, many (such as the one available from GitHub) are not easy to use and you may cause issues with your repository. One of the ones recommended is [GitKraken](https://www.gitkraken.com) which although has a cost attached is free for academic use.
+
+## 7 Sprint Planning
+
+As a team:
+
+1. Identify who will be the **Scrum Master** and who will be the **Product Owner**.
+2. Ideally with the client present, take the first user story from the top row of your user story map:
+    1. The product owner describes it from the user's perspective
+    2. Discusses how it can be implemented and work collaboratively on a whiteboard/flipchart to define it's UI until the client/product owner is satisfied/
+    3. Explain the success criteria (how will the team know they have completed the story implementation.
+3. Once the client has left:
+    1. Break the story into the component tasks and write these on sticky notes.
+    2. Use planning poker to estimate how many hours each task will take.
+        - If the estimated time for a task is longer than 4 hours, consider splitting the task down.
+    3. Add them to the left column of your Kanban board.
+    4. Finally the _Scrum Master_:
+        1. adds up the estimated durations for the tasks on the Kanban board and
+        2. draws out a burndown chart:
+            1. The X axis should show the days in the sprint.
+            2. the Y axis should show the combined duration.
+        3. draws a staight line from the top of the Y axis to the end of the X axis to indicate the optimal burn rate. 
+
+### 1.1 The Kanban Board
+
+For this first sprint, your Kanban board should have 4 columns as shown:
+
+```
+╔════════════════╦════════════════╦════════════════╦════════════════╗
+║ To Do          ║ Planning       ║ Implementation ║ Done           ║
+╟────────────────╫────────────────╫────────────────╫────────────────╢
+║   ┌────────┐   ║                ║                ║                ║
+║   │        │   ║                ║                ║                ║
+║   └────────┘   ║                ║                ║                ║
+║   ┌────────┐   ║                ║                ║                ║
+║   │        │   ║                ║                ║                ║
+║   └────────┘   ║                ║                ║                ║
+║   ┌────────┐   ║                ║                ║                ║
+║   │        │   ║                ║                ║                ║
+║   └────────┘   ║                ║                ║                ║
+╚════════════════╩════════════════╩════════════════╩════════════════╝
+```
+
+At the start of the sprint, all tasks should be in the first column. By the end of the sprint, all tasks should be in the last column.
+
+### 1.2 The Burndown Chart
+
+Here is an example of a burndown chart showing the line of optimal development. In this example the sprint lasts from Mon to Fri and there are an estimated 40 hours of development. It shows that the optimum burn rate would be 10 hours per day.
+
+```
+  40 ║*
+     ║   *
+  30 ║      *
+     ║         *
+  20 ║            *
+     ║               *
+  10 ║                  *
+     ║                     *
+  00 ║                        *
+     ╚══════════════════════════
+       M    T     W     T     F
+```
diff --git a/04 Agile Development.md b/04 Agile Development.md
@@ -5,65 +5,6 @@ Each week you will be expected to complete a series of lab activities. You will
 
 You should refer to [this week's presentation](https://drive.google.com/open?id=1nAEwEr7C6VTcRLSTnGqzhDvFzvek8fcKZuNHcjikBBs).
 
-## 1 Sprint Planning
-
-As a team:
-
-1. Identify who will be the **Scrum Master** and who will be the **Product Owner**.
-2. Ideally with the client present, take the first user story from the top row of your user story map:
-    1. The product owner describes it from the user's perspective
-    2. Discusses how it can be implemented and work collaboratively on a whiteboard/flipchart to define it's UI until the client/product owner is satisfied/
-    3. Explain the success criteria (how will the team know they have completed the story implementation.
-3. Once the client has left:
-    1. Break the story into the component tasks and write these on sticky notes.
-    2. Use planning poker to estimate how many hours each task will take.
-        -  If the estimated time for a task is longer than 4 hours, consider splitting the task down.
-    3. Add them to the left column of your Kanban board.
-    4. Finally the _Scrum Master_:
-        1. adds up the estimated durations for the tasks on the Kanban board and
-        2. draws out a burndown chart:
-            1. The X axis should show the days in the sprint.
-            2. the Y axis should show the combined duration.
-        3. draws a staight line from the top of the Y axis to the end of the X axis to indicate the optimal burn rate. 
-
-### 1.1 The Kanban Board
-
-For this first sprint, your Kanban board should have 4 columns as shown:
-```
-╔════════════════╦════════════════╦════════════════╦════════════════╗
-║ To Do          ║ Planning       ║ Implementation ║ Done           ║
-╟────────────────╫────────────────╫────────────────╫────────────────╢
-║   ┌────────┐   ║                ║                ║                ║
-║   │        │   ║                ║                ║                ║
-║   └────────┘   ║                ║                ║                ║
-║   ┌────────┐   ║                ║                ║                ║
-║   │        │   ║                ║                ║                ║
-║   └────────┘   ║                ║                ║                ║
-║   ┌────────┐   ║                ║                ║                ║
-║   │        │   ║                ║                ║                ║
-║   └────────┘   ║                ║                ║                ║
-╚════════════════╩════════════════╩════════════════╩════════════════╝
-```
-
-At the start of the sprint, all tasks should be in the first column. By the end of the sprint, all tasks should be in the last column.
-
-### 1.2 The Burndown Chart
-
-Here is an example of a burndown chart showing the line of optimal development. In this example the sprint lasts from Mon to Fri and there are an estimated 40 hours of development. It shows that the optimum burn rate would be 10 hours per day.
-```
-  40 ║*
-     ║   *
-  30 ║      *
-     ║         *
-  20 ║            *
-     ║               *
-  10 ║                  *
-     ║                     *
-  00 ║                        *
-     ╚══════════════════════════
-       M    T     W     T     F
-```
-
 ## 2 Conducting the Sprint
 
 During this first sprint, your development team will need to carry out a **Daily Standup meeting** every morning. Before this meeting, the _Scrum Master_ should: