Merge branch 'open_conversations' into 'master'

fixed broken links after principle 3 renaming

See merge request !34

_posts/2017-04-13-how-to-start-adopting-conversational-development.md

@@ -16,7 +16,7 @@ Each of the five stages on the model has fewer barriers to collaboration and inv
 1. [**Shorten** the conversation cycle](/shorten-cycle)
 1. [**Thread** the conversation through all stages](/thread-conversations) 
-1. [**Invite** everyone to the conversation](/invite-everyone) 
+1. [**Open** conversations without consensus](/open-conversations)
 1. [**Result** oriented conversation](/results-oriented) 
 ### Focus on Minimum Viable Change
@@ -39,7 +39,7 @@ As an exercise to get started pick a feature and ask your team what is the small
 Record any meetings or if not possible have someone take meeting notes to share with everyone afterwards. It is important to thread the conversation through the entire process either by linking various tools or using a centralized solution. A linked conversation with clearly defined stage transitions will allow your team to measure the entire cycle time for the minimum viable change as well as the time spent in each stage e.g design, development, testing etc. 
-#### 3. Invite
+#### 3. Open
 Make sure you invite someone from each cross functional team to the conversation and that the conversation is not dominated by anyone. There is nothing wrong with having a project manager or agile coach lead the conversation and act as a mediator.

thread-conversations.md

@@ -41,4 +41,4 @@ possible.
 The reason for that is that it is the only way to measure the cycle time (and 
 therefore, shorten it) and have result oriented conversations.
-[Principle #3: Invite everyone to the conversation](/invite-everyone)
+[Principle #3: Open conversations without consensus](/open-conversations)