Format all Exercises the same

chrisedington · Dec 16, 2014 · 12f3b62 · 12f3b62
1 parent 5b15286
commit 12f3b62
Show file tree

Hide file tree

Showing 14 changed files with 32 additions and 10 deletions.
diff --git a/Exercises/assumptions.md b/Exercises/assumptions.md
@@ -4,6 +4,7 @@
 **Estimated time:** 30 minutes
 
 ## Best to use when
+
 It is best to always keep track of the assumptions
 that you and your team are making about
 your product through the life of the product.
@@ -26,6 +27,7 @@ and how you know if that assumption is valid.
 * Repeat till all assumptions have a test for them.
 
 ## Example
+
 ![Galen's Assumption Test board](http://images.thoughtbot.com/the-product-design-sprint/assumptions.jpg)
 
 From [The Product Design Sprint](http://robots.thoughtbot.com/the-product-design-sprint)

diff --git a/Exercises/back-burner.md b/Exercises/back-burner.md
@@ -5,12 +5,14 @@
 **Estimated time:** 30min for review
 
 ## Best to use when
+
 A lot of ideas will be generated throughout the week. Some of the ideas
 will be pertinent to the tasks at hand, but others, although interesting, won’t
 be. Capture these good but not immediately relevant back burner ideas on a
 sticky note board.
 
 ## Instructions
+
 1. Have a dedicated space to collect back burner ideas on the whiteboard.
 * Throughout the sprint have everyone write down ideas that are not directly
 solving the job-to-be-done
@@ -23,4 +25,4 @@ Trash any that aren't relevant anymore.
 
 ## Example
 
-![Back Burner](images/back-burner.jpg)
+![Back Burner](images/back-burner.jpg)
diff --git a/Exercises/card-sorting.md b/Exercises/card-sorting.md
@@ -5,6 +5,7 @@
 **Estimated time:** 20 min
 
 ## Best to use when
+
 Card sorting helps organize and understand how people perceive the information architecture for the application. It is best to use when there are a seemingly a lot of ideas and a lot to take in. Card sorting helps understand the many facets of a problem by giving you a top down view.
 
 > Card sorting will help you understand your users' expectations and understanding of your topics. It is often most useful once you have done some homework to find out about your users and understand your content.
@@ -13,6 +14,7 @@ Card sorting helps organize and understand how people perceive the information a
 
 
 ## Instructions
+
 #### Open Card Sorting - Best for Understand
 1. Take 5 minutes and have all participants write down as many ideas as possible on post-its. If people get stuck just have them write down what they think is the most important idea again and again till they come up with more.
 2. Have everyone put their post-its up on the wall and take a min to read over them. 
@@ -31,6 +33,7 @@ Card sorting helps organize and understand how people perceive the information a
 For more detailed explanation see [Card Sorting](http://robots.thoughtbot.com/card-sorting)
 
 ## Example
+
 ### Open Card Sorting
 ![Open Card Sorting](images/open-card-sorting.jpg)
 

diff --git a/Exercises/crazy-eights.md b/Exercises/crazy-eights.md
@@ -35,9 +35,7 @@ that it is clear which sketch they should be on.
 * Repeat as necessary.
 
 ## Examples
+
 ![Crazy Eights Example](images/crazy-eights.jpg)
 ![Crazy Eights Example](images/crazy-six.jpg)
 ![Crazy Eights Example](images/crazy-six-2.jpg)
-
-
-
diff --git a/Exercises/critical-path.md b/Exercises/critical-path.md
@@ -5,6 +5,7 @@
 **Estimated time:** 15 min
 
 ## Best to use when
+
 The Critical Path should be discussed after a
 [Problem Statement](problem-statement.md) has been agreed upon.
 Once completed, the Critical Path should give a step-by-step map
@@ -41,4 +42,4 @@ The end result often looks like the map of a bus or subway line:
 ![Galen's Critical Path](http://images.thoughtbot.com/the-product-design-sprint/criticalpath.jpg) 
 From [The Product Design Sprint](http://robots.thoughtbot.com/the-product-design-sprint)
 
-![Example Critical Path](images/critical-path.jpg)
+![Example Critical Path](images/critical-path.jpg)
diff --git a/Exercises/five-whys.md b/Exercises/five-whys.md
@@ -5,21 +5,24 @@
 **Estimated time:** 30 min
 
 ## Best to use when
+
 Five whys should be used to get to the very root of a reasons for a problem. It also shows the relationships between several causes of the problem. 
 
 ## Instructions
+
 1. Write down a specific problem
 2. Ask the team to individually write down why that is happening.
 3. Form a new problem from the answers the team gave.
 4. Repeat steps 2 and 3 four more times or as much as necessary.
 5. Analyze the results and form relationships between answers.
 
 ## Example
+
 - The vehicle will not start. (the problem)
 - Why? - The battery is dead. (first why)
 - Why? - The alternator is not functioning. (second why)
 - Why? - The alternator belt has broken. (third why)
 - Why? - The alternator belt was well beyond its useful service life and not replaced. (fourth why)
 - Why? - The vehicle was not maintained according to the recommended service schedule. (fifth why, a root cause)
 
-Taken from [Wikipedia](http://en.wikipedia.org/wiki/5_Whys)
+Taken from [Wikipedia](http://en.wikipedia.org/wiki/5_Whys)
diff --git a/Exercises/group-critique.md b/Exercises/group-critique.md
@@ -5,6 +5,7 @@
 **Estimated time:** 3 minutes for each sketch
 
 ## Best to use when
+
 It is best to do a Group Critique after a Silent critique has already been done.
 It allows for in-depth discussion around the idea. It gives time for people to
 say what they thought was good about the idea and for the person that had the

diff --git a/Exercises/mind-mapping.md b/Exercises/mind-mapping.md
@@ -5,6 +5,7 @@
 **Estimated time:** 10–15 minutes
 
 ## Best to use when
+
 They are best used to warm up to other exercises
 like [Crazy Eights](crazy-eights.md).
 These are best for personal ideas,
@@ -17,6 +18,7 @@ along with Crazy Eights,
 [Silent Critique](silent-critique.md).
 
 ## Instructions
+
 > If you’re not familiar with mind mapping already, I often describe it as
 writing down everything in your head with no specific formatting; or quiet
 individual brainstorming. You can write words and connect them or not, you can

diff --git a/Exercises/needs-wants-desires.md b/Exercises/needs-wants-desires.md
@@ -5,6 +5,7 @@
 **Estimated time:** 30 min
 
 ## Best to use when
+
 Needs, Wants, Desires is a [Card Sorting](card-sorting.md)
 exercise to help figure out priorities.
 It's best to use when there are a lot of feature ideas
@@ -27,4 +28,5 @@ look at each section and the features in them
 and verify that each feature in is the appropriate section.
 
 ## Examples
-![Needs, Wants, Desires](images/needs-wants-desires.jpg)
+
+![Needs, Wants, Desires](images/needs-wants-desires.jpg)
diff --git a/Exercises/pitch-practice.md b/Exercises/pitch-practice.md
@@ -5,6 +5,7 @@
 **Estimated time:** 5 min
 
 ## Best to use when
+
 It's best to practice the pitch several times throughout the sprint, typically
 at the beginning of each day.
 It makes sure that everyone is staying

diff --git a/Exercises/problem-statement.md b/Exercises/problem-statement.md
@@ -5,6 +5,7 @@
 **Estimated time:** 20 min
 
 ## Best to use when
+
 It is best to identify the job-to-be-done that the sprint
 is trying to solve as early in
 the process as possible.
@@ -29,4 +30,5 @@ What is this product, and is it useful?
    reflect back on.
 
 ## Example
-![Problem Statement](images/problem-statement.jpg)
+
+![Problem Statement](images/problem-statement.jpg)
diff --git a/Exercises/silent-critique.md b/Exercises/silent-critique.md
@@ -5,6 +5,7 @@
 **Estimated time:** 5 min
 
 ## Best to use when
+
 Silent Critique is best to use after an individual thought process
 like [Storyboards](storyboards.md).
 It is a way to have a more unbiased and individual critique period.
@@ -35,6 +36,7 @@ vote for their own ideas.
 4. Jump into a [Group Critique](group-critique.md).
 
 ## Examples
+
 ![Silent Voting](images/silent-voting.jpg)
 ![Silent Voting](images/storyboards-2.jpg)
-![Silent Voting](images/storyboard.jpg)
+![Silent Voting](images/storyboard.jpg)
diff --git a/Exercises/storyboards.md b/Exercises/storyboards.md
@@ -5,6 +5,7 @@
 **Estimated time:** 20 min
 
 ## Best to use when
+
 Storyboards are great to use when the group has had some time to think
 individually about the problem and many possible solutions to it. Storyboards
 allow people to develop those early ideas further by giving them more time to
@@ -48,4 +49,4 @@ Make sure that each frame is understandable without further verbal explanation.
 ![Individual Storyboards](images/storyboard.jpg)
 ![Group of Storyboards](images/storyboards.jpg)
 ![Group of Storyboards](images/storyboards-2.jpg)
-![Individual Storyboards](images/storyboard-2.jpg)
+![Individual Storyboards](images/storyboard-2.jpg)
diff --git a/Exercises/who-what-when-where.md b/Exercises/who-what-when-where.md
@@ -5,6 +5,7 @@
 **Estimated time:** 30 min
 
 ## Best to use when
+
 Who, What, When, Where is best to use to find out what the different
 questions are surrounding a topic or problem.
 It helps uncover problems that are underlying or associated with the main
@@ -16,6 +17,7 @@ It works really well with a large group of people to
 get them all on the same page quickly.
 
 ## Instructions
+
 1. Divide up the whiteboard into four sections and
 give each a title of Who, What, When, and Where.
 2. Start with Who.