Renamed principle 3, added 4 new blog posts

_layouts/post.html

@@ -7,7 +7,9 @@ body_class: post
   {{ page.title }}  
 </h1>
+<div class="date">
 {{ page.date | date: "%b %d, %Y" }}
+</div>
 {{ content }}
@@ -32,7 +34,7 @@ body_class: post
             <h4>
               <a href="{{ site.baseurl }}{{ post.url }}">
                 {{ post.title }}
-                <small>{{ post.date | date_to_string }}</small>
+                <small class="date">{{ post.date | date_to_string }}</small>
               </a>
             </h4>
           </li>
@@ -62,7 +64,7 @@ body_class: post
             <h4>
               <a href="{{ site.baseurl }}{{ post.url }}">
                 {{ post.title }}
-                <small>{{ post.date | date_to_string }}</small>
+                <small class="date">{{ post.date | date_to_string }}</small>
               </a>
             </h4>
           </li>

_posts/2017-04-16-what-is-conversational-development.md

+---
+title: What is Conversation Development (ConvDev) and why should you care?
+date:   2017-04-16 8:00:00 +0100
+categories: guide beginner
+---
+
+ConvDev evolves the agile software development principles into a practical framework for modern software development. The agile manifesto and 12 principles are ideals every team should strive for but they don’t tell you how to get there. Frameworks like SCRUM or methodologies like Kanban have attempted to bring more structure and order to the software development process but introduce additional abstractions or endless columns of tasks with not end in sight.
+
+<p class="breakout">
+ConvDev takes a different approach by constraining the agile principles to what’s at the center of getting work done, the conversation. 
+</p>
+
+No matter what framework or methodology is used, work is always organized around meetings, updates and reviews no matter what department or even industry you are in. 
+
+ConvDev acknowledges this underlying construct of getting work done - the conversation - and instead of hiding it or abstracting it away organizes work around it to create a natural, light and specific result focused framework. The conversation encompasses every stage of taking an idea to production, from discussing what needs can be improved, how to implement it to asking if worked and brought the expected value to the customer.
+
+## The four principles
+
+The values of ConvDev are represented in four principles extracted from years of experience working in, with and observing how efficient and successful teams work.
+
+[Find out how](/2017/04/19/efficient-teams-use-short-conversation-cycles/) 
+efficient teams use Principle 1, 
+[short conversation cycles](/2017/04/19/efficient-teams-use-short-conversation-cycles/), 
+to get more done.

_posts/2017-04-19-efficient-teams-use-short-conversation-cycles.md

+---
+title: Efficient teams use short conversation cycles to get more done
+date:   2017-04-19 8:00:00 +0100
+categories: guide beginner
+--- 
+
+Efficient teams use shorter conversation cycles by identifying what is the Minimum Viable Change (MVC) that can bring value to customers. They are less concerned by delivering entire products or features in one go and instead ask what is the smallest aspect of the feature or product that can be shipped to bring value to the customer as soon as possible.
+
+<div class='row'>
+  <div class='col-md-2 col-xs-1'>
+    &nbsp;
+  </div>
+  <div class='col-md-8 col-xs-8'>
+    <img style="width:100%" src="/images/mvc.png"/>
+  </div>
+  <div class='col-md-2 col-xs-1'>
+    &nbsp;
+  </div>
+</div>
+
+<br>
+
+Interestingly the same rebuttals are always given by those not using MVC, “If we release our product piece by piece our competitors will steal our idea,” or “The product is too complicated and only adds value in its entirety.” 
+
+But using MVC allows you to iterate quicker, receive feedback sooner and more frequently, allowing you to affordably accommodate change and provide truly unique value to your customers while always leaving your competitors a few steps behind your incredible pace.
+
+[Learn how](/2017/04/23/thread-the-conversation-through-all-stages/) 
+to use Principle 2 to [thread the conversation through all stages](/2017/04/23/thread-the-conversation-through-all-stages/) to increase transparency and knowledge sharing. 
+
+## We would love to hear from you
+
+How you have shortened your development cycle? What are your thoughts and concerns with implementing shorter cycles?

_posts/2017-04-23-thread-the-conversation-through-all-stages.md

+---
+title: Why should you thread the conversation through all stages
+date:   2017-04-23 8:00:00 +0100
+categories: guide beginner
+---
+
+Work consists of many disconnected conversations happening during meetings, phone calls, video conferencing, over email and team messaging or even at lunch or over drink after work. Efficient teams recognize the value of all these conversations and thread them together to create one narrative from idea to production – a single conversation threaded through all mediums of communication.
+
+To thread the conversation through all stages of the software development lifecycle you will need a suite of integrated tools. Automating the the process is the key to making it a success. The more you can remove steps which require team members to manually take information from one tool to another the more knowledge can be shared. 
+
+- Setup your meeting recordings to be automatically uploaded and linked to relevant issues.
+- Use ChatOps to quickly and easily create and manage issues in your project management tool directly from your team chat. 
+- Integrate your CI/CD pipeline with your code repository and issue tracker to have a complete overview of the health of your project. 
+
+A conversation threaded through all stages will give you traceability allowing you to measure the time and effort required by each team member for every stage enabling you to make changes to improve efficiency.
+
+[Learn how](/2017/04/25/successful-teams-open-conversations-without-consensus/) 
+successful teams use Principle 3, 
+[open conversations without consensus](/2017/04/25/successful-teams-open-conversations-without-consensus/) 
+to get diverse solutions to problems and increase knowledge sharing. 

_posts/2017-04-25-successful-teams-open-conversations-without-consensus.md

+---
+title: Successful teams open conversation but don't require consensus
+date:   2017-04-25 8:00:00 +0100
+categories: guide beginner
+---
+
+Successful teams have an open and inclusive culture but don’t require consensus to make decisions. 
+
+Instead of locking conversations to a stage, team or specialty leave the doors as open as possible to encourage diverse solutions and improve knowledge sharing. Much like [threading the conversation through all stages](/2017/04/23/thread-the-conversation-through-all-stages/), opening the conversation benefits from a suite of integrated tools and favors a decentralized and asynchronous approach to work which better prepares the team to work independently and even remotely if desired.
+
+<p class="breakout">
+An open conversation does not mean everyone must agree before moving forward, it is used to share and compare different opinions and for the manager to make and own the decision on behalf of the team.
+</p>
+
+Opening the conversation up can be challenging, it is important that all participants understand and adhere to a code of conduct which at its heart encourages team members to argue the solution with pros and cons and not the person. Agile Coaches can mediate the conversation and Project Managers or Leads can summarize the conversation and make the final decision for the team. 
+
+## How does your team stay focused with open conversations?
+
+Opening a conversation can lead to more talk and less work if not mediated.  We have found that each task or project needs to have someone who is explicitly accountable and owns the decision making process. We would love to know how your team directs conversations to actionable decisions?

css/index.css

@@ -14,6 +14,11 @@ body {
   background-color: #fff;  
 }
+table {
+  font-size: small;
+  max-width: 100%;
+}
+
 .container {
 }
@@ -121,9 +126,25 @@ body.why .main section {
   font-weight: bold;
 }
-table {
-  font-size: small;
-  max-width: 100%;
+.main .date {
+  margin-bottom: 25px;
+}
+
+.main small.date {
+  display: block;
+  margin-bottom: 0;  
+}
+
+.date {
+  font-style: italic;
+  color: #666;
+}
+
+.breakout {
+  font-size: x-large;
+  padding: 10px 35px;
+  font-style: italic;
+  color: #666;
 }
 .footer {

invite-everyone.md → open-conversations.md

 ---
 ---
-## Principle 3: Invite everyone to the conversation
+## Principle 3: Open conversations without consensus
 Instead of locking conversation on per-stage, per team, or per-specialty 
 principle, leave the doors as open as possible.

why.md

@@ -25,13 +25,13 @@ 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.
 [Read more about threading the conversation through all stages](/thread-conversations).
-### [3. Invite everyone to the conversation](/invite-everyone)
+### [3. Open conversations without consensus](/open-conversations)
 Instead of locking conversation on per-stage, per team, or per-specialty 
 principle, leave the doors as open as possible to increase the reuse of 
 solutions, prevent duplicate work, increase knowledge sharing and scale your 
 organization.
-[Read more about inviting everyone to the conversation](/thread-conversations).
+[Read more about opening the conversation](/open-conversations).
 ### [4.Result oriented conversation](/results-oriented)